USBNetworking on the KindleBerry PI [KT 5.3.7.3]

jollyblondgiant · 11-08-2021, 07:02 PM

Hello again Wizards,

I've just about got a KindleBerry Pi setup between by raspi4 (raspbian 10) and my KT (5.3.7.3). Just about everything works, I just have to automate ssh keys on the kindle.

One issue I've had so far is that USBNetworking must not be set up 100%, but in my searching I haven't been able to find a reference to my issue: I am able to ssh into my raspi from my kindle over wifi, but not over USB.

Testing with ifconfig on my pc, I don't see an entry for the kindle when I plug it in. The light that indicates that the kindle is attached does light up, but each entry for ifconfig is present whether or not the kindle is plugged in.

A similar issue presents itself when I try USBN directly between the pi and the kindle: running ifconfig in kterm returns the same entries whether or not the kindle and pi are physically connected.

What painfully stupid thing am I missing w/r/t USBNetworking setup?

katadelos · 11-08-2021, 08:01 PM

2 things to check:

Is the USBNet extension installed and enabled?
Does your Kindle go into USB Drive mode when attached to your PC or Pi? If not, your cable is either busted or charge-only.

jollyblondgiant · 11-09-2021, 06:51 AM

Thank you for the response! I’ll answer your questions in order:

1. Yes, I toggle and check the usbnetwork under kual to ensure it is enabled before attaching the usb.

2. I use the same cable I used to install the jailbreak, which I am confident is a data cable.

jollyblondgiant · 11-09-2021, 11:33 AM

Perhaps interesting: when the two are tethered, ifconfig on the pi detects the kindle, just not the other way around.

katadelos · 11-09-2021, 04:23 PM

Quote:

Originally Posted by jollyblondgiant

Perhaps interesting: when the two are tethered, ifconfig on the pi detects the kindle, just not the other way around.

Try plugging in the Kindle then run dmesg on the Pi - you should see something similar to this:

Code:

[212626.094661] usb 1-2: new high-speed USB device number 106 using xhci_hcd
[212626.249894] usb 1-2: New USB device found, idVendor=0525, idProduct=a4a2, bcdDevice= 3.99
[212626.249912] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[212626.249921] usb 1-2: Product: RNDIS/Ethernet Gadget
[212626.249927] usb 1-2: Manufacturer: Linux 3.0.35-lab126 with fsl-usb2-udc
[212626.253116] cdc_subset: probe of 1-2:1.0 failed with error -22
[212626.256638] cdc_ether 1-2:1.0 usb0: register 'cdc_ether' at usb-0000:00:14.0-2, CDC Ethernet Device, ee:49:00:00:00:00
[212626.308247] cdc_ether 1-2:1.0 enxee4900000000: renamed from usb0

As you noticed, a new network interface will appear when running ifconfig:

Code:

