> 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?
I built dnsmasq-2.53test22 in a lenny chroot and tried it. I assume you mean the new interface prefix to DHCP ranges? (There are a couple typos in the section of the man page describing that feature: s/inteface/interface/, s/them/then/) I had been using "bind-interfaces", which (silently) conflicts with this option. Apparently it will only work with wildcard-bound sockets? Also, my goal in using the aliased interface in the first place was so that the DHCP replies would contain that address for the router and dns-server options, but it doesn't (unless I override them). Dnsmasq is still using the address of the primary (eth0) interface for both these fields, and for the server-identifier field. -- Eric Cooper e c c @ c m u . e d u -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
