Red Hat Bugzilla – Bug 20481
pump appears to fail when using DHCP in multiple subnets
Last modified: 2005-10-31 17:00:50 EST
When I configure DHCP for multiple NICs in the same machine and the NICs
are attached to different subnets, only the first NIC learns an address and
comes up. In my test network, I have 2 NICs, one in a 10.10.10.0 subnet and
the other in a 18.104.22.168 subnet. The first NIC comes up, sends a DHCP
discovery frame and gets an address, say 10.10.10.1, from the DHCP server.
A DHCP discovery frame is never sent from the second NIC. Instead, it
appears to broadcast a frame from 10.10.10.1 to 255.255.255.255 (I didn't
have a sniffer handy to see what this broadcast frame was). Eventually,
pump appears to fail and the interface is ifconfig'ed down.
Pump uses UDP Datagram Socket to broadcast DHCP DISCOVERY packets.
When the interfaces are not yet configured with any IP address, BIND is picking
source address from the top of the list of Interface addresses to put in the
This is not a problem on a system with one network adapter. With two or more
dhcp on different subnets, all pump clients will fail except the one on the
first adapter (it's because
pump sends out DISCOVER packets on the second adapter with the source IP address
first adatper. The DHCP server will not see these DISCOVER packet).
Apologies for the unresponsiveness of the previous pump packager...
Does dhcpcd handle multiple interfaces better? It is used in rawhide.
Closing at customer's request.
Close bug for real.