** Reply to message from Statux <[EMAIL PROTECTED]> on Sat, 25 Nov
2000 00:47:02 -0500 (EST)
> What's the output of ifconfig look like (while we're at it)? :P
Sorry, should have included that in the last post. Not sure how to
flush the stats from ifconfig to start at ground zero (reboot?). They
seem to be persistent over network restarts.
Here is ifconfig output:
eth0 Link encap:Ethernet HWaddr 00:A0:CC:36:DD:1D
inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:610494 errors:2883 dropped:0 overruns:0 frame:0
TX packets:512841 errors:1064 dropped:0 overruns:0
carrier:2128
collisions:10567 txqueuelen:10
Interrupt:11 Base address:0x9000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:831065 errors:0 dropped:0 overruns:0 frame:0
TX packets:831065 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
Txqueuelen throttled down to 10 as suggested by the ifconfig man page
since the LAN is connected to the internet via a (relatively) slow ppp
link. Certainly lots of errors from the suspect hub. Nice loopback, tho
:) Start a ping with the bad hub and get nowhere; but switch it hot and
the ping comes right up. Looks like a bad hub.
jack
Jack Bowling
Prince George, BC
mailto:[EMAIL PROTECTED]
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
