Quote:
Originally Posted by knc1
Each interface needs to have its own, unique address on the network, its own IP address.
Plus - -
Unless the configuration is changed elsewhere, the Kindle will default to using DHCP for the WiFi interface. The default for the USB network interface is to be set manually.# 95 00
|
<Really dumb look on my face>
Uh, I'm trying to recall references in the READ-ME file to DHCP being activated, and I think that may be an omission in the docs. (Confirmed: a search through USBNet's README-FIRST.txt reveals nothing on DHCP.)
So, although I understand what you're saying, I don't understand it. Two IP addresses to SSH to the Kindle?
Where is the Kindle's IP address set, and where is the interface IP address set? I'm confused. I know this is simple, but I've got a serious case of roadblock square in the middle of my face.
I sort of liken what you're saying to my setup I have on my router to my ISP: they have their WAN address side, and I have my LAN address side, so either side has different IP numbers. Although I understand that one, I don't understand the implication to the SSH configuration necessary.
(I'm not finger-pointing nor blaming. If I can help expand on the README-FIRST file to get better, clearer, more complete docs in place for the software I touch and use, I'm all for it. That's why I went through all the effort on getting this RESOLVED reply added to my OP.)
Quote:
Originally Posted by knc1
Since one of the purposes of pubkey authentication is "password free" authentication, why in the world do you add a passphrase to the private key?
All you've done is replace one passphrase entry point for another.# 95 00
|
I'm forever learning--I just didn't know. Thanks for pointing these things out. Now that you mention it, I
do recall the docs stating something about that in the README-FIRST file.