Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a RHEL 4 update 3 OS, my NIC suddenly stops working and there is no lights flushing (green and orange) if i leave the server for a while (like one hour). But when i do service network restart, life goes back to NIC and all the lights flushing normally and ping works great, but also after a while the NIC dies again.... it needs service network restart every while.
I checked system logs --> kernel: tg3: eth0: link is down.
I also checked the /etc/modprobe.conf, alias eth0 tg3
is the irq number ( set to unknown ) in system-config-network anything to do with this??? or it is a hardware problem or there is any services that blocks the network service after a while, or the OS is frozen and stops the service....
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
I would check to see if NetworkManager service is running. If so disable it and see if that helps.
To check /sbin/service --status-all | grep NetworkManager
/sbin/service Networkmanager stop
/sbin/chkconfig --level 345 NetworkManager off
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
That was my only idea. Based that on RHEL 5 which has NetworkManager service. Just to make sure since you wrote back in all lower case for the name NetworkManager, it is capital N and M in the name.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.