From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Stefan Haller <stefan.haller@stha.de>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: Re: FreeBSD if_wg POINTTOPOINT and MULTICAST behaviour
Date: Thu, 15 Apr 2021 11:22:57 -0600 [thread overview]
Message-ID: <CAHmME9pxnh6MFdQGQCWRX6aNJu=rM-SyVY1jLb6EurgNNhwJSg@mail.gmail.com> (raw)
In-Reply-To: <7be52421-db0d-4971-99b0-ce76307d1a33@stha.de>
Hi Stefan,
Sounds like Toke has come up with the optimal solution, so I think
I'll drop the "link1" patch/hack.
One thing I was wondering though, mostly for my own curiosity, is what
config you're using that shows the problem, and how does the problem
manifest?
I just put this in bird.conf:
router id 192.168.88.2;
protocol babel {
interface "wg0" {
type wired;
port 1234;
};
};
And then I ran:
# pkg install bird2
# bird -d -c bird.conf
And I didn't see any troubling error messages. But maybe it's more
subtle than that?
Jason
next prev parent reply other threads:[~2021-04-15 17:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 18:43 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 [this message]
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
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='CAHmME9pxnh6MFdQGQCWRX6aNJu=rM-SyVY1jLb6EurgNNhwJSg@mail.gmail.com' \
--to=jason@zx2c4.com \
--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).