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.
Following are my load balance server result
10.243.49.0/29 dev eth1 proto kernel scope link src 10.243.49.3
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.254
10.160.64.0/21 dev eth2 proto kernel scope link src 10.160.65.234
169.254.0.0/16 dev eth2 scope link
nexthop via 10.243.49.1 dev eth1 weight 1
nexthop via 10.160.64.1 dev eth2 weight 1
Chain PREROUTING (policy ACCEPT)
num target prot opt source destination
what about something (daemon) that monitors the connections and changes the route when they go up and down? Or using a full routing daemon one that handles bgp or ospf (though that seems like overkill)?