Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Do you use some "standard" solution to manage your server connectivity? In particular, how do you ensure that, week after week of uptime, your LAN remains connected, even if the router should reboot or other temporary problem should occur?

Since some years, I've arranged this using a custom script (loaded by init) which periodically pings the router, and in case it doesn't reply, a reconnection is attempted.

But I wonder if the norm is to write a custom script like this by yourself, or if there is some standard solution ready to go.

share|improve this question
Use quality server and networking equipment. There shouldn't be a need to write additional scripts for this. What types of problems are you trying to protect against? – ewwhite Jan 3 '13 at 1:54
Some years passed since I deployed this script, but I think that, without it, the NIC-to-router connection wasn't guaranteed to restore in case the router rebooted (eg. powerfailure). – davide Jan 3 '13 at 1:57
What do you mean by a "reconnection"? – David Schwartz Jan 3 '13 at 2:24
With "reconnection" I mean ifup ${iface_name}. – davide Jan 3 '13 at 2:26
@davide: There's no reason you should ever need to do that. I would suggest you troubleshoot to figure out what problem that's working around and then fix it for real. – David Schwartz Jan 3 '13 at 2:39
up vote 6 down vote accepted

In short: there is no such thing as a "standard solution" to this problem solely because of the fact that it is not a "standard" problem.

With a modern OS and sane network equipment, there is no need to do anything to ensure the network connection stays up, nor should any "custom script" be required to bring things up after a power outage or other unexpected disconnection.

If you are finding that connections are not being re-established after an unexpected disconnection, then you need to do further troubleshooting to determine the source of the issue.

As an aside, you ought to have some sort of external monitoring in place to detect and alert on events like this.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.