Eric on 30 Aug 2009 21:10:35 -0700 |
Gordon Dexter wrote: > Eric wrote: >> Once again I'm called on to wear my "network fixer" hat... but this time it's in >> my own office! >> >> I use an internal 10.10.10.0/24 IP range in my home/office. Unfortunately, most >> devices that I'm going to add to the network to configure (wireless routers, >> NAS, etc) have 192.168.[0|1].0/24 addresses. When I plug in the new device and >> try to access it via http or tftp from my Linux workstation - I get nothing. Is >> that because any request outside the 10.10.10.0/24 range falls through the >> routing table to "default" and then gets sent to the gateway - which drops it as >> non-routable? >> >> Thanks, >> Eric >> > Wait a second, why on earth would a NAS device make any assumptions > about the network it's being plugged into? I'd consider that stupid and > broken. That might be ok for a wireless router perhaps--it's a safe > assumption that it's the only router on the network in all but the most > exotic circumstances (namely yours), but who on earth would make a NAS > that gives itself a static IP on first boot instead of using DHCP? Actually, it's used - the previous owner fixed it's IP at 192.168.1.8. I found it at 192.168.1.101 after I reset it but the documentation I've found so far is pretty weak. My DHCP would have put it at 10.10.10.x so I don't know what it's problem is yet. Thanks, Eric -- # Eric Lucas # # "Oh, I have slipped the surly bond of earth # And danced the skies on laughter-silvered wings... # -- John Gillespie Magee Jr ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|