On dinsdag 16 augustus 2011 12:38:46 Olipro wrote:
On Tuesday 16 Aug 2011 08:56:41 Freek de Kruijf wrote:
On maandag 15 augustus 2011 22:49:44 Olipro wrote:
Please do not top post, see http://en.opensuse.org/openSUSE:Mailing_list_netiquette
You appear to be the first person to care, I can see several threads right now with upper-level replies.
I do care.
In this case the IPv6 implementation, used in openSUSE, does not properly use the Router Advertisement, when DHCP6 is active. Right at the start of the network service I have seen a Router Solicitation on which a Router Advertisement follows. However this advertisement, with the global IPv6 prefix, is ignored. A second Solicitation and following advertisement is seen and ignored. After that no Solicitation and Advertisement is seen. Only after about 10 minutes an unsolicited Router Advertisement is seen and at that moment the system establishes a global IPv6 address. Without enabling DHCP6 the system gets its global IPv6 address a few seconds after starting the network. See the bug report https://bugzilla.novell.com/show_bug.cgi?id=704666
You can find a Wireshark catched conversation where right at the beginning the RA is present, but is not used. Si I would like to know, because you seem to be more an expert than I am, what your opinion is on the above. You did not comment on this ignoring of the first RAs that the system receives.
This bug has been closed as RESOLVED and marked INVALID so I'm not really sure what conclusion you expect me to draw from it.
This is probably because the title talks about not receiving a global IPv6 address, where later this appears not to be true and the title should be the long delay in establishing the global IPv6 address, which is only solvable by not enabling DHCP6.
Additionally, the author's assertion that DHCPv6 is always stateful is also false; you can have stateless DHCPv6 for assigning DNS, NTP etcetera, one need not assign addresses with DHCPv6 at all.
I was only referring to Stateless _Address_ Allocation. Currently, with IPv4 still around, these other allocations are less important in my view. The received Router Advertisement, also contains other data apart from the global prefix, information on a Recursive DNS Server, the MTU and Source link- layer address.
it *may* contain that information; it depends on the RA implementation; older versions of radvd for example are not capable of RDNSSD - additionally, since some clients also do not support RDNSSD, it can be preferable to include all such information in DHCPv6 - either way, anyone running a network where they have expressly disabled SLAAC for the purposes of ensuring DHCPv6 only assignments (which may be necessary for accounting, hostname assignments or firewall policies) will have an issue if OpenSUSE clients are coming with DHCPv6 disabled.
Considering most other distros and operating systems are providing DHCPv6 clients by default, I don't think this is a road anyone should be taking OpenSUSE down.
openSUSE provides the DHCP6 client OK, but the question is, should the default be that it is enabled in YaST when using the dynamic address allocation as is the default right now (DHCP both version 4 and 6) enabled. I think the majority of the Linux users, with little knowledge, will use a setup like I have, an ADSL router with native IPv6 without a DHCP6 server. In case it takes almost 10 minutes before a global IPv6 address is set in the system, I would prefer not to have DHCP6 enabled in that case. So either this delay should be removed or the default for DHCP6 should be that the DHCP6 client is not activated. I can enter a new bug report about this.
Regards, Oliver
-- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org