Red Hat Bugzilla – Bug 81887
dhcpd sends ACK to a renew request received on wrong interface
Last modified: 2008-05-01 11:38:04 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
Description of problem:
DHCPD sends ACK on a renew request on a pool not assigned to an interface
whereas it should send out a NAK.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
configure a dhcp server w/ multiple interfaces (in this case 5)
create pools of addresses for 4 of the 5 and no pool for the 5th.
1. acquire an address from eth0, e.g. 184.108.40.206
2. Disconnect from eth0 network
3. Connect to eth1 network.
4. Client sends a renew 220.127.116.11 to dhcp on eth1
Actual Results: 5. DHCP responds with an ACK out eth1 for 18.104.22.168
Expected Results: DHCP should have sent a NAK out eth1 to the client, then the
client would initiate discovery.
Also seen the ACK and/or NAK getting sent out eth0 and eth4.
eth1 and eth4 share an IRQ, all other adapters have their own IRQ. Is there an
update that takes care of this issue?
redhat 7.1, kernel: 2.4.2-2
Please check Current release of dhcp 3.0 to see if this solves the problem
I believe adding an:
line to the beginning of dhcpd.conf causes the NAKs to be sent out if renew
requests are receieved from clients w/ IPs from other subnets.
This functionality is present in the release mentioned, so upgrading is not
necessary (although I did so).