View Single Post
Old 06-30-2012, 02:29 PM   #8
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by NiLuJe View Post
The USBNet hack defaults to 192.168.2.1 / 192.168.2.2 on the K2/K3, and 192.168.15.1 / 192.168.15.244 on the K4/K5. (Host / Kindle). Although, on the host side, just being on the same /24 subnet should be enough .
Okay, I was on the wrong subnet for the K2/K3 (I reassign all mine to 10.0.x.1, where each device has a different x so I can plug them in at the same time). The 2 subnet makes more sense so as not to confict with the 1 subnet assigned by many routers.

On the K4/K5 though, the IP address SHOULD really not be 192.16.15.1, or some diags will fail (such as NFS export, etc.). The scripts in the K4/K5 assume that the host is at 192.168.15.201. The wikis are in error on that one (which you can verify in the diags startup scripts, and I have posted this in a number of posts).

So you were right on the K2/K3, and I was right on the K4/K5 (and the K4/K5 hacking wikis are wrong, but would still work except for some diags problems).

And yes, for most cases, anything on the same subnet that is not already in use (the kindle IP in this case) should work fine for the host PC. Beware that you cannot use .0 or .255 for the last IP octet. The only problem would be with certain built-in scripts that look for a host PC at a specific IP address (such as 192.168.15.201).

Last edited by geekmaster; 07-01-2012 at 03:56 AM.
geekmaster is offline   Reply With Quote