Network Oddities -- Failure to Communicate

[Matt Shirel]

Thanks for the reply,  
I was taking the interface down to run the diagnostics b/c I hadn't
found the -f flag.  When I ran with the interface active and the -f flag
I also got a Rx state of "Waiting.." and a Tx state of "Idle"

Matt

Mikkel Ellertson wrote:
> 
> It looks like you don't have the interfaces up.  Send a copy of the
> output of /sbin/ifconfig.  I have the same cards, and the same driver,
> and the output of tulic-diag -fa looks like this:
> 
> [root@gatekeeper /etc]# tulip-diag -fa
> tulip-diag.c:v1.03 5/20/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
> Chip Index #1: Found a DC21140 Tulip card at PCI bus 0, device 10 I/O
> 0xb800.
> Digital DS21140 Tulip chip registers at 0xb800:
>   ffa04800 ffffffff ffffffff 00fff820 00fffa20 fc660000 320e2202 ffffebef
>   e0000000 fffd83ff ffffffff fffe0000 ffffff80 ffffffff 1c09fdc0 fffffec8
>  The Rx process state is 'Waiting for packets'.
>  The Tx process state is 'Idle'.
> Transmit started, Receive started, full-duplex.
>  The transmit threshold is 128.
>  Port selection is MII, full-duplex.
> EEPROM transceiver/media description for the DC21140 chip.
> 
> Leaf node at offset 30, default media type 0800 (Autosense).
>  CSR12 direction setting bits 00.
>  1 transceiver description blocks:
>    MII interface PHY 0 (media type 11).
>  MII PHY found at address 0, status 0x782d.
> 
> Notice the differences?  Rx is 'Waiting for packets' and Tx is 'Idle',
> instead of 'Stopped'.  I only see 'Stopped' if the interface is down.
> 
> Mikkel
>