Networking help
Ed Robbins
ed at erobbins.com
Thu Dec 12 15:01:05 EST 2002
Paul,
Can you draw a rough diagram of the layout. In your original post you
refer to them as SystemA, SystemB and SystemC. I find it helpful, to
know the layout with the addresses.
Where does 10.241.38.2 come into play? Is that another multi-homed box
with an interface on the 168.159.36 network?
The first think I noticed was the two default routes, on multi-homed
boxes I only run one default route and then add specific network routes
to handle packets that won't go through the default route. Have you
tried adding a specific route to handle the request, I can't think of a
single case, that I've experienced, in the scenario that you describe
that hasn't come down to a problem in configuring the routing tables.
Ed
On Thu, 2002-12-12 at 14:37, pll at lanminds.com wrote:
>
> Does this make sense to *anyone*?
>
> This information is from a system currently not responding to pings
> (as described previously in the thread).
>
> # ifconfig
> eth0 Link encap:Ethernet HWaddr 00:D0:A8:00:D6:DE
> inet addr:192.168.10.11 Bcast:192.168.10.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:275555 errors:0 dropped:0 overruns:0 frame:0
> TX packets:276739 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:52875228 (50.4 MiB) TX bytes:331924088 (316.5 MiB)
> Interrupt:10
>
> eth1 Link encap:Ethernet HWaddr 00:D0:A8:00:D6:DF
> inet addr:10.241.38.11 Bcast:10.241.38.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:10902420 errors:0 dropped:0 overruns:0 frame:0
> TX packets:8356304 errors:0 dropped:0 overruns:10 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:2088329274 (1.9 GiB) TX bytes:1876519092 (1.7 GiB)
> Interrupt:5 Base address:0x2000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:9818 errors:0 dropped:0 overruns:0 frame:0
> TX packets:9818 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:21383856 (20.3 MiB) TX bytes:21383856 (20.3 MiB)
>
> # netstat -rn
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window irtt Iface
> 10.241.38.0 0.0.0.0 255.255.255.0 U 40 0 0 eth1
> 192.168.10.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0
> 0.0.0.0 10.241.38.1 0.0.0.0 UG 40 0 0 eth1
> 0.0.0.0 192.168.10.1 0.0.0.0 UG 40 0 0 eth0
>
> # ping 168.159.36.90
> PING 168.159.36.90 (168.159.36.90): 56 data bytes
> 64 bytes from 168.159.36.90: icmp_seq=0 ttl=254 time=0.4 ms
> 64 bytes from 168.159.36.90: icmp_seq=1 ttl=254 time=0.2 ms
>
> --- 168.159.36.90 ping statistics ---
> 2 packets transmitted, 2 packets received, 0% packet loss
> round-trip min/avg/ma10.241.38.2x = 0.2/0.3/0.4 ms
> bldsvr:~# ssh -l pll 168.159.36.90
> ssh: connect to address 168.159.36.90 port 22: No route to host
>
> # traceroute 168.159.36.90
> traceroute to 168.159.36.90 (168.159.36.90), 30 hops max, 38 byte packets
> 1 10.241.38.2 (10.241.38.2) 2.563 ms 0.452 ms 0.346 ms
> 2 168.159.36.90 (168.159.36.90) 0.191 ms 0.208 ms 0.177 ms
>
> --
>
> Seeya,
> Paul
> --
> Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE
>
> It may look like I'm just sitting here doing nothing,
> but I'm really actively waiting for all my problems to go away.
>
> If you're not having fun, you're not doing it right!
>
>
> _______________________________________________
> gnhlug-discuss mailing list
> gnhlug-discuss at mail.gnhlug.org
> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
More information about the gnhlug-discuss
mailing list