From: Nico Schottelius <nico.schottelius@ungleich.ch>
To: netdev@vger.kernel.org
Subject: IPv6 addresses stay tentative (Linux 5.4.6, 5.4.7)
Date: Wed 01 Jan 2020 04:30:10 PM CET [thread overview]
Message-ID: <87mub7tbr3.fsf@ungleich.ch> (raw)
https://roy.marples.name/archives/dhcpcd-discuss/0002774.html
p.s.: I am using accept_ra = 2, because forwarding is also enabled.
Hello,
it seems something in the kernel code changed in regard to setting IPv6
addresses usable (i.e. dad done). Since 5.4.6 IPv6 addresses setup
statically or via autoconf (router advertisements) seem so stay in
"tentative" state forever.
I did not experience this behaviour in 5.3.13 (*) and it seems I am not
the only one affected:
I turned dhcpcd off to test whether it happens without it and indeed the
problem seems to be unrelated to dhcpcd.
Does anyone know about a recent change that may cause this behaviour?
Best regards,
Nico
(*) I cannot boot kernels 5.4.x < 5.4.6, as the wifi card does not show
up with them.
--
Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch
next reply other threads:[~2020-01-01 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 15:30 Nico Schottelius [this message]
2020-01-02 16:53 ` IPv6 addresses stay tentative (Linux 5.4.6, 5.4.7) David Ahern
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=87mub7tbr3.fsf@ungleich.ch \
--to=nico.schottelius@ungleich.ch \
--cc=netdev@vger.kernel.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).