usbnetwork problems

[tyto alba]

Moderator notice: these posts have originally been posted in the Kubrick thread, but were moved into an own thread because the discussion is off-topic there.
--ixtab


Thaks a lot for all the work you put into it. I just used it to debrick my kindle 4 nt. Worked great!

Except ... after debricking I can no longer ssh into the kindle - "connection refused" (used to work fine without any modifications before I bricked it).

In diags - usbnet mode the Kindle registeres on lsusb as
Bus 001 Device 019: ID 0525:a4a2 Netchip Technology, Inc. Linux-USB Ethernet/RNDIS Gadget

And here is what I belive to be the problem:
Nmap scan report for 192.168.15.244
Host is up (0.00017s latency).
Not shown: 998 closed ports
PORT STATE SERVICE
139/tcp open netbios-ssn
445/tcp open microsoft-ds

I tried the usbNetwork hack from this site but this didnt change anything (visible?). Any sugestions on how to enable ssh/open the port?

Thanks

ta

[ixtab]

First off, welcome to the forum... And - a reminder that you are posting in the wrong thread. You're having a problem with usbnetwork, not with Kubrick. So if you keep having trouble, please post in the usbnetwork thread instead. Anyway...

Originally Posted by tyto alba

Thaks a lot for all the work you put into it. I just used it to debrick my kindle 4 nt. Worked great!

Except ... after debricking I can no longer ssh into the kindle - "connection refused" (used to work fine without any modifications before I bricked it).

In diags - usbnet mode the Kindle registeres on lsusb as
Bus 001 Device 019: ID 0525:a4a2 Netchip Technology, Inc. Linux-USB Ethernet/RNDIS Gadget

Correct so far.

And here is what I belive to be the problem:
Nmap scan report for 192.168.15.244
Host is up (0.00017s latency).
Not shown: 998 closed ports
PORT STATE SERVICE
139/tcp open netbios-ssn
445/tcp open microsoft-ds

That is NOT a Kindle. It's a Windows machine (or possibly a Linux host with only Samba enabled). Chances are that you configured your network incorrectly. The recommended settings (in usbnet/etc/config) are HOST_IP=192.168.15.201, KINDLE_IP=192.168.15.244.

I tried the usbNetwork hack from this site but this didnt change anything (visible?). Any sugestions on how to enable ssh/open the port?

Thanks

ta

Make sure that you are using the latest version of usbNetwork for the K4, and make sure to configure it correctly, and to start it. In other words: READ the instructions that come with usbnetwork. Double-check usbnet/etc/config after installation, and enable it by typing ~usbNetwork. To be extra-careful, make sure that you booted the Kindle with the USB cable DISCONNECTED. (on some Kindles, having the cable connected during startup will cause funky failures when trying to enable usbNetwork, though I'm quite sure that this only affects the K5).

[knc1]

Originally Posted by tyto alba

In diags - usbnet mode the Kindle registeres on lsusb as
Bus 001 Device 019: ID 0525:a4a2 Netchip Technology, Inc. Linux-USB Ethernet/RNDIS Gadget

OK - So your host machine is running Linux.

Originally Posted by tyto alba

And here is what I belive to be the problem:
Nmap scan report for 192.168.15.244
Host is up (0.00017s latency).
Not shown: 998 closed ports
PORT STATE SERVICE
139/tcp open netbios-ssn
445/tcp open microsoft-ds

And that address is (in the Kindle world) used by the K5-Paperwhite, not the K4.

Originally Posted by tyto alba

I tried the usbNetwork hack from this site but this didnt change anything (visible?). Any sugestions on how to enable ssh/open the port?

Thanks

ta

So, by copying my own quote in the "HowTo" threads, with address pair added from the K4 README file:
Note: This presumes that you have KUAL installed along with the USBnetwork control button.)

This order should work on all firmware versions.
Early firmwares, v-2 and v-3 may also work with the cable attached.

