diff options
| author | Ovidiu Vancea <ovidiu.vancea@ni.com> | 2016-01-06 15:45:01 +0200 |
|---|---|---|
| committer | Joe MacDonald <joe_macdonald@mentor.com> | 2016-01-20 21:41:43 -0500 |
| commit | 28b009f98e93b72efc7b65842cdac140202d9002 (patch) | |
| tree | 12f23aea56b55f26eaf4c1733c4f0727771ea514 /meta-networking | |
| parent | d43819eb0481dd19f83e10542762c944083d9848 (diff) | |
| download | meta-openembedded-28b009f98e93b72efc7b65842cdac140202d9002.tar.gz | |
dnsmasq: Listen only on loopback and disable DHCP
Dnsmasq functions as DHCP and DNS servers by default and listens on all
interfaces. This conflicts with other DHCP or DNS servers already on
the network and corrupts DNS configuration on Windows systems.
We noticed that after installing docker, the Linux system became a
magnet for DNS requests coming from Windows systems. Dnsmasq is a
dependency for lxc which is recommended for docker.
Windows periodically broadcasts DHCPInform and DHCP servers reply with
DHCPAck. If the DHCPAck from the Linux target reaches the Windows
system first, Windows changes its DNS server IP to the Linux system
running dnsmasq. Dnsmasq ends up forwarding the DNS requests to the
official DNS server and replies back the answer to the original
requestor. The Linux system transparently becomes a DNS proxy on the
subnet.
Signed-off-by: Ovidiu Vancea <ovidiu.vancea@ni.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
Diffstat (limited to 'meta-networking')
| -rwxr-xr-x | meta-networking/recipes-support/dnsmasq/files/dnsmasq.conf | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/meta-networking/recipes-support/dnsmasq/files/dnsmasq.conf b/meta-networking/recipes-support/dnsmasq/files/dnsmasq.conf index 1a198a3791..bd0ee001a2 100755 --- a/meta-networking/recipes-support/dnsmasq/files/dnsmasq.conf +++ b/meta-networking/recipes-support/dnsmasq/files/dnsmasq.conf | |||
| @@ -77,7 +77,7 @@ bogus-priv | |||
| 77 | #except-interface= | 77 | #except-interface= |
| 78 | # Or which to listen on by address (remember to include 127.0.0.1 if | 78 | # Or which to listen on by address (remember to include 127.0.0.1 if |
| 79 | # you use this.) | 79 | # you use this.) |
| 80 | #listen-address= | 80 | listen-address=127.0.0.1 |
| 81 | 81 | ||
| 82 | # On systems which support it, dnsmasq binds the wildcard address, | 82 | # On systems which support it, dnsmasq binds the wildcard address, |
| 83 | # even when it is listening on only some interfaces. It then discards | 83 | # even when it is listening on only some interfaces. It then discards |
| @@ -114,7 +114,7 @@ bogus-priv | |||
| 114 | # repeat this for each network on which you want to supply DHCP | 114 | # repeat this for each network on which you want to supply DHCP |
| 115 | # service. | 115 | # service. |
| 116 | #dhcp-range=192.168.0.50,192.168.0.150,12h | 116 | #dhcp-range=192.168.0.50,192.168.0.150,12h |
| 117 | dhcp-range=10.0.0.10,10.0.0.200,2h | 117 | #dhcp-range=10.0.0.10,10.0.0.200,2h |
| 118 | 118 | ||
| 119 | # This is an example of a DHCP range where the netmask is given. This | 119 | # This is an example of a DHCP range where the netmask is given. This |
| 120 | # is needed for networks we reach the dnsmasq DHCP server via a relay | 120 | # is needed for networks we reach the dnsmasq DHCP server via a relay |