netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Garri Djavadyan <g.djavadyan@gmail.com>
To: netdev@vger.kernel.org
Cc: 1117959@bugs.debian.org
Subject: ipv6_route flags RTF_ADDRCONF and RTF_PREFIX_RT are not cleared when static on-link routes are added during IPv6 address configuration
Date: Thu, 16 Oct 2025 00:12:40 +0200	[thread overview]
Message-ID: <ba807d39aca5b4dcf395cc11dca61a130a52cfd3.camel@gmail.com> (raw)

Hi Everyone,

A year ago I noticed a problem with handling ipv6_route flags that in
some scenarios can lead to reachability issues. It was reported here:

https://bugzilla.kernel.org/show_bug.cgi?id=219205


Also it was recently reported in the Debian tracker after checking if
the latest Debian stable is still affected:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1117959


Unfortunately, the Debian team cannot act on the report because no one
from the upstream kernel team has confirmed if the report in the
upstream tracker is valid or not. Therefore, I am checking if anyone
can help confirm if the observed behavior is indeed a bug.

Many thanks in advance!

Regards,
Garri

             reply	other threads:[~2025-10-15 22:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 22:12 Garri Djavadyan [this message]
2025-10-18  8:39 ` ipv6_route flags RTF_ADDRCONF and RTF_PREFIX_RT are not cleared when static on-link routes are added during IPv6 address configuration Stephen Hemminger
2025-10-25 14:53   ` Bug#1117959: " Salvatore Bonaccorso
2025-10-25 21:21     ` Garri Djavadyan
2025-11-10 16:54       ` Fernando Fernandez Mancera

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=ba807d39aca5b4dcf395cc11dca61a130a52cfd3.camel@gmail.com \
    --to=g.djavadyan@gmail.com \
    --cc=1117959@bugs.debian.org \
    --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).