On 27/03/12 15:18, Simon wrote:
> The strange packets have source address 0.0.0.0 and/or destination > address 255.255.255.255. When an socket is bound to a particular > address, it may not receive these packets. Some kernels work fine, > but it's really moving into undefined territory and portable code > which works everywhere is much easier when binding the wildcard. As an example of the sort of trouble you can get into with this, imagine a physical network interface with two IP addresses, say 192.168.1.1 and 192.168.2.1 Now start two different instances of a DHCP server, one bound to 192.168.1.1 and the other bound to 192.168.2.1 A client on the network attached to the interface now starts DHCP by broadcasting to 255.255.255.255. Which DHCP server instance should reply? Cheers, Simon. _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
