Hide Forgot
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) Description of problem: Ethernet connection crawls on FC2 box. ifconfig reveals RX frame errors for almost every packet. FC2 fresh install connected via cat5 cable to d-link di-624 router. windows box connected to same router works fine and fast. Bypassing router and hooking FC2 directly into cable modem alleviates the problem. Also, I have switched cables, ports on the router, etc. It seems, then, that the problem is not hardware based, and is not in the router itself, but somewhere in my FC2 machine. I have changed configs several times via system-config-network but have been unable to fix the problem. I have also messed with the router ad nauseum, and have reset it to factory settings and set it back up (the windows box works as expected through the router). I can ping the router (192.168.0.1) and the windows box (192.168.0.102) with adequate ping times (.2-.4ms) - the FC2 machine is 192.168.0.101. the FC2 machine seems to connect to the router, and receives an IP address via DHCP, but still does not resolve hosts, load pages, etc., at a reasonable rate. Connections worked fine on previous FC versions. Thanks for the help! Version-Release number of selected component (if applicable): kernel-smp-2.6.6-1.435.2.3 How reproducible: Always Steps to Reproduce: 1. open any internet browser 2. try to load any webpage 3. Actual Results: Eventually, page may load, slowly. Even sites made to load quickly, like yahoo.com, take forever. The yahoo logo itlsef took several minutes. Expected Results: web pages load at reasonable rate for cable modem. Additional info: Attached ifconfig and netstat -nr output.
Created attachment 102084 [details] Text file output from ifcongif and netstat
Fedora Core 2 has now reached end of life, and no further updates will be provided by Red Hat. The Fedora legacy project will be producing further kernel updates for security problems only. If this bug has not been fixed in the latest Fedora Core 2 update kernel, please try to reproduce it under Fedora Core 3, and reopen if necessary, changing the product version accordingly. Thank you.