On 05-22-2013 10:06, Alexandre DERUMIER wrote:
An idea. What about create an extra tap on each host which dnsmasq listens on. This tap should then be connected to every bridge on the host.If the daemon listen to 192.168.10.1, I can't see the DHCPDISCOVERY packet.I need to listen to 0.0.0.0.
For lease files we could use the same concept behind pve-cluster. Configuration and lease files are shared within the cluster using pmxcfs it will however, require implementing the POSIX file locking features in pmxcfg. dnsmasq is by design thread safe since numerous worker processes uses the same lease files and to achieve this dnsmasq uses POSIX file locking features like 'exclusive lock' when updating and 'shared lock' when reading.
-- Hilsen/regards Michael Rasmussen
<<attachment: vcard.vcf>>
_______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
