Am 21.10.2015 um 11:41 schrieb Kevin Darbyshire-Bryant:
> Ideally those cheap, low margin home router manufacturers will remember
> to put '--bogus-priv' in their configs.
The ideal fix is getting rid of junk by making it unattractive to sell
cheapo gadgets without long-term support.
Ways out
On 20/10/15 21:35, Simon Kelley wrote:
> To add to the list of canonical uses for dnsmasq: DHCP and DNS services
> to VMs and containers in things like OpenStack. These typically use
> RFC1918 addresses (there's no point in being able to spin a new VM in
> seconds if you have to go buy it a real
To add to the list of canonical uses for dnsmasq: DHCP and DNS services
to VMs and containers in things like OpenStack. These typically use
RFC1918 addresses (there's no point in being able to spin a new VM in
seconds if you have to go buy it a real IPv4 address on the black market
first.) so
Hi Simon & list,
Ok, here's the controversial idea. Can we consider enabling
'bogus-priv' by default and have an additional option say 'allow-priv'
to now disable?
My feeling is that not forwarding 'link-local' type requests upstream by
default is a cleaner way of having things configured.
Kevin,
I don't think there is a flaw in your logic. You are probably 50% right.
DNSMASQ is so flexible and useful it has found two significant homes and
a bunch of other neat uses.
Top however, (1) as a single point entry router caching DNS
(ex 192.168.1.1 / X.X.X.X -> 8.8.4.4), and (2) as a
