Your message dated Thu, 23 Jun 2022 15:32:59 -0700
with message-id <YrTqG/2TTX8U4qa/@doom.morgul.net>
and subject line Re: Bug#794571: network-manager: Disables
net.ipv6.conf.<interface>.accept_ra if IPv6 method is set to "Automatic, DHCP
only"
has caused the Debian Bug report #794571,
regarding network-manager: Disables net.ipv6.conf.<interface>.accept_ra if IPv6
method is set to "Automatic, DHCP only"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
794571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794571
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 1.0.4-1
Tags: ipv6
For a specific wifi connection I know that IPV6 SLAAC won't succeed but
DHCPv6 will. So I've set the "Method" to "Automatic, DHCP only" under
"IPv6 Settings".
The interface also gets the expected IP addresses, but routes are no
more set because net.ipv6.conf.wlp3s0.accept_ra is unexpectedly set to
0.
This doesn't make sense at all, because with DHCPv6 routes are still
announced by the routers. DHCPv6 does not even have support for
announcing routes.
So please stop setting net.ipv6.conf.*.accept_ra on the according
interface if the IPv6 method is set to "Automatic, DHCP only".
In case my expected semantic is not the intended one, please label that
option differently (e.g. "Automatic IP via DHCPv6, no routing") and add
another option labeled "Automatic, use DHCPv6".
--- End Message ---
--- Begin Message ---
On Tue, Aug 04, 2015 at 04:24:24PM +0200, Axel Beckert wrote:
> For a specific wifi connection I know that IPV6 SLAAC won't succeed but
> DHCPv6 will. So I've set the "Method" to "Automatic, DHCP only" under
> "IPv6 Settings".
>
> The interface also gets the expected IP addresses, but routes are no
> more set because net.ipv6.conf.wlp3s0.accept_ra is unexpectedly set to
> 0.
>
> This doesn't make sense at all, because with DHCPv6 routes are still
> announced by the routers. DHCPv6 does not even have support for
> announcing routes.
>
> So please stop setting net.ipv6.conf.*.accept_ra on the according
> interface if the IPv6 method is set to "Automatic, DHCP only".
>
> In case my expected semantic is not the intended one, please label that
> option differently (e.g. "Automatic IP via DHCPv6, no routing") and add
> another option labeled "Automatic, use DHCPv6".
It's not that NM doesn't expect to need routes from RAs, but rather
NetworkManager implements IPv6 neighbor discovery in userspace, so it's
expected that the kernel's implementation is disabled when NM is
managing an interface. RAs are still solicited and processed. See
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/tree/main/src/core/ndisc
systemd-networkd does the same thing.
I'd argue that it doesn't make any sense to apply IP address
configuration without any corresponding routes, as described in your
proposal, but we can leave that to the maintainers to ponder if you want
to reopen this and pursue it further.
noah
--- End Message ---
