From: Frank Behrens <frank@harz.behrens.de>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: [PATCH] freebsd: Implement selection of FIB (routing table) for tunneled packets
Date: Fri, 19 Mar 2021 17:57:01 +0100 [thread overview]
Message-ID: <6aa0fd33-4c0d-557f-f7f5-5f5406b3a273@harz.behrens.de> (raw)
Hello Jason, hello community,
although I regret the recent removal of FreeBSD kernel driver I can live
with the present development model.
With the current sources in the external repository I could create a
working VPN for the first time with my Android phone. It works well,
thanks to all contributors. The setup was done only with ifconfig(8), I
have the now removed parts still in place. :-)
For my setup I needed a different route for the encapsulated packets and
so I implemented the missing parts. With this message I give that part
to the community (matching the existing BSD-2-Clause-FreeBSD license).
For the sake of simplicity I created an own branch on github, the commit
is
https://github.com/frbehrens/wireguard-freebsd/commit/f0445be7b5b30a98da11bf2e209739a2155a59bb
or use for direct patch download:
https://github.com/frbehrens/wireguard-freebsd/commit/f0445be7b5b30a98da11bf2e209739a2155a59bb.patch
Kind regards,
Frank
--
Frank Behrens
Osterwieck, Germany
next reply other threads:[~2021-03-19 17:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 16:57 Frank Behrens [this message]
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
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=6aa0fd33-4c0d-557f-f7f5-5f5406b3a273@harz.behrens.de \
--to=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).