From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Muenz, Michael" <m.muenz@spam-fetish.org>
Cc: wireguard@lists.zx2c4.com
Subject: Re: FreeBSD if_wg POINTTOPOINT and MULTICAST behaviour
Date: Fri, 16 Apr 2021 09:17:26 -0600 [thread overview]
Message-ID: <CAHmME9p3MOtJKw7LK4WraPjB20cGGrmGgMNZOSf4YT=jTzH-ww@mail.gmail.com> (raw)
In-Reply-To: <8e80a3e4-4118-6273-a5e3-0ec7692fcb17@spam-fetish.org>
Hi Michael,
On 4/16/21, Muenz, Michael <m.muenz@spam-fetish.org> wrote:
> Am 16.04.2021 um 10:57 schrieb Stefan Haller:
>> 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):
>
>
> Hi,
>
> Just following the conversation and also had a quick chat with Jason via
> IRC (mimugmail).
> We had a couple of reports that with latest change of removing PTP which
> breaks OSPF.
> In our case (OPNsense) we rely on FRR so it would be nice to have a
> generic solution without toucingh routing software itself.
>
>
>> 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.
>>
>>
>
> I set up a lab and will do some testing with version before and after
> the change, maybe for FRR it's enough to set NBMA or similar.
Could you send a minimal bird config that's broken so that I can
reproduce the problem and debug?
Jason
next prev parent reply other threads:[~2021-04-16 15:20 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
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 [this message]
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='CAHmME9p3MOtJKw7LK4WraPjB20cGGrmGgMNZOSf4YT=jTzH-ww@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=m.muenz@spam-fetish.org \
--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).