-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, in openstack neutron, we experience the following bug : For a port, if we configure both a stateful (dhcp4 or dhcpv6-stateful) address AND a dhcpv6-stateless address with an extra dhcp option assigned, then neutron dhcp agent fails to
Simon Kelley (si...@thekelleys.org.uk) wrote on Thu, Jun 18, 2015 at 06:28:08AM BRT: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 If you could do a quick check and see if 2.73rc9 behaves the same way, that would be useful. The change most likely to have provoked this happened after rc9.
Hi All Functions and conditions used in dnsmasq while choosing the entry in hosts file for a MAC address request - https://github.com/guns/dnsmasq/blob/nerv/src/dhcp-common.c#L275 https://github.com/guns/dnsmasq/blob/nerv/src/dhcp-common.c#L287
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 223 interfaces is quite impressive! Let's try and debug at your end rather than reproduce the bug here for now. Next test: start dnsmasq with the -d flag, and see what happens. Next next test: start dnsmasq -d under strace and post the large
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As Albert says, the whole thing is explained by the printer getting an IP address other than the one you configured for it. Looking in the logs for what happened during that event is the key to this. Cheers, Simon. On 18/06/15 08:08, Albert
Hi B. Cook, Le Wed, 17 Jun 2015 15:21:59 -0400, B. Cook bc...@poughkeepsieschools.org a écrit : 2.72 on CentOS 6.x latest.. not giving name hp6-216.phs.pcsd to the DHCP lease of 10.20.13.116 because the name exists in /etc/dnsmasq.d/hosts with address 10.20.15.234 This is the literal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 If you could do a quick check and see if 2.73rc9 behaves the same way, that would be useful. The change most likely to have provoked this happened after rc9. Cheers, Simon. On 17/06/15 22:32, Carlos Carvalho wrote: I tried 2.73 today but it