eth1 is dead

[Rick Stevens]

Michael Weber wrote:
> Hi Rick.  Thanx for the help.
> 
> Here's your additional info:
> 
> 
> 
>>>>rstevens at vitalstream.com 01/05/04 04:48PM >>>
>>
>>I'd recommend "traceroute 172.16.30.32" and verify that the ping is
>>indeed going out eth1.  Also, give us the output of "netstat -rn"
>>(your routing tables).
> 
> 
> # traceroute 172.16.30.32
> traceroute to 172.16.30.32 (172.16.30.32), 30 hops max, 38 byte
> packets
>  1  172.16.30.25 (172.16.30.25)  2991.683 ms !H  2993.419 ms !H 
> 2999.962 ms !H

Uh, uh.  That's bad.

> # netstat -nr
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window 
> irtt Iface
> 66.136.128.232  0.0.0.0         255.255.255.248 U         0 0         
> 0 eth0
> 172.16.30.0      0.0.0.0         255.255.255.0     U         0 0       
>   0 eth1
 > 127.0.0.0       0.0.0.0         255.0.0.0       U         0 0
 > 0 lo
 > 0.0.0.0         66.136.128.238  0.0.0.0         UG        0 0
 > 0 eth0

Uh, I lost track of part of this, but wasn't the netmask on eth1 set
to 255.255.0.0?  ("ifconfig eth1")  If so, then the route table and
the card don't match up.  Shouldn't matter here, as eth1 and the target
machine are on the same subnet as far as THIS machine is concerned.
It rather depends on the netmask on the target machine at this point.
Can you tell us what the target machine's netmask is?
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens at vitalstream.com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
- If at first you don't succeed, quit. No sense being a damned fool! -
----------------------------------------------------------------------