From: Enrico on
Il Wed, 16 Jun 2010 21:56:08 +0300, Tauno Voipio ha scritto:

> 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.

That's not good. Also, I don't think that any standard say to do that.

Enrico
From: Enrico on
Il Wed, 16 Jun 2010 12:31:20 -0700, Shawn ha scritto:
> 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.

They are configured to use DHCP? Are you sure that they aren't using
another gateway?

> 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

What OS? Can you post your routing table? And, of course, netmask and IP
address?

Enrico
From: Tauno Voipio on
On 16.6.10 10:01 , Shawn wrote:
> "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.


Please go to a working Windows computer and post what

route print

shows (activate cmd.exe and write the command).

Also go to a working Mac and post what

netstat -nr

shows (activate Terminal and write the command).

--

Tauno Voipio


From: Denis McMahon on
On 16/06/10 19:56, Tauno Voipio wrote:
> 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.

maybe:

route add default gw 146.243.124.1 eth0

might also need:

route add host 146.243.124.1 dev eth0

This might solve it, not sure, never tried to do anything this dumb.

Rgds

Denis McMahon
From: Denis McMahon on
On 16/06/10 20:01, Shawn wrote:
> "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

Try:

sudo route add host gw 146.243.124.1 eth0
sudo route add default gw 146.243.124.1 eth0

Rgds

Denis McMahon