From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: iwd: update to 1.10.
Date: Mon, 30 Nov 2020 22:21:23 +0100 [thread overview]
Message-ID: <20201130212123.LCO7S2UGCCUtZTVtpf4d_EDDHfD72IWnRaBpYd7eOqo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26824@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/26824#issuecomment-736064043
Comment:
This release totally breaks stateless autoconfig for IPv6. With 1.9, `iwd` ignored IPv6, so the kernel was able to use its built-in SLAAC mechanism to configure IPv6 when router advertisements were received. With the new "support", `iwd` unconditionally disabled router advertisement receipts by setting the `net.ipv6.conf.<interface>.accept_ra=0` sysctl. Furthermore, unless `EnableIPv6=true` or `EnableNetworkConfiguration=false` in the `main.conf` for `iwd`, it will also set `net.ipv6.conf.<interface>.disable_ipv6=0`.
I have not been able to restore old in-kernel IPv6 behavior, so the only way I can get SLAAC with this version of `iwd` is to force `EnableNetworkConfiguration=false` and fall back to `dhcpcd` for address assignment.
next prev parent reply other threads:[~2020-11-30 21:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 14:25 [PR PATCH]  " pbui
2020-11-30 14:33 ` [PR REVIEW] " ericonr
2020-11-30 14:33 ` ericonr
2020-11-30 14:33 ` ericonr
2020-11-30 14:38 ` pbui
2020-11-30 14:42 ` ericonr
2020-11-30 15:01 ` [PR REVIEW] " pbui
2020-11-30 17:06 ` ericonr
2020-11-30 17:07 ` ericonr
2020-11-30 17:20 ` [PR PATCH] [Updated] " pbui
2020-11-30 17:21 ` [PR REVIEW] " pbui
2020-11-30 17:21 ` pbui
2020-11-30 17:22 ` pbui
2020-11-30 19:30 ` ericonr
2020-11-30 19:40 ` [PR PATCH] [Updated] " pbui
2020-11-30 19:40 ` pbui
2020-11-30 20:32 ` [PR REVIEW] " ericonr
2020-11-30 21:21 ` ahesford [this message]
2020-11-30 23:03 ` [PR PATCH] [Updated] " pbui
2020-11-30 23:06 ` [PR REVIEW] " pbui
2020-11-30 23:20 ` ericonr
2020-12-01 21:31 ` ericonr
2020-12-01 23:33 ` ahesford
2020-12-01 23:40 ` [PR PATCH] [Merged]: " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201130212123.LCO7S2UGCCUtZTVtpf4d_EDDHfD72IWnRaBpYd7eOqo@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).