01-17-2023, 06:47 AM | #1 |
Junior Member
Posts: 8
Karma: 10
Join Date: Jan 2023
Device: Kindle 4.1.4
|
Struggling with getting a USBNet connection
Hi everyone.
I'm still really struggling with getting USBNet setup and would love some help debugging. Having previously got USB networking up and running, albeit patchily, but having problems with wifi. I now can't connect via USB at all. I've read README_FIRST.txt but must be missing something: I have so far: * Jailbroken my kindle 4NT * installed (via update.bin file) USBNetwork * Installed KUAL * Installed BBB * Set my K4NT a static IP on my router * Blocked my K4NT from accessing the internet * Tried several times to connect via SSH, but failed due to the `no route to host` error * re-installed USBNetwork in case that was the problem * Retried USBNetwork (via the KUAL menu): 1. Edited the config file to add my kindle's static IP to `KINDLE_IP` and to set `USE_OPENSSH="true"` as my distro uses openSSH 2. Toggled USBNetwork via KUAL 3. Checked USBNetwork status (via KUAL) which output `N * USBNetwork: enabled (usbnet, sshd up)` 4. Connected the cable to my PC running KDE Neon (an Ubuntu 22.04 LTS derivative) 5. Opened my terminal emulator on my PC to setup the wired connection 6. Checked for my wired network device name with `ifconfig` and found it to be `enxee4900000000` 7. tried to setup the wired connection to match what the K4NT expects as host, but ran into permission errors ``` ifconfig enxee4900000000 192.168.15.201 SIOCSIFADDR: Operation not permitted SIOCSIFFLAGS: Operation not permitted ``` 8. tried again with `sudo` which looked like it worked: ``` sudo ifconfig enxee4900000000 192.168.15.201 ifconfig (base) enxee4900000000: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.15.201 netmask 255.255.255.0 broadcast 192.168.15.255 inet6 fe80::11ab:af5e:b97b:bc9d prefixlen 64 scopeid 0x20<link> ether ee:49:00:00:00:00 txqueuelen 1000 (Ethernet) ``` 9. Recieved two popups from the system tray (network Manager?) about errors ``` Connection 'Wired connection 1' deactivated. IP configuration was unavailable ``` 10. Needless to say could not connect via ssh `sh: connect to host MY.KINDLE.STATIC.IP port 22: Connection timed out` |
01-17-2023, 08:38 AM | #2 |
Junior Member
Posts: 8
Karma: 10
Join Date: Jan 2023
Device: Kindle 4.1.4
|
Sorry, can't edit the above:
Using the standard config i can now connect via USB - seems the K4 really needs that amazon default IP - though my system seems to fight it and close the connection periodically. Now I'm back to the situation described here Can't ping or connect via wifi. Any idea what I can try to enable that? |
Advert | |
|
01-17-2023, 01:42 PM | #3 |
Grand Sorcerer
Posts: 5,292
Karma: 98804578
Join Date: Apr 2011
Device: pb360
|
Network manager has been wreaking havoc with usbnetwork for years. I've also had trouble with it dropping wifi connections.
My solution is to not install network manager. In /etc/network/interfaces I have: Code:
allow-hotplug enxee4900000000 iface enxee4900000000 inet static address 192.168.15.201 netmask 255.255.255.0 broadcast 192.168.15.255 |
01-23-2023, 12:15 PM | #4 |
Junior Member
Posts: 8
Karma: 10
Join Date: Jan 2023
Device: Kindle 4.1.4
|
Thanks, I'll try that in my config to keep NM under control. That may make the USB connection more stable.
Wifi seems fine, but I need to be on the same SSID (perhaps due to needing to block the K4 from phoning home in my router settings) I've made a different thread about that. |
Tags |
usbnetwork |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Connection issue: content server works / wireless connection doesn't | yunadwb | Calibre Companion | 4 | 07-18-2015 02:49 PM |
Kindle DX y UsbNet | muermo | Amazon Kindle | 7 | 11-30-2013 10:44 AM |
How to connect to kt with usbnet | Emrexcem | Kindle Developer's Corner | 2 | 02-16-2012 02:02 PM |
Dreaming of usbnet | GregorRichards | iRex Developer's Corner | 5 | 06-07-2011 05:14 AM |
Wireless internet connection frustrating IDS connection | Socrates | iRex | 8 | 10-21-2009 12:46 PM |