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 have observed a strange behavior for my static routes. As of late afternoon my static routes where fine. I came in today and they were gone. I checked uptime. The machine has not rebooted yet all of the routes I had manually configured are gone. Does the kernel after a while reread some file?
Apart from a reboot or some one logging in as root, why else would my static routes disappear from the routing table. (I have 3 network interfaces, all of which are set manually. no DHCP)
This is on FC6 if that helps at all.
You can setup routing at command line as you already know with the route command but that doesn't make them "persistent".
I've not seen this dropout myself but my coworker says he has.
If something happened to the interface (e.g. eth1) that you'd tied the route to (e.g. someone did and ifconfig eth1 down then an ifconfig eth1 up) then the route would drop. If the NIC burped on its own you'd have the same issue.
You can insure the routes are reestablished at boot (or restart of networking) by adding to /etc/sysconfig/network-scripts/route-<interface>
(e.g. route-eth1). Example would be:
That would be the equivalent of the command line:
route add -net 10.0.0.0 netmask 255.0.0.0 gw 10.0.52.54 metric 1