From: Frank Volf <frank@deze.org>
To: Kyle Evans <kevans@freebsd.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard on FreeBSD - a few questions
Date: Wed, 3 Nov 2021 21:52:40 +0100 [thread overview]
Message-ID: <3b364170-7a7e-d9aa-d365-fe0ce3390acd@deze.org> (raw)
In-Reply-To: <CACNAnaE8DrntMR0RifxNzijLWfBXNHxm2poSY-DewOQszP-XqQ@mail.gmail.com>
Hi Kyle,
>> 1) Is it possible on FreeBSD to enable some kind of logging? I did made
>> a small configuration error with my first client and it was hard to find
>> the error, because there does not seem to be any logging at all. Some
>> logging information would be appreciated and probably wold have pointed
>> me faster to the fact that I needed to switch two keys in my config.
>>
> If you set 'debug' on the interface (`ifconfig wg0 debug`) then it'll
> write some useful bits to syslog for your perusal.
O.k. good to know this. It would be even better if this was documented,
I think a if_wg manual page for FreeBSD would be appropriate.
>> 2) I noticed that Wireguard uses a wildcard to listen to all IP
>> addresses on my multi-homed machine on his dedicated UDP port. I would
>> prefer if Wireguard would only bind to the specific IP address on the
>> outside interface that is designated for that use. Is this possible?
I think it is useful if you could bind Wireguard to use/listen on a
specific IP address, instead of the wildcard.
For example, for my tests I used a secondary (alias) IP address on a
server as the entry point for Wireguard tunnels.
However, if the server starts a session to the client (or tries to check
if the client is still alive), it uses the primary interface address
instead.
Binding it to a specific IP address would solve this.
Kind regards,
Frank
prev parent reply other threads:[~2021-11-03 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 18:41 Wireguard on FreeBSD - a few questions Frank Volf
2021-11-03 16:39 ` Kyle Evans
2021-11-03 20:52 ` Frank Volf [this message]
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=3b364170-7a7e-d9aa-d365-fe0ce3390acd@deze.org \
--to=frank@deze.org \
--cc=kevans@freebsd.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).