Having 2 ports connecting to the same subnet - redundancy and speed?
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.
Having 2 ports connecting to the same subnet - redundancy and speed?
Hi guys,
I have a server which has 4 network ports (redundancy purposes). each pair is connected to one subnet. meaning;
eth0 and eth1 connected to 192.168.10.x
eth2 and eth3 connected to 192.168.20.x
while this ensure redundancy (if one down, naturally it will go the other port.. right?), how do I make sure it transfer data via both ports simultaneously? To ensure.. 'speed'.
The speed limit on ethernet is set by the standard. That is, the slowest part of ethernet is actually the speed on the wire, not processing it on the PC, so I can't imagine any situation where it would be desireable to have two NICs transmitting on the same segment.
As for having an automatic backup, that's an interesting idea, but I've never heard of anyone doing it. For one thing, ethernet hardware seems to be reliable--much more reliable than hard disks, for example. For another, I don't know how you would configure it or how you would detect whether a failure is caused by local hardware or by some other hardware on the segment.
To acheive redundancy you need the ports to be running VRRP so that your host address doesn't change when the i/f goes down. That would give you redundancy. To acheive load balancing where you can use both i/f simultaneously you would need to employ bonding. The network device you are connected to also needs to support bonding. Cisco calls this etherchanneling and Nortel calls it trunking.
You can acheive a semblance of load balancing, termed load "sharing" by giving each i/f a different address and have half your hosts talk to one i/f, etc. To do this with redundancy you need to use two vrrp adresses with a different i/f as primary.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.