From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] ip/ipconfig: don't add default routes for ipv6 prefixes with a validlt of 0
Date: Tue, 11 Jun 2024 13:23:15 +0200 [thread overview]
Message-ID: <CAFSF3XO_xuPyLCie6EJEwTKjnR=3ED17MEE2_85hRoxkqKQ7Fg@mail.gmail.com> (raw)
In-Reply-To: <100769261.2962249.1718035785390@comcenter.netcologne.de>
it might not be the fritz!box's fault:
against all sanity and against the working mechanism described in the
RFC, the ISPs invalidate old prefixes immediately after they give you
a new PPP session. sadly this is the most common scenario now for end
users. in this case it makes sense that the fritze sets the same 0
lifetime in RAs for the old prefixes.
tbh there's no other good reasons for prefixes changing continuously
like that anyways, apart from this ISP-generated sabotage edge-case.
next prev parent reply other threads:[~2024-06-11 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 16:09 Arne Meyer
2024-06-11 11:23 ` hiro [this message]
2024-06-11 11:41 ` Arne Meyer
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='CAFSF3XO_xuPyLCie6EJEwTKjnR=3ED17MEE2_85hRoxkqKQ7Fg@mail.gmail.com' \
--to=23hiro@gmail.com \
--cc=9front@9front.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).