Eric Cooper wrote: > Package: dnsmasq > Version: 2.52-1 > Severity: normal > > I have a second IP address associated with eth0 (the "virtual address" used > by the ucarp daemon): > > # ip addr show dev eth0 > 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast > state UNKNOWN qlen 1000 > link/ether 00:aa:bb:cc:dd:ee brd ff:ff:ff:ff:ff:ff > inet 10.0.0.11/24 brd 10.0.0.255 scope global eth0 > inet 10.0.0.1/24 brd 10.0.0.255 scope global secondary eth0:ucarp > > I want to use this address for dnsmasq, so I use the following config: > listen-address=127.0.0.1 > listen-address=10.0.0.1 > > When I do this, I can get DNS service but not DHCP. > So "dig ... @10.0.0.1" works, but DHCP clients get no response. > Running > dnsmasq -d --log-dhcp > doesn't show any incoming DHCP requests. > > If I just use "interface eth0" instead of the listen-address, or if I use > listen-address=10.0.0.11 > (the "primary" IP address of eth0), then it works OK. >
This situation is rather more complex than it seems at first sight: When a client first turns up on a network, all the DHCP server knows about is the physical network to which it is connected: there's no way to tell if the host is supposed to be on "eth0" or eth0:ucarp" so dnsmasq always assumes the primary address. The current development version of dnsmasq adds an option which tells dnsmasq to assume a named secondary interface instead, which should fix this. Are you in a position to build from source and test this? Cheers, Simon. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
