ssh over wifi on paperwhite

[nasser]

I finally managed to get usbnet working on my PW..
Used latest 0.9 version..
Telnet worked straightaway..
Could never get root password working for ssh.. tried mario and the other two too..
Did the shared keys trick and got ssh working over usb..

Now.. how do I get ssh over wifi working?
there is a kual shortcut under usbnet menu..
there is also a config option..
but is usbnet really required for ssh over wifi..? since you don't need to have the kindle plugged in..? Or do you..?
which address do you try for connecting over wifi? Obviously not 192.168.15.244?
I tried getting the kindle i.p(dhcp) using the ";711" trick.. still not successful..
not able to ping kindle over wifi..
what do you need to do on the PC side..?

[NiLuJe]

Until you enable SSH over WiFi in the USBNet settings, you should *NOT* have any issue with passwords, dropbear is patched to let you in no matter what (not OpenSSH, but dropbear, the default, yes).

That said, to get in over WiFi, you'll need the Kindle IP address for the wireless network interface. It should be in you usual subnet, since it's connecting to your usual router. It should be visible on the ;711 page, IIRC, or you can simply run ifconfig over USB .

Not sure if ICMP pings are blocked by the firewall over WIFi, so the fact that it doesn't ping might not be a good indicator.

[knc1]

Originally Posted by NiLuJe

Until you enable SSH over WiFi in the USBNet settings, you should *NOT* have any issue with passwords, dropbear is patched to let you in no matter what (not OpenSSH, but dropbear, the default, yes).

That said, to get in over WiFi, you'll need the Kindle IP address for the wireless network interface. It should be in you usual subnet, since it's connecting to your usual router. It should be visible on the ;711 page, IIRC, or you can simply run ifconfig over USB .

Not sure if ICMP pings are blocked by the firewall over WIFi, so the fact that it doesn't ping might not be a good indicator.

@nasser: Which firewall ?
Amazon "stock" or mine?

[nasser]

Haven't looked at or fiddled with any firewall yet.. so don't know..
but nmap output as below.. when kindle accessed by ssh over usb:
---------------------------------
Starting Nmap 5.00
Interesting ports on kpw.xxx.yyy (192.168.15.244):
Not shown: 998 closed ports
PORT STATE SERVICE
22/tcp open ssh
23/tcp open telnet
--------------------------------

till now had tried enabling ssh over wifi by using kual usbnet menu..
will try setting it in the config next..

[nasser]

hmm..
found that executing kual usbnet submenu for allow/restrict wifi is actually modifying the config file..

[NiLuJe]

@knc1: stock

@nasser: Yep, it does tweak the config file. Note that you'll need to reboot your device for those changes to be taken into account.

[nasser]

ssh over wifi working now..
regarding root passwords for ssh over usb, i suppose i must have enabled and left on wifi over ssh setting..
since i now have shared keys, can't test that again.. unless i remove them..:-)

[nasser]

Originally Posted by NiLuJe

@knc1: stock

..Note that you'll need to reboot your device for those changes to be taken into account.

Hmm.. i suppose i must have tried without rebooting too.. which was why root login didn't work..

[nasser]

Originally Posted by NiLuJe

..Not sure if ICMP pings are blocked by the firewall over WIFi, so the fact that it doesn't ping might not be a good indicator.

strange thing: with kindle on wifi am able to ping pc from kindle (kterm or ssh from pc) but not able to ping kindle from pc.. so it does look like the (stock) kindle firewall blocks pings..

[knc1]

Originally Posted by nasser

strange thing: with kindle on wifi am able to ping pc from kindle (kterm or ssh from pc) but not able to ping kindle from pc.. so it does look like the (stock) kindle firewall blocks pings..

Responses to outbound ping answers only allowed on **stock** firewall input chain:

Packet counts taken at: 2013-07-22T12:19:15UTC

Chain INPUT (policy DROP 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     tcp  --  ppp0   *       0.0.0.0/0            0.0.0.0/0           tcp dpt:40317 
    0     0 ACCEPT     tcp  --  ppp0   *       0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED 
    0     0 ACCEPT     tcp  --  wlan0  *       0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED 
    0     0 ACCEPT     udp  --  wlan0  *       0.0.0.0/0            0.0.0.0/0           state ESTABLISHED 
    0     0 ACCEPT     udp  --  ppp0   *       0.0.0.0/0            0.0.0.0/0           state ESTABLISHED 
    0     0 ACCEPT     udp  --  ppp0   *       0.0.0.0/0            0.0.0.0/0           udp spt:40317 
    0     0 ACCEPT     udp  --  ppp0   *       0.0.0.0/0            0.0.0.0/0           udp spt:49317 
    0     0 ACCEPT     udp  --  ppp0   *       0.0.0.0/0            0.0.0.0/0           udp spt:33434 
   24  2488 ACCEPT     all  --  lo     *       127.0.0.1            0.0.0.0/0           
    0     0 ACCEPT     all  --  usb0   *       0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     icmp --  *      *       0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED 

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
   24  2488 ACCEPT     all  --  *      lo      0.0.0.0/0            127.0.0.1

Note: The BBB packet counter report works on either the stock or the BBB.firewall.