Debian PC unpingable after reboot

[Syphonx]

So I've just set up a media server running Debian 8.5 and I'm still working out a few kinks. The server is headless so all access is remote. However it seems that when my router gets rebooted I cannot ping the server afterwards or access it. I have set the router to reserve the server the same IP. (have the same for my windows PC's and they work fine after a reboot of the router). I then have to powercycle the server to get it accessible again. Any ideas on why this is happening?

 

[Mr Scratch]

So I've just set up a media server running Debian 8.5 and I'm still working out a few kinks. The server is headless so all access is remote. However it seems that when my router gets rebooted I cannot ping the server afterwards or access it. I have set the router to reserve the server the same IP. (have the same for my windows PC's and they work fine after a reboot of the router). I then have to powercycle the server to get it accessible again. Any ideas on why this is happening?

Set a static IP on the box instead. Docs: https://wiki.debian.org/NetworkConfiguration

 

[Drake2007]

You may have some networking services running on the server that may interfere with the router reboot such as dhcp or dnsmasq. Check dmesg log

 

[KleinBoontjie]

wake on lan?

 

[Syphonx]

Set a static IP on the box instead. Docs: https://wiki.debian.org/NetworkConfiguration

I'm contemplating that but would try fix this first.

You may have some networking services running on the server that may interfere with the router reboot such as dhcp or dnsmasq. Check dmesg log

I had a look but not sure what exactly I should be looking for in there. I have not made any changes to network settings since install, only installed a few docker images.

wake on lan?

I don't believe that is enabled, or at least I haven't enabled it myself

 

[sicelo.m]

I then have to powercycle the server to get it accessible again. Any ideas on why this is happening?

If you want to solve it (instead of, for example, setting static IP on box), inspect the logs.

 

[garyc]

Wired or wireless? The reason I ask is that I have seen some wireless configurations that are reluctant to re-connect is the router is re-booted and need to have the power cycled.

 

[Syphonx]

Wired or wireless? The reason I ask is that I have seen some wireless configurations that are reluctant to re-connect is the router is re-booted and need to have the power cycled.

It's wired.

 

[shadow_man]

I had this issue with an older Debian box too. It turned out to be the gateway that was at fault - it seemed to forget that the box existed at some point.

All I made it do was ping the gateway every once in a while.

Set a crontab for every 5 mins or so:

1.) crontab -e

Then add in:

2.) 5 * * * * ping -c5 yourgatewayip

 

[Syphonx]

Ok I believe I have fixed it, for reference I added the following to /etc/network/interfaces

auto eth0
allow-hotplug eth0
iface eth0 inet dhcp

https://wiki.debian.org/NetworkConfiguration