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 server with 2 network cards. I want it so that if one of them dies, or can't ping the default gateway for whatever reason, the other card takes over automatically with a minimum of down time. My searches for this haven't come up with anything. I must just be using the wrong keywords, I know something like this must be out there.
At work, on windows, we use some kind of NIC teaming software where they work together as the same virtual card with the same IP. One of them can die without the network going down. I need to be able to implement something like this on the Linux server but I don't know where to look for answers.
Exactly as stated above by jlightner. And MOST of the Google hits are indeed for Debian, but are pretty transportable.
You will find in your kernel sources the C code for 'ifenslave' which needs to be compiled and put into /sbin as a binary, which makes creating the bonded interfaces simple as pie and has built-in --help info.
If you can't work it out and need it for RHEL5 I can dig out the steps I did on RHEL3 which should be fairly close despite the kernel difference (2.4.x vs 2.6.x)
One key difference for RHEL over Debian would be location of network files. They are in /etc/sysconfig/network-scripts (ifcfg-eth0, ifcfg-eth1 etc...)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.