Prev: Cisco PIX 501 - How could I configure a VPN tunnel back to the office
Next: ospf and openvpn
From: Enrico on 17 Jun 2010 05:58
Il Wed, 16 Jun 2010 22:36:38 +0100, Denis McMahon ha scritto:
> Try:
>
> sudo route add host gw 146.243.124.1 eth0 sudo route add default gw
> 146.243.124.1 eth0
>
> Rgds
> Denis McMahon

You are forcing the situation. Why the default gateway is not into the
local IP range?

Enrico
From: Shawn on 17 Jun 2010 08:10
Tauno,

For the Windows machine I set its address to 146.243.56.160
255.255.254.0 gateway of 146.243.124.1. In other words the exact
settings I am trying on the Debian machine. The Debian machine was
shutdown when I did this so no duplication of IP addresses.

This is the output of route print on the Windows machine...

C:\Documents and Settings\Administrator>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 0f 20 73 5a 9f ...... Broadcom NetXtreme Gigabit Ethernet
for hp - Pac
ket Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 146.243.124.1
146.243.56.160 20
127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1 1
146.243.56.0 255.255.254.0 146.243.56.160
146.243.56.160 20
146.243.56.160 255.255.255.255 127.0.0.1
127.0.0.1 20
146.243.255.255 255.255.255.255 146.243.56.160
146.243.56.160 20
224.0.0.0 240.0.0.0 146.243.56.160
146.243.56.160 20
255.255.255.255 255.255.255.255 146.243.56.160
146.243.56.160 1
Default Gateway: 146.243.124.1
===========================================================================
Persistent Routes:
None

As can be seen no static routes are defined on the machine. It has no
problem pinging the default gateway or accessing the Internet.

On the OSX machine (Leopard Server at 146.243.56.254, 255.255.254.0,
gateway 146.243.124.1) netstat -nr gives...

netstat -nr
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif
Expire
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 22 137417 lo0
146.243.56/23 link#4 UCS 5 0 en0
146.243.56.13 8:0:87:b:f0:8f UHLW 0 1 en0
1037
146.243.56.160 0:f:20:73:5a:9f UHLW 0 34 en0
943
146.243.56.162 0:14:22:e5:e6:d9 UHLW 0 30656 en0
942
146.243.56.234 0:23:7d:bd:a9:5c UHLW 0 0 en0
1019
146.243.56.254 127.0.0.1 UHS 0 0 lo0
146.243.57.255 ff:ff:ff:ff:ff:ff UHLWb 0 4 en0
146.243.124.1 0:23:33:65:1e:69 UHLW 0 368 en0
1031
146.243.124.1/32 link#4 UCS 1 0 en0
169.254 link#4 UCS 0 0 en0

Internet6:
Destination
Gateway Flags Netif Expire
::1
link#1 UHL lo0
fe80::%lo0/64
fe80::1%lo0 Uc lo0
fe80::1%lo0
link#1 UHL lo0
fe80::%en0/64
link#4 UC en0
fe80::21b:63ff:fe9f:176a%en0 0:1b:63:9f:
17:6a UHL lo0
ff01::/32 ::
1 U lo0
ff02::/32
fe80::1%lo0 UC lo0
ff02::/32
link#4 UC en0
ff02::fb
link#4 UHLW en0

Likewise this machine has no problem reaching the gateway or machine
it onto the Internet.

Shawn

From: Shawn on 17 Jun 2010 08:35
Hi Denis,

Revisiting this....

"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 changed the netmask and restarted networking this had no
effect.

However upon rebooting with just the netmask changed in the interfaces
file got this working. I did not need to add the route to the
machine.

THANK YOU!!!!!

