Bug #1057
closeddhclient deletes ifaddr, then fails
0%
Description
Hey,
considering this sequence:
dhclient fxp0
now we have ip address & everything is fine. dhclient keeps running
dhclient fxp0
returns error 1. in syslog, it complains about the address already
beeing taken, because of the running dhlient. However, it will set the
ip address of fxp0 to 0.0.0.0. Now I'm left with an unusable system.
killall dhclient
dhclient fxp0
now it works again.
cheers
simon
Updated by sepherosa over 16 years ago
Use a pid file in /var to lock out multi dhclients on the same interface?
Best Regards,
sephe
Updated by dillon over 16 years ago
:Hey,
:
:considering this sequence:
:
: dhclient fxp0
:
:now we have ip address & everything is fine. dhclient keeps running
:
: dhclient fxp0
:
:returns error 1. in syslog, it complains about the address already
:beeing taken, because of the running dhlient. However, it will set the
:ip address of fxp0 to 0.0.0.0. Now I'm left with an unusable system.
:
: killall dhclient
: dhclient fxp0
:
:now it works again.
:
:cheers
: simon
I think it has always done that. If you run dhclient while one is
already running it explodes the network interface. Feel free to
fix the code :-)
-Matt
Matthew Dillon
<dillon@backplane.com>