Kindle Touch/PW1/PW2 5.0.x - 5.4.4.2 JailBreak. Plus FW 5.x USBNetwork.

[nasser]

Originally Posted by Cinisajoy

I am not sure but I am trying to find you the answer.
Oh and you accidentally posted in the PW1 thread.

Thanks, Cinisajoy!
Geekmaster has suggested I use mrpi.
Regarding posting in PW1 thread.. well, the file does say pw3(and kv) in its name..?
Couldn't find a dedicated PW3 thread for usbnetwork too..

[NiLuJe]

@nasser: Definitely in the right place. It's a dual-purpose thread .

[nasser]

Originally Posted by NiLuJe

@nasser: Definitely in the right place. It's a dual-purpose thread .

Thanks, NiLuJe!
Have now installed Usbnetwork using MRPI on my PW3.
Now to try it out...

[nasser]

Trying to make Usbnw work on PW3.
From my old PW1 notes, I have the command:
sudo ip address add 192.168.15.201 peer 192.168.15.244 dev usb0
But I've already set up my PW1 as 192.168.15.244. Have added it to hosts, etc. If I proceed further, I get the Linux message that the destination has changed, somebody may have tampered, etc.
Tried changing 244 to 245.. Didn't seem to work.
Request help from NiLuJe and other wizards..!

[geekmaster]

Same IP addr, different MAC addr, okay to ignore errors and use it anyway.

[knc1]

Originally Posted by geekmaster

Same IP addr, different MAC addr, okay to ignore errors and use it anyway.

You should carefully inspect the entire length of the USB cable to ensure no one is wire-tapping it, but otherwise ^^^

[nasser]

Ok.. Maybe I wasn't specific enough.. Here's the full message:

nasser@nasser-nb-ub:~$ ssh 192.168.15.244
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
d4:17:62:24:ed:1f:02:a8:cc:43:29:d8:c0:0f:2a:cc.
Please contact your system administrator.
Add correct host key in /home/nasser/.ssh/known_hosts to get rid of this message.
Offending RSA key in /home/nasser/.ssh/known_hosts:1
remove with: ssh-keygen -f "/home/nasser/.ssh/known_hosts" -R 192.168.15.244
RSA host key for 192.168.15.244 has changed and you have requested strict checking.
Host key verification failed.

I want to retain the set up for my PW1.. I've already done the shared keys, hosts entry stuff for it.
How can set up a new I.P for the PW3?

[geekmaster]

Originally Posted by nasser

Ok.. Maybe I wasn't specific enough.. Here's the full message:

I want to retain the set up for my PW1.. I've already done the shared keys, hosts entry stuff for it.
How can set up a new I.P for the PW3?

That happens with multple devices sharing an IP address. If it annoys you, modify the kindle usbnet config so each kindle gets unique MAC and IP addresses.

[Cinisajoy]

Originally Posted by geekmaster

That happens with multple devices sharing an IP address. If it annoys you, modify the kindle usbnet config so each kindle gets unique MAC and IP addresses.

Confused on your IP comment. Every one of my devices has a different IP address.

[geekmaster]

Originally Posted by Cinisajoy

Confused on your IP comment. Every one of my devices has a different IP address.

Talking about multiple kindles at 192.168.15.244, as nasser mentioned (PW1 and PW3). They both identify as the same device, but have different certs, hence the "potential MITM" warning. The cached cert keeps changing when swapping devices, which triggers that warning. Because in a sane world, certs should not change unexpectedly. But we do expect this on kindles sharing a default network identity, so just an annoyance. As I said, it can be resolved with a custom usbnet config in the kindle(s). Even more convenient to use my 'mntusb' script so you can use multiple kindles over USB at the same time, automagically.

Read these for details:
https://www.mobileread.com/forums/sho....php?p=2056931
https://www.mobileread.com/forums/sho....php?p=1906267
https://www.mobileread.com/forums/sho....php?p=1841893

[Cinisajoy]

Originally Posted by geekmaster

Talking about multiple kindles at 192.168.15.244, as nasser mentioned (PW1 and PW3). They both identify as the same device, but have different certs, hence the "potential MITM" warning. The cached cert keeps changing when swapping devices, which triggers that warning. Because in a sane world, certs should not change unexpectedly. But we do expect this on kindles sharing a default network identity, so just an annoyance. As I said, it can be resolved with a custom usbnet config in the kindle(s). Even more convenient to use my 'mntusb' script so you can use multiple kindles over USB at the same time, automagically.

Read this for details (and a link):
https://www.mobileread.com/forums/sho...31#post2056931

I just found it odd because my kindles are 192.xx.x.xx× & 192..xx.x.xyy.
On the IPs.

[geekmaster]

Originally Posted by Cinisajoy

I just found it odd because my kindles are 192.xx.x.xx× & 192..xx.x.xyy.
On the IPs.

Not automatically assigned (no DHCP server in the kindles). Your host OS cached whatever YOU typed in when you configured that usbnet/RNDIS interface on your host PC the first time you plugged in your kindle (to that particular USB part, on some OS versions).

The variable oddness factor was your own personal choice each time (or those of whomever configured the RNDIS network connections for you).

But you are discussing the host PC side of the connection, whilst we are discussing the kindle side of the connection (the ssl cert index cached on your host), so apples and oranges...

I updated the links in my previous post so no need to click through a series of posts. Check them out above to help eliminate confusion (and learning helps keep your brain young).

[Cinisajoy]

Originally Posted by geekmaster

Not automatically assigned (no DHCP server in the kindles). Your host OS cached whatever YOU typed in when you configured that usbnet/RNDIS interface on your host PC the first time you plugged in your kindle (to that particular USB part, on some OS versions).

The variable oddness factor was your own personal choice each time (or those of whomever configured the RNDIS network connections for you).

But you are discussing the host PC side of the connection, whilst we are discussing the kindle side of the connection (the ssl cert index cached on your host), so apples and oranges...

I updated the links in my previous post so no need to click through a series of posts. Check them out above to help eliminate confusion (and learning helps keep your brain young).

Oops miscommunication. Sorry Spock. I was referring to the IP listed on ISP page.
Everything ever connected has a separate IP.

[geekmaster]

Originally Posted by Cinisajoy

Oops miscommunication. Sorry Spock. I was referring to the IP listed on ISP page.
Everything ever connected has a separate IP.

ISP page? Internet Service Provider? What has that got to do with kindles and USB networking?

Though I suppose with no dhcpd on the kindles, we COULD give the kindles 169.254.x.x addresses and let the host OS find them in the default "no DHCP server" range (except for those diags requirements I listed in one of those links above).

[knc1]

@geekmaster:
cinisajoy has some sort of funky ISP controlled setup out there in west Texas that I never did figure out, last time she had problems with it.

And then there is West Texas Microwave -
I don't even want to remember about that one now.