Debian networking help....
in [Linux Networking]
|
From: Enrico on 16 Jun 2010 14:14 Il Wed, 16 Jun 2010 11:03:00 -0700, Shawn ha scritto: > Using those same static settings in a windows machine or OSX machine has > no problem accessing all across the network. I don't think so, because the gateway (aka default router) is the "gateway" to machines outside your local network, identified by IP and netmask addresses. So, your default gateway/router MUST be in your local network. Enrico
From: Tauno Voipio on 16 Jun 2010 14:56 On 16.6.10 9:14 , Enrico wrote: > Il Wed, 16 Jun 2010 11:03:00 -0700, Shawn ha scritto: >> Using those same static settings in a windows machine or OSX machine has >> no problem accessing all across the network. > > I don't think so, because the gateway (aka default router) is the > "gateway" to machines outside your local network, identified by IP and > netmask addresses. So, your default gateway/router MUST be in your local > network. > > Enrico My guess is that the gateway is in the physical local network of the OP. IIRC, Windows and OSX will create a single-host route to the gateway even when it is not in the specified address range directly. -- Tauno Voipio
From: Shawn on 16 Jun 2010 15:01 "So what you could do is set the netmask to 255.255.128.0 and then route add default 146.243.124.1. " When I try: "sudo route add default 146.243.124.1" I get SIOCADDRT: No Such Device with: "sudo route add default gw 146.243.124.1" I get SIOCADDRT: No Such Process "It would indeed be interesting to see the ip addresses, gateways and netmasks used by other equipment on the lan." Another OSX machine for example uses 146.243.56.254 255.255.254.0 Static IP addresses are in the 146.243.56.x and I think 146.243.57.x. AFAIK There are no static routes defined on those machines, I certainly didn't add any to the 146.243.56.254 machine for example. Dynamic addresses are 146.243.124.x and 146.243.125.x ranges. Same netmask and gateway for all. "Is it possible that another gateway in 146.243.56.160/255.255.254.0 is forwarding to 146.243.124.1 for the other computers? " Nothing is configured on the computers and I don't see anything else on a traceroute. Thanks, Shawn
From: Moe Trin on 16 Jun 2010 15:19 On Wed, 16 Jun 2010, in the Usenet newsgroup comp.os.linux.networking, in article <33c5cefe-ea18-49b0-9062-524e3a741ad7(a)u7g2000yqm.googlegroups.com>, Shawn wrote: NOTE: Posting from groups.google.com (or some web-forums) dramatically reduces the chance of your post being seen. Find a real news server. >In /etc/networks/interfaces >iface eth0 inet static >address 146.243.56.160 >netmask 255.255.254.0 >gateway 146.243.124.1 Gateway not on local wire - must be wrong address or mask >The IP address gets assign properly and I can ping anything in the >146.243.56.x range. It appears that Debian doesn't like that the >gateway is in a different addressing range as I can't get past >146.243.56.x. You've said that 146.243.56.0 - 146.243.57.255 is on the eth0 interface. Where is 146.243.124.1? How do you get there? It sure isn't on the local wire, and gateways MUST BE locally reachable. 146.243.0.0/16 is a state IP range, so talk to the network administrator, and find what the _local_ gateway address (it's something in the range 146.243.56.1 - 146.243.57.254) is. >I have many others machines (Macs/Windows) with IP addresses that are >outside of the gateway range and they have no problem. /usr/sbin/traceroute might provide a clue, as would reading and understanding the routing tables on those other systems, but you really should be talking to the network administrator. Old guy
From: Shawn on 16 Jun 2010 15:31
"Gateway not on local wire - must be wrong address or mask " Neither are wrong. "You've said that 146.243.56.0 - 146.243.57.255 is on the eth0 interface. Where is 146.243.124.1?" Same interface. ", and gateways MUST BE locally reachable. " Works fine on OSX and on Windows, and other network devices like printers, iPhones (via a wireless AP)...etc...etc. They may be doing something internally behind the scenes but no extra routing is entered on them by a user. Debian doesn't like it though. Traceroute to 146.243.124.1 from 146.243.56.254 has one hop.... 1) 146.243.124.1 (146.243.124.1) 1.903 ms * 1.755ms Shawn |