[SOLVED] Wired network drops out frequently in Fedora
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I'm having issues with my wired network. After about 5-10 minutes of turning on my machine, the network will drop out. Sometimes rebooting my pc or router will fix the connection, other times it will have no effect. Also, sometimes the connection will completely disconnect, other times it will appear to be connected (i.e. the network icon will indicate that there is a connection), but trying to ping a remote server or the router will fail.
This problem first showed up on Fedora 11 64, however I've just installed Fedora 13 64 and that hasn't helped. I'm using a brand new NIC (I've tried using the onboard NICs). The machine also has Windows 7 installed, which is able to connect just fine.
Apart from changing NICs, the only other thing I've tried is switching from dhcp to a static IP address.
Any tips or suggestions would be greatly appreciated.
I've tried using my wireless dongle, which also hasn't worked. I'm albe to connect wirelessly for about 5-10 minutes but I'm still disconnected eventually. When I try to re-connect, I'm asked for the password (meaning that I can still the network), but am unable to hook up.
Does anyone have any suggestions or know of any doccuments that deal with these types of issues?
Does anyone have any ideas? I know bumping is looked down upon, but I'm really at a loss. Sometimes I'm able to maintain a connection for an hour, sometimes less than 5 minutes; there's no (obvious) cause for this sort of variance.
Use "iwconfig" and "route" to check the interface settings and the route settings. Read through the kernel messages for the period of time when the problem starts. Consider disabling ipv6. Try to ping the router from another computer on your lan if you have one. Look at the ethtool command to examine your devices settings and capabilities.
Just looking at your kernel.txt there's a whole lot of weird stuff going on with the interrupts and pci bus. I'm on 18.104.22.168 and I don't have half that crap about pci bus & interrupts. The last 4 lines tell you why your connection is dropping
r8169: eth0: link down
r8169: eth0: link up
r8169: eth0: link down
r8169: eth0: link up
One possibility adding these 2 is that the hardware is dropping out in the box - and I would suspect your interrupt setup. You seem to have gone at everywhere else fairly effectively. You have eliminated everything except things shared by eth0 & wlan0. Can you try default safe settings in the bios? And if the interrupts are on 'edge' set them to 'level' and vice versa.
One other possibility is that the terms of connection from your router is not broadcast (like mine)
dhcpIPaddrLeaseTime=604800 in DHCP server response.
dhcpT1value is missing in DHCP server response. Assuming 302400 sec
dhcpT2value is missing in DHCP server response. Assuming 529200 sec
And somehow that's falling over. Does changing the default lease time in your router affect how regularly it falls over?
In my experience, 95% of link down errors are due to bad cables. But since you've not only tried different cables, but different NICs as well, this issue may be a little tougher to troubleshoot than normal. One thing you should try is manually setting the duplex on both ends (router and NIC), do not let the them auto-negotiate.
Also, if "r8169" stands for Realtek 8169 NIC, then you should consider switching NICs again. They are notorious for having link issues in linux. Just google it and you'll see what I mean.