From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Stefan Haller" <stefan.haller@stha.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>,
Bernhard Froehlich <decke@freebsd.org>
Subject: Re: FreeBSD if_wg POINTTOPOINT and MULTICAST behaviour
Date: Thu, 15 Apr 2021 18:05:03 -0600 [thread overview]
Message-ID: <CAHmME9qerb3LhuJfQ2L=J9gz=vGXV47qUAwC3-LYMTWVWnn62Q@mail.gmail.com> (raw)
In-Reply-To: <87sg3rigdx.fsf@toke.dk>
Hey Stefan, Toke,
I spent the day playing around with bird and babel and sorted out
FreeBSD's v6 situation. Basically, ff00::/8 addresses are treated
differently, and they're blocked unless the interface sets
IFF_MULTICAST. So I've committed
https://git.zx2c4.com/wireguard-freebsd/commit/?id=a7a84a17faf784857f076e37aa4818f6b6c12a95
to do this. We _could_ also set IFF_BROADCAST, which would translate
to babel enabling IF_MULTICAST, but so far I can't see how this would
help anything real, and combined with Toke's patch --
https://bird.network.cz/pipermail/bird-users/2021-April/015415.html --
I think we're actually in a good situation. Seeing that this now
works, I've also dropped the link1 hack and put that in a branch in
case it becomes useful later.
Bernhard (decke@) is CC'd here in case he'd like to get some of this
into ports early for your use case. Specifically, this involves:
1) https://bird.network.cz/pipermail/bird-users/2021-April/015415.html
for the bird2 package.
2) https://git.zx2c4.com/wireguard-freebsd/patch/?id=a7a84a17faf784857f076e37aa4818f6b6c12a95
for the wireguard-kmod package.
Stefan - please let me know if those work for you. In my testing thus
far, things seem to work for me.
Long term, we'll certainly want to have Toke's planned support for
direct WireGuard peering inside of bird.
Regards,
Jason
next prev parent reply other threads:[~2021-04-16 0:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 18:43 FreeBSD if_wg POINTTOPOINT and MULTICAST behaviour Stefan Haller
2021-04-14 20:24 ` Jason A. Donenfeld
2021-04-14 21:50 ` Stefan Haller
2021-04-14 22:14 ` Toke Høiland-Jørgensen
2021-04-15 4:30 ` Jason A. Donenfeld
2021-04-15 9:42 ` Toke Høiland-Jørgensen
2021-04-15 11:36 ` Stefan Haller
2021-04-15 12:22 ` Toke Høiland-Jørgensen
2021-04-15 17:22 ` Jason A. Donenfeld
2021-04-15 17:53 ` Toke Høiland-Jørgensen
2021-04-16 0:05 ` Jason A. Donenfeld [this message]
2021-04-16 8:57 ` Stefan Haller
2021-04-16 9:35 ` Toke Høiland-Jørgensen
2021-04-19 18:25 ` Toke Høiland-Jørgensen
2021-04-19 19:41 ` Stefan Haller
2021-04-19 19:42 ` Jason A. Donenfeld
2021-04-19 19:49 ` Stefan Haller
2021-04-19 21:46 ` Toke Høiland-Jørgensen
2021-04-16 12:14 ` Muenz, Michael
2021-04-16 15:17 ` Jason A. Donenfeld
2021-04-16 17:45 ` Jason A. Donenfeld
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='CAHmME9qerb3LhuJfQ2L=J9gz=vGXV47qUAwC3-LYMTWVWnn62Q@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=decke@freebsd.org \
--cc=stefan.haller@stha.de \
--cc=toke@toke.dk \
--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 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).