• un-plug cable (if still plugged in)
• toggle USBnetwork ON in the KUAL launcher
• plug the cable
• kill any automation (or configure yours to do: )
• sudo ip link set up dev usb0 (It may already be up, no harm in upping it twice)
• [for Kpw]sudo ip address add 192.168.15.201 peer 192.168.15.244 dev usb0
• [for K4] sudo ip address add 192.168.2.1 peer 192.168.2.2 dev usb0
• use the networking until your done (telnet or ssh to the 'peer' address)
• un-plug cable
• toggle USBnetwork OFF in the KUAL launcher

Note 1: You can assign **both** point-to-point link addresses to usb0 - the network stack can deal with that and the "ip" utility will take care of updating the routing tables for you.

Note 2: If you are running devices on a 192.168.x.y network which use the general routing rules, these ptp rules will be tested first. I.E: If your (something) is already using 192.168.2.2 on your local network, the packets for that address will now go to the Kindle. (that address seems popular with router and modem manufacturers)

[ixtab]

Originally Posted by knc1

And that address is (in the Kindle world) used by the K5-Paperwhite, not the K4.

No. The 192.168.2.x addresses are the default configuration shipped with usbnetwork for the K4, which was, and remains, a poor choice IMO. It's the first thing that I correct whenever I install usbnet on a K4.

Why? Not only are the chances of clashing with an existing home network on that subnet MUCH higher than for the 192.168.15.x one, but it also results in requiring different host configurations depending on whether the Kindle is in main or in diags mode: in diags, the Kindle ALWAYS uses 192.168.15.244 - why should that be different in main?

[knc1]

Originally Posted by ixtab

No. The 192.168.2.x addresses are the default configuration shipped with usbnetwork for the K4, which was, and remains, a poor choice IMO. It's the first thing that I correct whenever I install usbnet on a K4.

Why? Not only are the chances of clashing with an existing home network on that subnet MUCH higher than for the 192.168.15.x one, but it also results in the K4 requiring different network configurations in main and diags mode: in diags, it uses 15.244 - why should that be different in main?

Ah, but here we are replying to someone who did not know that USBnetworking has to be "turned on" - - PLUS I added note 2, probably while you where also posting.

Not somebody who has probably read the readme or already changed the configuration file defaults.

My post will "make it work" with the config file defaults as shipped. Which is the reason why I describe using Point-to-Point links rather than trying to route a sub-net.

Once the O.P. learns about the advanced topic of "turn it on, turn it off" -
then we can teach them to pick a better address pair. (192.168.2.x is a REALLY BAD CHOICE - I agree).

PS: Why not move these posts to a new thread?

[ixtab]

Originally Posted by knc1

PS: Why not move these posts to a new thread?

Done

[knc1]

Originally Posted by ixtab

Done

Super!

Nowhere in my USB/SSH "HowTo" posts did I describe how to change the configured address defaults.

I guess I should tackle that topic also.
Phooey! And I thought I was done writing about the USB/SSH/TelNet subject.

Hmm...
**My opinion** is that networked **devices** should be in the 169.254.0.0 (link local) reserved area.
(But then we might still run into HP networked printers.)

Will on this topic some more.
Maybe a KUAL button that re-writes the USBnetworking configuration files?

[tyto alba]

Originally Posted by knc1

Ah, but here we are replying to someone who did not know that USBnetworking has to be "turned on"

Ouch! Stupid me. Once I "turned it on" I got some results .... so far only a "Connection timed out" but at least something I can work on ...

Cheers
ta

[NiLuJe]

Unfortunately, the K4 is using the same code tree as the K2/K3, so it inherited the same defaults we've been using for over four years... FWIW, since that's what I'm used to, I do the exact opposite on my K5/PW: I switch to 'old' default .

That said, I completely agree that on devices with a working USBNet in diags, it's stupid and confusing to use a different default in main. In fact, when I first read this, I though 'wait, I switched the default, didn't I?' But nope, that was on the K5 ˆˆ. There are already a couple of tweaks to the default config made during the install process specifically for the K4, so I could probably switch the default for new installs, it'll just make the doc potentially a bit more confusing.