Bug 587561 - Does not add DHCPv6-learned name servers to /etc/resolv.conf
Does not add DHCPv6-learned name servers to /etc/resolv.conf
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
12
All Linux
low Severity medium
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
:
Depends On:
Blocks: 538499
  Show dependency treegraph
 
Reported: 2010-04-30 05:32 EDT by Tore Anderson
Modified: 2010-05-02 17:39 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-02 17:39:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
/var/log/messages (72.53 KB, text/plain)
2010-04-30 05:32 EDT, Tore Anderson
no flags Details

  None (edit)
Description Tore Anderson 2010-04-30 05:32:27 EDT
Created attachment 410348 [details]
/var/log/messages

This happened in NetworkManager-0.8.0-9.git20100429.fc12.x86_64.

The test network is set up with IPv4 DHCP, IPv6 SLAAC+Information-Only DHCPv6.  Config on the IPv6 router is as follows:

[root@lust ~]# cat /etc/radvd.conf
interface eth0 {
	AdvSendAdvert on;
	AdvOtherConfigFlag on;
	MaxRtrAdvInterval 30;
	prefix 2001:16d8:ee47::/64 {
		AdvAutonomous on;
	};
};
[root@lust ~]# cat /etc/dhcp/dhcpd6.conf
default-lease-time 2592000;
preferred-lifetime 604800;
option dhcp-renewal-time 3600;
option dhcp-rebinding-time 7200;
allow leasequery;
option dhcp6.name-servers  2001:16d8:ee47::d4cb;
option dhcp6.domain-search "fud.no";
option dhcp6.info-refresh-time 21600;
subnet6 2001:16d8:ee47::/64 { }

When booting up the client (F12 with updated NM packages, both IPv6 and IPv4 modes set to Automatic), the connection established successfully, but the resulting /etc/resolv.conf did _not_ contain the expected "nameserver 2001:16d8:ee47::d4cb" line.  I tested booting Windows 7 host (on the same computer), and it had no such problems.

I'm attaching /var/log/messages from the boot.  There's some suspicious-looking error messages from dhclient at 11:07:37...

Tore
Comment 1 Tore Anderson 2010-04-30 06:02:29 EDT
Curiously enough, if I change the network environment to use stateful DHCPv6 and disable SLAAC, like so:

[root@lust ~]# cat /etc/radvd.conf 
interface eth0 {
	AdvSendAdvert on;
	AdvOtherConfigFlag on;
	AdvManagedFlag on;
	MaxRtrAdvInterval 30;
	prefix 2001:16d8:ee47::/64 {
		AdvAutonomous off;
	};
};
[root@lust ~]# cat /etc/dhcp/dhcpd6.conf
default-lease-time 2592000;
preferred-lifetime 604800;
option dhcp-renewal-time 3600;
option dhcp-rebinding-time 7200;
allow leasequery;
option dhcp6.name-servers  2001:16d8:ee47::1234:d4cb;
option dhcp6.domain-search "fud.no";
option dhcp6.info-refresh-time 21600;
subnet6 2001:16d8:ee47::/64 {
	range6 2001:16d8:ee47::aaaa 2001:16d8:ee47::bbbb;
}

NM is able to successfully configure retrieve an DHCPv6 lease and configure it, _and_ correctly configure the DHCPv6-provided DNS server in /etc/resolv.conf.  So this setup works perfectly (only nit I could see is that the "search" field in /etc/resolv.conf contains "fud.no fud.no." - it should probably have removed the duplicate).

Tore
Comment 2 Tore Anderson 2010-05-02 17:39:47 EDT
Appears fixed in NM git20100502.

Note You need to log in before you can comment on or make changes to this bug.