Network Packet errors after ...up2date

FC4 fedora at browder.us
Thu Aug 4 18:14:40 UTC 2005


I installed FC4 with no issue and it has been running for a month. 
Just got everything running good.  So what did I do?  I selected up2date and pick all. 

Now I get the following network errors. System is running 98% idle..

ifconfig eth0 
eth0      Link encap:Ethernet  HWaddr 00:A0:CC:E6:94:AE  
          inet addr:192.168.20.12  Bcast:192.168.20.255  Mask:255.255.255.0
          inet6 addr: fe80::2a0:ccff:fee6:94ae/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1313 errors:51 dropped:0 overruns:0 frame:17
          TX packets:1360 errors:66 dropped:0 overruns:0 carrier:30
          collisions:0 txqueuelen:1000 
          RX bytes:661901 (646.3 KiB)  TX bytes:117653 (114.8 KiB)
          Interrupt:5 Base address:0x8000 

[root at redhat ~]# uptime
 13:52:51 up 16 min,  3 users,  load average: 0.04, 0.34, 0.32

When I ping the system from another box...  
Reply from 192.168.20.12: bytes=32 time=3995ms TTL=64
Reply from 192.168.20.12: bytes=32 time<1ms TTL=64
Reply from 192.168.20.12: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.20.12: bytes=32 time=714ms TTL=64
Request timed out.
Reply from 192.168.20.12: bytes=32 time=2214ms TTL=64
Request timed out.
Reply from 192.168.20.12: bytes=32 time=2714ms TTL=64
Reply from 192.168.20.12: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.20.12: bytes=32 time=1714ms TTL=64
Reply from 192.168.20.12: bytes=32 time<1ms TTL=64



SSH is unusable as it is to slow. 

I have changed out ethernet cards ,cables and move 
it to another network switch with no change.

Any ideals?   

Thanks.. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20050804/0dd0b9d1/attachment-0001.htm>


More information about the fedora-list mailing list