Red Hat Bugzilla – Bug 243652
Network Manager doesn't change address when DHCP lease expires
Last modified: 2008-08-02 19:40:36 EDT
Description of problem:
If the DHCP lease expires and the DHCP server requests an address change, the
address bound to the NIC is not changed. (This may be better filed against
dhclient, but the dhclient package doesn't appear to be in the bugzilla package
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Use NetworkManager to acquire a lease from the DHCP server
2. When the lease expires, have the DHCP server NAK the renewal and lease a
different IP address instead.
3. using "ip ad", observe that the NIC is still bound to the old IP instead of
the new IP.
The below log shows a lease of 22.214.171.124 being made and then the IP address
being changed to 126.96.36.199. Everything appears to be correct, but the
interface remains bound to 188.8.131.52.
Jun 11 09:35:38 atlantis dhclient: DHCPREQUEST on eth0 to 184.108.40.206 port 67
Jun 11 09:35:38 atlantis dhclient: DHCPACK from 220.127.116.11
Jun 11 09:35:38 atlantis NetworkManager: <info> DHCP daemon state is now 3
(renew) for interface eth0
Jun 11 09:35:38 atlantis dhclient: bound to 18.104.22.168 -- renewal in 13 seconds.
Jun 11 09:35:51 atlantis dhclient: DHCPREQUEST on eth0 to 22.214.171.124 port 67
Jun 11 09:35:51 atlantis dhclient: DHCPNAK from 126.96.36.199
Jun 11 09:35:51 atlantis NetworkManager: <info> DHCP daemon state is now 10
(unknown) for interface eth0
Jun 11 09:35:51 atlantis dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port
67 interval 7
Jun 11 09:35:51 atlantis NetworkManager: <info> DHCP daemon state is now 1
(starting) for interface eth0
Jun 11 09:35:51 atlantis dhclient: DHCPOFFER from 188.8.131.52
Jun 11 09:35:51 atlantis dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jun 11 09:35:51 atlantis dhclient: DHCPACK from 184.108.40.206
Jun 11 09:35:51 atlantis NetworkManager: <info> DHCP daemon state is now 2
(bound) for interface eth0
Jun 11 09:35:51 atlantis dhclient: bound to 220.127.116.11 -- renewal in 1603
"ip ad" shows:
inet 18.104.22.168/25 brd 22.214.171.124 scope global eth0
The NIC should be bound to the new IP address
Does this happen when not using NetworkManager?
Also, what version of dhcdbd are you running?
This happens without NetworkManager too.
Also when rebooting computer NIC takes old ip (from
/var/lib/dhclient/dhclient-eth0.leases ?). Running "/sbin/dhclient -1 eth0"
assings correct ip.
$ rpm -q dhcdbd
i'm seeing this as well with dhclient-3.0.5-38.fc7 and dhcdbd-2.7-5.fc7. i
noticed this because i use ip passthrough on my router and when the router
address changes, my eth0 does not. if i deactivate/activate, eth0 gets the
address. i didn't have to go through this with fc6.
Is this happening on an Fedora 8 Test release or with rawhide?
Unfortunately I'm not in a position to test this at the moment.
Created attachment 233401 [details]
message log for dhcp test
still not working for me on fc8t3 live cd w/no updates. i've sent my messages
log. seems like it should be working from what is in messages, however when i
do an ifconfig, the interface still shows the original address obtained when
first booting the livecd. at the end of the log you can see where i
deactivated/activated the interface in order to get the correct address.
Is this happening with rawhide now? I have dhcp-4.0.0 in the tree now and would
like to know if this is still happening to you.
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.
Setting status to "CLOSED INSUFFICIENT_DATA". If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.
Thank you in advance.
Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9.