Rapinapof
Posts: 4
Joined: Fri Aug 28, 2015 7:30 am

static eth0 interface does not receive IP after hotplug

Fri Aug 28, 2015 8:09 am

Hello,

Raspberry Pi is used as a DHCP server for a network.
When the router is restarted, Rasberry Pi lost the IP address of eth0 and does not recover it.
However the packet arrives to eth0, because the DHCP server complains that it receives them but it cannot answer because of the lack of address for eth0.
Only a reboot of Raspbian does a recovering of this IP.

I have added allow-hotplug but without succeed.

Do you know how to give back automatically this address without a rebooting?

It is an updated Raspbian Jessie.
$cat /etc/network/interfaces
auto lo

iface lo inet loopback
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.16
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1

Regards.

per-SM
Posts: 8
Joined: Sun Nov 23, 2014 5:31 pm

Re: static eth0 interface does not receive IP after hotplug

Wed Sep 02, 2015 11:38 am

Try "sudo ifdown -a" and "sudo ifup -a". That has worked for me in the past.

User avatar
allfox
Posts: 452
Joined: Sat Jun 22, 2013 1:36 pm
Location: Guang Dong, China

Re: static eth0 interface does not receive IP after hotplug

Wed Sep 02, 2015 12:16 pm

Please try: sudo apt-get purge ifplugd

Rapinapof
Posts: 4
Joined: Fri Aug 28, 2015 7:30 am

[SOLVED] static eth0 interface does not receive IP after hot

Thu Sep 03, 2015 8:07 am

allfox wrote:Please try: sudo apt-get purge ifplugd
Thank you for your answers, per-SM and allfox.

Wicd was installed and running but useless. I do not know if this issue was from both wicd and ifplugd or one of them, but I removed wicd and now all work fine.

Thank you, allfox, for helping me to track this issue.

Rapinapof
Posts: 4
Joined: Fri Aug 28, 2015 7:30 am

Re: static eth0 interface does not receive IP after hotplug

Wed Sep 09, 2015 4:26 pm

This issue is known by Debian and a report is yet published here :
https://bugs.debian.org/cgi-bin/bugrepo ... bug=557156
with a workaround here :
https://bugs.debian.org/cgi-bin/bugrepo ... =557156#22.

Return to “Advanced users”