eth1 is dead
Rick Stevens
rstevens at vitalstream.com
Tue Jan 6 21:51:50 UTC 2004
Michael Weber wrote:
>
>>>>>rstevens at vitalstream.com 01/06/04 11:25AM >>>
>>
>>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?
>
>
> Here's the short version. I played with the netmasks trying to get the
> thing working. Both netmasks are now 255.255.255.0, and it still
> doesn't work.
>
> Since my last post, I swapped the configs in
> /etc/sysconfig/network-scripts. Now the 172 address is using eth0 and
> the 66 address is using eth1. Even with the hardware swappind addresses
> it is still the 172 link that is dead. This takes all hardware issues
> out of the loop, right? It has to be something in the 172 routing that
> is munged.
>
> I still have all firewalling turned off, routes look fine, but no
> pingy-pingy. Or arpy-arpy for that matter. The card never responds
> with an arp-reply which is why the traceroutes get !H's.
Ok, let's get to basics.
1) Do you have a link LED lit up on the bad card?
2) Is the non-working card plugged into a switch or hub, or is it
directly plugged into the other machine? If it's plugged into the other
machine, you need a crossover network cable.
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer rstevens at vitalstream.com -
- VitalStream, Inc. http://www.vitalstream.com -
- -
- "I understand Windows 2000 has a Y2K problem." -
----------------------------------------------------------------------
More information about the users
mailing list