enxee4900000000: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::bd21:212e:6ca6:7430  prefixlen 64  scopeid 0x20<link>
        ether ee:49:00:00:00:00  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4  bytes 632 (632.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Attempting to SSH into the Kindle at this point will fail because an IP address hasn't been defined on the Pi for the interface presented by the Kindle. ifconfig is just a utility to list and configure network interfaces, it doesn't automatically set the connection up for you.

To set the IP address for the network interface presented by the Kindle, run this:

Code:

sudo ifconfig enxee4900000000 192.168.15.201

You should now be able to ping and SSH into the Kindle:

Code:

user@ubuntu:~$ ping 192.168.15.244
PING 192.168.15.244 (192.168.15.244) 56(84) bytes of data.
64 bytes from 192.168.15.244: icmp_seq=1 ttl=64 time=0.372 ms
64 bytes from 192.168.15.244: icmp_seq=2 ttl=64 time=0.242 ms
^C
--- 192.168.15.244 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1027ms
rtt min/avg/max/mdev = 0.242/0.307/0.372/0.065 ms

Code:

user@ubuntu:~$ ssh root@192.168.15.244


Welcome to Kindle!

root@192.168.15.244's password: 
#################################################
#  N O T I C E  *  N O T I C E  *  N O T I C E  # 
#################################################
Rootfs is mounted read-only. Invoke mntroot rw to
switch back to a writable rootfs.
#################################################
[root@kindle root]#

Manually setting the IP address is still annoying though - it would be nice if we could set things up to handle this automatically. IIRC, Raspbian uses netplan now, so you should be able to define a configuration that does exactly that:

Code:

network:
  version: 2
  renderer: networkd
  ethernets:
    enxee4900000000:
      link-local: []
      dhcp4: false
      addresses:
        - 192.168.15.201/24

Save the contents of the code block above to /etc/netplan/01-kindle.yaml then run the command below:

Code:

sudo netplan apply

This will automatically assign the IP address 192.168.15.201 to the network interface presented by the Kindle when you next plug it in. Note that the network interface name might differ on your Pi - if it does, substitute enxee4900000000 with the interface name that you saw appearing in ifconfig.

jollyblondgiant · 11-13-2021, 09:36 AM

Thank you for the detailed writeup!

Turns out I had to switch cables after all, because I am a smoothbrain who assumed I could use the same usb cord in either kindle mode. Swapped for the usb from my wacom and dmesg returns this:

Quote:

[ 1237.377750] usb 1-1.1: new high-speed USB device number 3 using xhci_hcd
[ 1237.522913] usb 1-1.1: New USB device found, idVendor=0525, idProduct=a4a2, bcdDevice= 3.25
[ 1237.522935] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1237.522953] usb 1-1.1: Product: RNDIS/Ethernet Gadget
[ 1237.522971] usb 1-1.1: Manufacturer: Linux 2.6.31-rt11-lab126 with fsl-usb2-udc
[ 1237.616145] cdc_subset: probe of 1-1.1:1.0 failed with error -22
[ 1237.621049] cdc_subset 1-1.1:1.1 usb0: register 'cdc_subset' at usb-0000:01:00.0-1.1, Linux Device, 9a:ad:04:62:d6:2a
[ 1237.621219] usbcore: registered new interface driver cdc_subset
[ 1237.621283] cdc_ether: probe of 1-1.1:1.0 failed with error -16
[ 1237.621357] usbcore: registered new interface driver cdc_ether

The first thing that's apparent to me is that my dmesg returns 'error-16' rather than having renamed usb0.
I continued with:
$ sudo ifconfig usb0 192.168.15.201
$ ping 192.168.15.244

Quote:

PING 192.168.15.244 (192.168.15.244) 56(84) bytes of data. |
From 96.120.108.61 icmp_seq=66 Packet filtered
From 96.120.108.61 icmp_seq=117 Packet filtered

--- 192.168.15.244 ping statistics ---
152 packets transmitted, 0 received, +2 errors, 100% packet
loss, time 169ms

and $ ssh root@192.168.15.244 hangs.

Should I try more usb cables? Is there some simple setup step I've missed in USBN? What is the meaning of 'error-16'? Device is busy? How do I work around this?

Thanks again!

jollyblondgiant · 11-13-2021, 09:49 AM

With a new usb cable came new tests, ran this command on the kindle:
$ ls /sys/class/net/
And it returns

Quote:

lo usb0 wlan0

Regardless of whether the kindles attached to the raspi.

katadelos · 11-14-2021, 07:27 AM

Quote:

Originally Posted by jollyblondgiant

The first thing that's apparent to me is that my dmesg returns 'error-16' rather than having renamed usb0.

This points to an error with either the cable that you're using, the USB port of the host device that you're connecting your Kindle to or a kernel bug within the USB implementation of your host device (i.e not Kindle related).

What is the output of ifconfig on your host device? It sounds like the network interface presented by the Kindle is not being detected by the host.

Quote:

Originally Posted by jollyblondgiant

With a new usb cable came new tests, ran this command on the kindle:
$ ls /sys/class/net/
And it returns

Quote:

lo usb0 wlan0

Regardless of whether the kindles attached to the raspi.

That's expected behavior - these interfaces always exist on the Kindle when USBNet is enabled regardless of whether the device is attached to a host. The only new interface that you should expect to appear is on the host.

jollyblondgiant · 11-14-2021, 09:01 AM

i changed cables and no longer see the error-16. thank you.

Here's the output from my host machine (a pc running Ubuntu) , without the kindle attached:

Code:

