I have an NSLU2 ("slug") network-attached storage box, running nslu2-linux, which was working well until I replaced some hardware in my home network. My current setup is very simple: I have a single box (Motorola SBG6580) which is a combination cable modem and wifi router. A couple of desktop machines, the NAS, and a Vonage box all hang off of this box. The slug is hardcoded to use IP address 192.168.1.77. The router assigns DHCP addresses in the 192.168.0.x range. I'm pretty ignorant about networking, but this actually seems like it should be OK: the hardcoded IP of the slug doesn't fall in the range that the router wants to be able to use for DHCP, so there would be no conflicts. However, I can no longer connect to the slug:
---- rintintin ~ $ ping 192.168.1.77 PING 192.168.1.77 (192.168.1.77) 56(84) bytes of data. From 18.104.22.168 icmp_seq=1 Time to live exceeded From 22.214.171.124 icmp_seq=2 Time to live exceeded From 126.96.36.199 icmp_seq=3 Time to live exceeded From 188.8.131.52 icmp_seq=4 Time to live exceeded ^C
---- rintintin ~ $ ssh firstname.lastname@example.org ssh: connect to host 192.168.1.77 port 22: No route to host
Access to other stuff on the network is fine:
---- rintintin ~ $ ping 192.168.0.3 PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data. 64 bytes from 192.168.0.3: icmp_req=1 ttl=64 time=0.144 ms 64 bytes from 192.168.0.3: icmp_req=2 ttl=64 time=0.095 ms 64 bytes from 192.168.0.3: icmp_req=3 ttl=64 time=0.096 ms ^C
I've clicked around in the router's big, complicated web interface, but haven't found any indications of what might be wrong. Maybe it's set by default to deny access to IP's that aren't of the form 192.168.0.x? Maybe it's set by default to deny access to IP's that aren't ones that it assigned via DHCP? How would one go about diagnosing and fixing this problem?