Shawn
From: Tauno Voipio on 17 Jun 2010 11:04
On 17.6.10 3:10 , Shawn wrote:
> Tauno,
>
> For the Windows machine I set its address to 146.243.56.160
> 255.255.254.0 gateway of 146.243.124.1. In other words the exact
> settings I am trying on the Debian machine. The Debian machine was
> shutdown when I did this so no duplication of IP addresses.
>
> This is the output of route print on the Windows machine...
>
> C:\Documents and Settings\Administrator>route print
> ===========================================================================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x2 ...00 0f 20 73 5a 9f ...... Broadcom NetXtreme Gigabit Ethernet
> for hp - Pac
> ket Scheduler Miniport
> ===========================================================================
> ===========================================================================
> Active Routes:
> Network Destination Netmask Gateway Interface
> Metric
> 0.0.0.0 0.0.0.0 146.243.124.1
> 146.243.56.160 20
> 127.0.0.0 255.0.0.0 127.0.0.1
> 127.0.0.1 1
> 146.243.56.0 255.255.254.0 146.243.56.160
> 146.243.56.160 20
> 146.243.56.160 255.255.255.255 127.0.0.1
> 127.0.0.1 20
> 146.243.255.255 255.255.255.255 146.243.56.160
> 146.243.56.160 20
> 224.0.0.0 240.0.0.0 146.243.56.160
> 146.243.56.160 20
> 255.255.255.255 255.255.255.255 146.243.56.160
> 146.243.56.160 1
> Default Gateway: 146.243.124.1
> ===========================================================================
> Persistent Routes:
> None
>
> As can be seen no static routes are defined on the machine. It has no
> problem pinging the default gateway or accessing the Internet.

The logic in the Microsoft stack evades me ....

> On the OSX machine (Leopard Server at 146.243.56.254, 255.255.254.0,
> gateway 146.243.124.1) netstat -nr gives...
>
> netstat -nr
> Routing tables
>
> Internet:
> Destination Gateway Flags Refs Use Netif
> Expire
> 127 127.0.0.1 UCS 0 0 lo0
> 127.0.0.1 127.0.0.1 UH 22 137417 lo0
> 146.243.56/23 link#4 UCS 5 0 en0
> 146.243.56.13 8:0:87:b:f0:8f UHLW 0 1 en0
> 1037
> 146.243.56.160 0:f:20:73:5a:9f UHLW 0 34 en0
> 943
> 146.243.56.162 0:14:22:e5:e6:d9 UHLW 0 30656 en0
> 942
> 146.243.56.234 0:23:7d:bd:a9:5c UHLW 0 0 en0
> 1019
> 146.243.56.254 127.0.0.1 UHS 0 0 lo0
> 146.243.57.255 ff:ff:ff:ff:ff:ff UHLWb 0 4 en0
> 146.243.124.1 0:23:33:65:1e:69 UHLW 0 368 en0
> 1031
> 146.243.124.1/32 link#4 UCS 1 0 en0
^^^^^^^^^^^^^^^^

Here, there is a point-to-point route to the gateway in an otherwise
inaccessible segment

> 169.254 link#4 UCS 0 0 en0

So, this proves that you're having several different local subnets in
the same physical net, and the default gateway is indeed in the same
local network as the concerned host.

For me, this is still not a RFC-compliant setup.

--

Tauno Voipio
From: Pascal Hambourg on 17 Jun 2010 13:19
Hello,

Tauno Voipio a �crit :
>> ===========================================================================
>> Active Routes:
>> Network Destination Netmask Gateway Interface
>> Metric
>> 0.0.0.0 0.0.0.0 146.243.124.1
>> 146.243.56.160 20
>> 127.0.0.0 255.0.0.0 127.0.0.1
>> 127.0.0.1 1
>> 146.243.56.0 255.255.254.0 146.243.56.160
>> 146.243.56.160 20
>> 146.243.56.160 255.255.255.255 127.0.0.1
>> 127.0.0.1 20
>> 146.243.255.255 255.255.255.255 146.243.56.160
>> 146.243.56.160 20
>> 224.0.0.0 240.0.0.0 146.243.56.160
>> 146.243.56.160 20
>> 255.255.255.255 255.255.255.255 146.243.56.160
>> 146.243.56.160 1
>> Default Gateway: 146.243.124.1
>> ===========================================================================
[...]
> The logic in the Microsoft stack evades me ....

Yup, this looks so wrong... It looks like it assumes a classless mask of
255.255.0.0 (/16) for the directed broadcast address 146.243.255.255.
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5 6
Prev: Cisco PIX 501 - How could I configure a VPN tunnel back to the office
Next: ospf and openvpn