Thomas Haller d512ed9f1f dnsmasq: fix generating shared IPv4 address range ... Change behavior for the network-address and broadcast-address. Users should not specify such addresses, but if they do, generate something more sensible. Also, if the address was in network larger then /24, the generated address range was rather unexpected. Change behavior here. There are no particularly strong reasons for the chosen range. It just seems suitable. The decision to hand out at most a /24 is because it is likely to be plenty, and because that is what the previous code did -- at least, if the address was in the first /24 of the subnet. See how the result for 192.168.0.1/20 is unchanged, but 192.168.1.1/20 changes.		2017-05-29 11:10:36 +02:00
..
tests	dnsmasq: fix generating shared IPv4 address range	2017-05-29 11:10:36 +02:00
nm-dnsmasq-manager.c	dnsmasq: use ipv4.dns and ipv4.dns-search with ipv4.method=shared	2017-03-03 13:51:05 +01:00
nm-dnsmasq-manager.h	build: rename "src/dnsmasq-manager" to "src/dnsmasq"	2016-11-21 14:07:47 +01:00
nm-dnsmasq-utils.c	dnsmasq: fix generating shared IPv4 address range	2017-05-29 11:10:36 +02:00
nm-dnsmasq-utils.h	build: don't add subdirectories to include search path but require qualified include	2016-11-21 14:26:37 +01:00