From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Frank Behrens <frank@harz.behrens.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] freebsd: Implement selection of FIB (routing table) for tunneled packets
Date: Sat, 17 Apr 2021 10:49:08 -0600 [thread overview]
Message-ID: <CAHmME9qu+3GpQtq78kZ4T9LAVAMqvoVjWChCqNT0Pn9BB29adg@mail.gmail.com> (raw)
In-Reply-To: <3d610bc1-84c9-1ad5-a366-3c8b77efb858@harz.behrens.de>
Hi Frank,
On Sat, Apr 17, 2021 at 9:23 AM Frank Behrens <frank@harz.behrens.de> wrote:
>
>
> Am 17.04.2021 um 17:00 schrieb Jason A. Donenfeld:
> > Does this actually fix or change anything? Don't new sockets have
> > fib==0 right out of the gate already?
>
> New sockets inherit the fib from the current process. If you create
> the wg interface from a process with different fib, that fib will also
> be used for this socket. Probably the difference in code is not very
> important for the case of a system default boot. But that may vary
> for jails/vnets with different default fibs.
>
> In my test case the sequence
> > setfib 1 ifconfig wg0 create ....
> > ifconfig wg0 tunnelfib 0
> failed.
Ahh, interesting. I applied your patch. Thanks for the persistence in
getting this feature working well.
Jason
next prev parent reply other threads:[~2021-04-17 16:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 16:57 [PATCH] freebsd: Implement selection of FIB (routing table) for tunneled packets Frank Behrens
2021-03-19 17:35 ` Jason A. Donenfeld
2021-03-20 17:05 ` Frank Behrens
2021-03-20 18:59 ` Franco Fichtner
2021-03-22 17:43 ` Jason A. Donenfeld
2021-03-22 18:14 ` Jason A. Donenfeld
2021-03-23 5:51 ` Frank Behrens
2021-03-31 19:05 ` Frank Behrens
2021-03-31 19:11 ` Jason A. Donenfeld
2021-03-31 19:16 ` Frank Behrens
2021-04-01 16:27 ` Frank Behrens
2021-04-13 2:57 ` Jason A. Donenfeld
2021-04-17 13:08 ` Frank Behrens
2021-04-17 15:00 ` Jason A. Donenfeld
2021-04-17 15:23 ` Frank Behrens
2021-04-17 16:49 ` Jason A. Donenfeld [this message]
2021-03-19 17:38 ` 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=CAHmME9qu+3GpQtq78kZ4T9LAVAMqvoVjWChCqNT0Pn9BB29adg@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=frank@harz.behrens.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).