On 02/14/2017 08:40 PM, Alice Wonder wrote:> Well CentOS 7 doesn't use that, and trying to figure out where in the > mess of /etc/sysconfig/network-scripts the problem is occurring has > caused me much frustration.DHCPv6 is really unusual. IPv6 addressing and routing is set up almost entirely in the kernel, unless you're using static addresses. IPv6 is neither harder nor easier with NetworkManager, in my experience.
On 2/15/2017 12:04 AM, Gordon Messmer wrote:> DHCPv6 is really unusual. IPv6 addressing and routing is set up > almost entirely in the kernel, unless you're using static addresses. > IPv6 is neither harder nor easier with NetworkManager, in my experience.It was my understanding that most ipv6 networks don't need DHCPv6, they normally self-configure with 'stateless address autoconfiguration', http://www.ietf.org/rfc/rfc2462.txt -- john r pierce, recycling bits in santa cruz
Once upon a time, Gordon Messmer <gordon.messmer at gmail.com> said:> DHCPv6 is really unusual. IPv6 addressing and routing is set up > almost entirely in the kernel, unless you're using static addresses. > IPv6 is neither harder nor easier with NetworkManager, in my > experience.Not sure about the version in CentOS, but in Fedora, NM disables kernel IPv6 autoconfiguration and "handles" it itself. This means that when I wake up my desktop from sleep, it can take 10-60 seconds to get working IPv6 (vs. the second or so it took the kernel). Progress... -- Chris Adams <linux at cmadams.net>
On 02/15/2017 12:23 AM, John R Pierce wrote:>> DHCPv6 is really unusual. IPv6 addressing and routing is set up >> almost entirely in the kernel, unless you're using static addresses. >> IPv6 is neither harder nor easier with NetworkManager, in my experience. > > It was my understanding that most ipv6 networks don't need DHCPv6, > they normally self-configureYes, that's what I was saying. :)