Description of problem: I have IPV6_AUTOCONF=yes specified in /etc/sysconfig/network-scripts/ifcfg-foo. I have: net.ipv6.conf.eth0.accept_ra=1 net.ipv6.conf.eth0.accept_redirects=1 net.ipv6.conf.eth0.autoconf=1 I have radvd configured to contain 'AdvManagedFlag: on': [root@mbooth ~]# radvdump Router advertisement from xxxx::xxxx:xxxx:xxxx:xxxx (hoplimit 255) Received by interface eth0 # Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump AdvCurHopLimit: 64 AdvManagedFlag: on AdvOtherConfigFlag: on AdvHomeAgentFlag: off AdvReachableTime: 0 AdvRetransTimer: 0 Prefix xxxx:xxxx:xxxx:xxxx::/64 AdvValidLifetime: 2592000 AdvPreferredLifetime: 604800 AdvOnLink: on AdvAutonomous: on AdvRouterAddr: off AdvSourceLLAddress: XX XX XX XX XX XX I have dhcp6s configured correctly in this environment (I am currently using an IPv6 address assigned by it). The machine correctly obtains an IP address in the network specified by radvd. However, unless I add DHCPV6C=yes to ifcfg-foo, which starts dhcp6c explicitly on the interface, the stateful protocol is never used. Version-Release number of selected component (if applicable): kernel-2.6.9-42.0.3.EL How reproducible: Always Steps to Reproduce: 1. As above Actual results: Machine obtains IP using stateless protocol, but ignores stateful (DHCPv6). Expected results: Machine obtains IP (and associated network info) using stateful autoconf (DHCPv6).
Are you still experiencing this problem?
No idea.
The current upstream decision is to not invoke dhcpv6 if the managed flag is set. The flag is ignored and a explicit call to a dhcp client is expected in the if-up scripts to achieve stateful autoconf. Therefore I'm closing this bug for now. We may back port this to RHEL5 if it gets implemented upstream.