$ ifconfig
br-ccee69454789: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 172.18.255.255
        ether 02:42:e8:30:37:c9  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:8d:db:66:a6  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp8s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 70:85:c2:96:38:17  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 208  bytes 17462 (17.4 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 208  bytes 17462 (17.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.192  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::9770:c562:1e7:aa14  prefixlen 64  scopeid 0x20<link>
        ether 78:2b:46:bd:98:fe  txqueuelen 1000  (Ethernet)
        RX packets 807  bytes 980900 (980.9 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 268  bytes 38950 (38.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

And the PC with kindle:

Code:

$  ifconfig
br-ccee69454789: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 172.18.255.255
        ether 02:42:e8:30:37:c9  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:8d:db:66:a6  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp8s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 70:85:c2:96:38:17  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 424  bytes 39118 (39.1 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 424  bytes 39118 (39.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::9595:a560:7580:5f2  prefixlen 64  scopeid 0x20<link>
        ether 2e:0c:86:9a:13:2b  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 13  bytes 1884 (1.8 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.192  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::9770:c562:1e7:aa14  prefixlen 64  scopeid 0x20<link>
        ether 78:2b:46:bd:98:fe  txqueuelen 1000  (Ethernet)
        RX packets 7476  bytes 6355102 (6.3 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4501  bytes 967072 (967.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Here's the output from the pi, which is connected to my wireless router via ethernet (shell access via ssh from my ubuntu pc connected via wifi) before attaching kindle to the pi:

Code:

$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.191  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::95bc:2e39:4afd:8f90  prefixlen 64  scopeid 0x20<link>
        ether dc:a6:32:92:48:f5  txqueuelen 1000  (Ethernet)
        RX packets 522  bytes 96016 (93.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 93  bytes 13210 (12.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 22:1d:b2:af:34:c2  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

and the output from the pi with kindle attached:

Code:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.191  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::95bc:2e39:4afd:8f90  prefixlen 64  scopeid 0x20<link>
        ether dc:a6:32:92:48:f5  txqueuelen 1000  (Ethernet)
        RX packets 635  bytes 109918 (107.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 157  bytes 22786 (22.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 169.254.96.198  netmask 255.255.0.0  broadcast 169.254.255.255
        inet6 fe80::cd6f:2529:65e4:8bcc  prefixlen 64  scopeid 0x20<link>
        ether ee:49:00:00:00:00  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 72  bytes 12124 (11.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 22:1d:b2:af:34:c2  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

in both cases, looks like usb0 is new. that's a good sign, right?
i tried:

Code:

$ ping 169.254.96.198                      |
PING 169.254.96.198 (169.254.96.198) 56(84) bytes of data.  
From 169.254.22.81 icmp_seq=1 Destination Host Unreachable  
From 169.254.22.81 icmp_seq=2 Destination Host Unreachable  
From 169.254.22.81 icmp_seq=3 Destination Host Unreachable  
^C                                                          
--- 169.254.96.198 ping statistics ---                      
5 packets transmitted, 0 received, +3 errors, 100% packet lo
ss, time 164ms

I'm eternally grateful for your continued attentions on my quest.

katadelos · 11-14-2021, 09:41 AM

Looks like you're getting closer now - you should be able to access the Kindle from your Ubuntu PC by setting the IP address of the usb0 interface that appears to 192.168.15.201.

The Pi is detecting the interface correctly but is auto-assigning an bogon IP address to the interface because.. reasons? Try setting the IP address to 192.168.15.201 too.

jollyblondgiant · 11-14-2021, 10:16 AM

I'm trying to implement your suggestion:

from my pc, with kindle directly attached:

Code:

ags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 172.18.255.255
        ether 02:42:61:9b:93:39  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:f0:31:a3:c7  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp8s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 70:85:c2:96:38:17  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 545  bytes 65756 (65.7 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 545  bytes 65756 (65.7 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether b6:02:cb:b6:ff:fa  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 121  bytes 18952 (18.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.192  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::9770:c562:1e7:aa14  prefixlen 64  scopeid 0x20<link>
        ether 78:2b:46:bd:98:fe  txqueuelen 1000  (Ethernet)
        RX packets 49136  bytes 72412979 (72.4 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4954  bytes 715637 (715.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

$ sudo ifconfig usb0 192.168.15.201
$ ping 192.168.15.244
PING 192.168.15.244 (192.168.15.244) 56(84) bytes of data.
64 bytes from 192.168.15.244: icmp_seq=1 ttl=64 time=1.44 ms
64 bytes from 192.168.15.244: icmp_seq=2 ttl=64 time=0.395 ms
64 bytes from 192.168.15.244: icmp_seq=3 ttl=64 time=0.506 ms
64 bytes from 192.168.15.244: icmp_seq=4 ttl=64 time=0.407 ms
64 bytes from 192.168.15.244: icmp_seq=5 ttl=64 time=0.252 ms
^C
--- 192.168.15.244 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4070ms
rtt min/avg/max/mdev = 0.252/0.600/1.442/0.428 ms

$ ssh root@192.168.15.244

here the code hangs but I get "activation of network connection failed" alerts from ubuntu

katadelos · 11-14-2021, 10:40 AM

Quote:

Originally Posted by jollyblondgiant

here the code hangs but I get "activation of network connection failed" alerts from ubuntu

Ubuntu behaves strangely with USBNet (IIRC network-manager will endlessly try to reconfigure the interface, overriding you manually setting the interface IP), try creating and applying the netplan configuration from one of my earlier posts in this thread.

jollyblondgiant · 11-14-2021, 10:20 PM

using ssh on the raspi
I attempted to update my netplan settings but received an error

Code:

sudo: netplan: command not found

$ cat /etc/os-release informs me that I've got buster installed, and apparently busteruses dhcpcd.conf.

i edited mine to include:

Code:

interface usb0
static ip_address=192.168.15.244
static routers=192.168.15.1

then once I rebooted the raspi, I ran:

Code:

$ sudo ifconfig usb0 192.168.15.201
$ ping 192.168.15.244
PING 192.168.15.244 (192.168.15.244) 56(84) bytes of data.
64 bytes from 192.168.15.244: icmp_seq=1 ttl=64 time=1.62 ms
64 bytes from 192.168.15.244: icmp_seq=2 ttl=64 time=0.394 ms
64 bytes from 192.168.15.244: icmp_seq=3 ttl=64 time=0.482 ms
^C
--- 192.168.15.244 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 64ms
rtt min/avg/max/mdev = 0.394/0.832/1.621/0.559 ms

$  ssh root@192.168.15.244                  |


Welcome to Kindle!

root@192.168.15.244's password:
#################################################
#  N O T I C E  *  N O T I C E  *  N O T I C E  #
#################################################
Rootfs is mounted read-only. Invoke mntroot rw to
switch back to a writable rootfs.
#################################################
[root@kindle root]#

jollyblondgiant · 11-14-2021, 10:54 PM

update: added the following code to /home/pi/.bach_profile

Code:

sudo ifconfig usb0 192.168.15.201

and even after multiple reboots, I'm able to ssh into kindle with just

Code:

$ ssh root@192.168.15.244

Thank you so much for your continued patience! How do I use this dark power you've bestowed upon me to ssh into the pi, from the kindle over USB? We've got it set up to go to the kindle from the Pi, which is 2/3 the battle. however, when I try to ssh into the pi on the kindle:

Code:

[kterm]# ping 192.168.15.201

hangs, as does:

Code:

[kterm]# ssh pi@192.168.15.201

jollyblondgiant · 11-15-2021, 10:04 AM

Final update!!
I found that if I run
[CODE]
[kterm]# ifconfig usb0 192.168.15.244
[kterm]# ssh pi@192.168.15.201
[\CODE]

Succeeds! I’m going to modify a bash script to run those two commands before rotating the screen and toggling the keyboard to smoothify setup.

Any suggestions for kterm commands to rotate screen/toggle keyboard? The double-tap method works ok but it’s worth trying to shave off the steps

11-08-2021, 07:02 PM	#1
jollyblondgiant Member Posts: 24 Karma: 10 Join Date: Jun 2021 Device: Kindle Touch K5	USBNetworking on the KindleBerry PI [KT 5.3.7.3] Hello again Wizards, I've just about got a KindleBerry Pi setup between by raspi4 (raspbian 10) and my KT (5.3.7.3). Just about everything works, I just have to automate ssh keys on the kindle. One issue I've had so far is that USBNetworking must not be set up 100%, but in my searching I haven't been able to find a reference to my issue: I am able to ssh into my raspi from my kindle over wifi, but not over USB. Testing with ifconfig on my pc, I don't see an entry for the kindle when I plug it in. The light that indicates that the kindle is attached does light up, but each entry for ifconfig is present whether or not the kindle is plugged in. A similar issue presents itself when I try USBN directly between the pi and the kindle: running ifconfig in kterm returns the same entries whether or not the kindle and pi are physically connected. What painfully stupid thing am I missing w/r/t USBNetworking setup?

11-08-2021, 08:01 PM	#2
katadelos rm -rf / Posts: 219 Karma: 3333683 Join Date: Nov 2019 Location: United Kingdom Device: K5, KT, KT2, KT3, KT4, KV, PW2, PW3, PW4, PW5	2 things to check: Is the USBNet extension installed and enabled? Does your Kindle go into USB Drive mode when attached to your PC or Pi? If not, your cable is either busted or charge-only.

11-14-2021, 10:54 PM	#14
jollyblondgiant Member Posts: 24 Karma: 10 Join Date: Jun 2021 Device: Kindle Touch K5	update: added the following code to /home/pi/.bach_profile Code: sudo ifconfig usb0 192.168.15.201 and even after multiple reboots, I'm able to ssh into kindle with just Code: $ ssh root@192.168.15.244 Thank you so much for your continued patience! How do I use this dark power you've bestowed upon me to ssh into the pi, from the kindle over USB? We've got it set up to go to the kindle from the Pi, which is 2/3 the battle. however, when I try to ssh into the pi on the kindle: Code: [kterm]# ping 192.168.15.201 hangs, as does: Code: [kterm]# ssh pi@192.168.15.201

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Kindleberry ?	bobodude	Kindle Developer's Corner	8	03-18-2017 07:33 AM
Will the Kindleberry dmage the Kindle's screen?	yyman	Kindle Developer's Corner	2	05-10-2013 07:09 AM
Question: Kindleberry Pi Help	penguinsfly1	Kindle Developer's Corner	3	03-02-2013 03:02 PM
KindleBerry Pi, raspberry pi with a kindle screen!	damaru	Kindle Developer's Corner	39	01-20-2013 10:59 PM
KindleBerry PI	skull43	Kindle Developer's Corner	2	01-20-2013 10:59 PM

11-09-2021, 06:51 AM	#3
jollyblondgiant Member Posts: 24 Karma: 10 Join Date: Jun 2021 Device: Kindle Touch K5	Thank you for the response! I’ll answer your questions in order: 1. Yes, I toggle and check the usbnetwork under kual to ensure it is enabled before attaching the usb. 2. I use the same cable I used to install the jailbreak, which I am confident is a data cable.

11-09-2021, 11:33 AM	#4
jollyblondgiant Member Posts: 24 Karma: 10 Join Date: Jun 2021 Device: Kindle Touch K5	Perhaps interesting: when the two are tethered, ifconfig on the pi detects the kindle, just not the other way around.

11-14-2021, 09:41 AM	#10
katadelos rm -rf / Posts: 219 Karma: 3333683 Join Date: Nov 2019 Location: United Kingdom Device: K5, KT, KT2, KT3, KT4, KV, PW2, PW3, PW4, PW5	Looks like you're getting closer now - you should be able to access the Kindle from your Ubuntu PC by setting the IP address of the usb0 interface that appears to 192.168.15.201. The Pi is detecting the interface correctly but is auto-assigning an bogon IP address to the interface because.. reasons? Try setting the IP address to 192.168.15.201 too.

11-15-2021, 10:04 AM	#15
jollyblondgiant Member Posts: 24 Karma: 10 Join Date: Jun 2021 Device: Kindle Touch K5	Final update!! I found that if I run [CODE] [kterm]# ifconfig usb0 192.168.15.244 [kterm]# ssh pi@192.168.15.201 [\CODE] Succeeds! I’m going to modify a bash script to run those two commands before rotating the screen and toggling the keyboard to smoothify setup. Any suggestions for kterm commands to rotate screen/toggle keyboard? The double-tap method works ok but it’s worth trying to shave off the steps

Advert

Advert