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.
Hi all,
I currently run a dual-stacked network and would like to say that you *MUST NOT* disable DHCPv6 by default - quite the opposite in fact, both DHCPv4 and v6 need to be enabled from the get-go with appropriate firewall rules.
Having a DHCPv6 client will not (and should not) interfere with SLAAC in any way since Router Advertisements will inform clients as to whether or not there is a running DHCPv6 server - any router that is indicating in RAs that it is running a DHCPv6 server when it in fact is not is effectively *broken* (or criminally misconfigured) and is something that needs to be fixed at source, not worked-around by default-disabling DHCPv6 for everyone else.
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
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.
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.
Regards, Oliver
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org