From: JuniorJPDJ <juniorjpdj@juniorjpdj.pl>
To: wireguard@lists.zx2c4.com
Subject: Re: Standardized IPv6 ULA from PublicKey
Date: Wed, 24 Jun 2020 19:30:52 +0200 [thread overview]
Message-ID: <a1475e1d-24e8-2e0a-030a-cdefffb1de8c@juniorjpdj.pl> (raw)
In-Reply-To: <CA+cYV6uWUC1YDbpXz+ft-fKug7SY4_QNrR-x7q_z_qWmj7u-Ww@mail.gmail.com>
IMO link-local should be assigned by core - RFC4291 which is defining
IPv6 clearly says:
"Its required Link-Local address for each interface."
https://tools.ietf.org/html/rfc4291#section-2.8
On 6/24/20 7:08 PM, Chriztoffer Hansen wrote:
> On Wed, 24 Jun 2020 at 17:37, Florian Klink <flokli@flokli.de> wrote:
>> Deriving an IPv6 link-local address from the pubkey and adding it to the
>> interface should be a no-brainer and sane default, and already fix Babel
>> Routing (and most other issues) for "point-to-point tunnels"
>> (only one peer, both sides set AllowedIPs=::/0).
> An idea to implement as an option for e.g. wg-quick, rather than the
> base code-base itself?
>
next prev parent reply other threads:[~2020-06-29 18:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 16:52 Standardized IPv6 ULA from PublicKey Lonnie Abelbeck
2017-12-04 17:14 ` Aaron Jones
2017-12-05 2:53 ` Luis Ressel
2017-12-05 3:31 ` Jason A. Donenfeld
2020-06-24 15:37 ` Florian Klink
2020-06-24 17:08 ` Chriztoffer Hansen
2020-06-24 17:30 ` JuniorJPDJ [this message]
2020-06-27 21:43 ` Reid Rankin
2020-06-28 10:15 ` Arti Zirk
2020-06-28 15:19 ` Derrick Lyndon Pallas
2020-06-29 10:22 ` Toke Høiland-Jørgensen
2020-06-29 10:31 ` Roman Mamedov
2020-06-29 10:52 ` Justin Kilpatrick
2020-06-29 11:03 ` Toke Høiland-Jørgensen
2020-06-29 11:38 ` Roman Mamedov
2020-06-29 12:15 ` Toke Høiland-Jørgensen
2020-06-29 17:01 ` Arti Zirk
2020-06-29 18:01 ` Jason A. Donenfeld
2020-06-29 19:58 ` Reid Rankin
2020-06-30 1:24 ` Jason A. Donenfeld
2020-06-30 8:01 ` Reid Rankin
2020-06-29 18:49 ` Luiz Angelo Daros de Luca
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=a1475e1d-24e8-2e0a-030a-cdefffb1de8c@juniorjpdj.pl \
--to=juniorjpdj@juniorjpdj.pl \
--cc=wireguard@lists.zx2c4.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.