[ILUG] routing woes
bernhard.d.rohrer at accenture.com
bernhard.d.rohrer at accenture.com
Thu Aug 25 21:33:11 IST 2005
I must be missing something blatantly obvious, but my new ubuntu box does something very weird when routing.
I have the following network setup:
local LAN - eth0 Ubuntu eth1 - DMZ - router - Irish broadband
local lan is 192.168.1.0
DMZ is 192.168.2.0
my /etc/network/interfaces looks like this:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo eth0
iface lo inet loopback
# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping hotplug
script grep
map eth1
# The primary network interface
iface eth1 inet static
address 192.168.2.100
netmask 255.255.255.0
network 192.168.2.0
broadcast 192.168.2.255
gateway 192.168.2.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers localhost
iface eth0 inet static
address 192.168.1.100
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.2.1 (I have also tried 192.168.2.100 and 192.168.1.100 here - same result)
dns-nameservers localhost
route gives me this:
root at serf:~ # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
localnet * 255.255.255.0 U 0 0 0 eth1
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.2.1 0.0.0.0 UG 0 0 0 eth1
the last line displays after a bit of thinking
route print on a box in the local lan gives:
C:\Documents and Settings\GrayLion>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 50 56 c0 00 08 ...... VMware Virtual Ethernet Adapter for VMnet8
0x3 ...00 50 56 c0 00 01 ...... VMware Virtual Ethernet Adapter for VMnet1
0x4 ...00 50 2c 02 90 7c ...... VIA PCI 10/100Mb Fast Ethernet Adapter - Packet
Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.100 192.168.1.90 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.90 192.168.1.90 20
192.168.1.90 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.90 192.168.1.90 20
192.168.93.0 255.255.255.0 192.168.93.1 192.168.93.1 20
192.168.93.1 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.93.255 255.255.255.255 192.168.93.1 192.168.93.1 20
192.168.244.0 255.255.255.0 192.168.244.1 192.168.244.1 20
192.168.244.1 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.244.255 255.255.255.255 192.168.244.1 192.168.244.1 20
224.0.0.0 240.0.0.0 192.168.1.90 192.168.1.90 20
224.0.0.0 240.0.0.0 192.168.93.1 192.168.93.1 20
224.0.0.0 240.0.0.0 192.168.244.1 192.168.244.1 20
255.255.255.255 255.255.255.255 192.168.1.90 192.168.1.90 1
255.255.255.255 255.255.255.255 192.168.93.1 192.168.93.1 1
255.255.255.255 255.255.255.255 192.168.244.1 192.168.244.1 1
Default Gateway: 192.168.1.100
===========================================================================
Persistent Routes:
None
ipconfig:
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-50-2C-02-90-7C
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.90
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.100
DNS Servers . . . . . . . . . . . : 192.168.1.100
so, I ping my way through the world ;)
C:\Documents and Settings\GrayLion>ping 192.168.1.100
Pinging 192.168.1.100 with 32 bytes of data:
Reply from 192.168.1.100: bytes=32 time<1ms TTL=64
Reply from 192.168.1.100: bytes=32 time<1ms TTL=64
Reply from 192.168.1.100: bytes=32 time<1ms TTL=64
Reply from 192.168.1.100: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\GrayLion>ping 192.168.2.100
Pinging 192.168.2.100 with 32 bytes of data:
Reply from 192.168.2.100: bytes=32 time<1ms TTL=64
Reply from 192.168.2.100: bytes=32 time<1ms TTL=64
Reply from 192.168.2.100: bytes=32 time<1ms TTL=64
Reply from 192.168.2.100: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.2.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\GrayLion>ping 192.168.2.1
Pinging 192.168.2.1 with 32 bytes of data:
Reply from 192.168.2.1: bytes=32 time<1ms TTL=63
Reply from 192.168.2.1: bytes=32 time<1ms TTL=63
Reply from 192.168.2.1: bytes=32 time<1ms TTL=63
Reply from 192.168.2.1: bytes=32 time<1msTTL=63
Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
so far so good, I can ping the router
ping the external interface of the router:
C:\Documents and Settings\GrayLion>ping 87.192.244.10
Pinging 87.192.244.10 with 32 bytes of data:
Reply from 87.192.244.10: bytes=32 time<1ms TTL=63
Reply from 87.192.244.10: bytes=32 time<1ms TTL=63
Reply from 87.192.244.10: bytes=32 time<1ms TTL=63
Reply from 87.192.244.10: bytes=32 time<1ms TTL=63
Ping statistics for 87.192.244.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
ok
ping www.google.ie:
C:\Documents and Settings\GrayLion>ping 66.249.87.99
Pinging 66.249.87.99 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 66.249.87.99:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Documents and Settings\GrayLion>tracert 66.249.87.99
Tracing route to 66.249.87.99 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.100
2 <1 ms <1 ms <1 ms 192.168.2.1
3 * * * Request timed out.
now, if I connect a client PC to the DMZ then everything is fine and dandy.
I am confused. especially since the very same setup worked just fine under suse a few days ago ...
cheers
Bernhard
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
More information about the ILUG
mailing list