From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Stefan Haller <stefan.haller@stha.de>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: FreeBSD if_wg POINTTOPOINT and MULTICAST behaviour
Date: Fri, 16 Apr 2021 11:35:46 +0200 [thread overview]
Message-ID: <87a6pyinbh.fsf@toke.dk> (raw)
In-Reply-To: <15c3483d-546b-4c86-aca7-9ab37945791e@stha.de>
Stefan Haller <stefan.haller@stha.de> writes:
> Hi Jason,
>
> On Thu, Apr 15, 2021 at 06:05:03PM -0600, Jason A. Donenfeld wrote:
>> 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.
>
> That is also what I observed. Without IFF_MULTICAST I see the following
> error in bird's log:
>
> bird[8045]: babel1: Socket error: IPV6_MULTICAST_IF: Can't assign requested address
> bird[8045]: babel1: Cannot open socket for wg1
>
>> Stefan - please let me know if those work for you. In my testing thus
>> far, things seem to work for me.
>
> After applying Toke's patch for bird and your Wireguard patch in
> a7a84a17faf784 everything is working as before (with minor config
> changes).
>
> Just for the record, my previous configuration looked like this (using
> POINTTOPOINT interfaces, I use ifconfig to set the peer address):
>
>> [Interface]
>> ...
>> Address = fe80::5/64
>> PostUp = ifconfig %i inet 169.254.42.5/32 169.254.42.2
>
> My new configuration without POINTTOPOINT, but only a single peer
> directly attached to other side of the wg tunnel:
>
>> [Interface]
>> ...
>> Address = 169.254.42.5/32, fe80::5/64
>> PostUp = route add 169.254.42.2 -iface %i
>
> So for me everything works as expected again. A big thanks to all of you for
> figuring out what was going wrong and getting it fixed so quickly.
Great! You're welcome :)
-Toke
next prev parent reply other threads:[~2021-04-16 9:35 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
2021-04-16 8:57 ` Stefan Haller
2021-04-16 9:35 ` Toke Høiland-Jørgensen [this message]
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=87a6pyinbh.fsf@toke.dk \
--to=toke@toke.dk \
--cc=Jason@zx2c4.com \
--cc=stefan.haller@stha.de \
--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).