Dan Williams 12d96c30f2 core: capture DNS configuration from resolv.conf when generating connections ... If the interface who's IP configuration is being captured has the default route, then read DNS servers from resolv.conf into the NMIP[4|6]Config. This allows NetworkManager to repopulate resolv.conf if anything changes. For example, if the system does not define a persistent hostname, then when a device which has generated a connection activates, a hostname lookup will be performed. The results of that lookup may change resolv.conf, and thus NetworkManager must rewrite resolv.conf. Without capturing DNS information at startup when generating connections, an empty resolv.conf would be written.		2013-11-22 15:01:10 -06:00
..
Makefile.am	core: capture DNS configuration from resolv.conf when generating connections	2013-11-22 15:01:10 -06:00
test-dcb.c	core: add dcbtool manipulation logic	2013-10-31 13:29:22 -05:00
test-dhcp-options.c	coverity: fix various warnings detected with Coverity	2013-11-13 15:29:24 +01:00
test-ip4-config.c	core: add const qualifier to functions in nm-ip[46]-config	2013-09-24 18:31:34 +02:00
test-ip6-config.c	core: add const qualifier to functions in nm-ip[46]-config	2013-09-24 18:31:34 +02:00
test-policy-hosts.c	tests: clean up gtester usage	2013-02-26 13:07:33 +01:00
test-resolvconf-capture.c	core: capture DNS configuration from resolv.conf when generating connections	2013-11-22 15:01:10 -06:00
test-secret-agent.py	use /usr/bin/env instead of /bin/env	2011-03-29 01:00:47 +02:00
test-wifi-ap-utils.c	core: remove 'wep40' and 'wep104' from several places in NM	2013-09-18 12:07:29 +02:00