Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Frank Volf <frank@deze.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [ANNOUNCE] wireguard-freebsd snapshot v0.0.20220615 is available
Date: Sun, 26 Jun 2022 19:51:44 +0200	[thread overview]
Message-ID: <672909d9-560f-3e83-3c9b-e3d69e8e70fa@deze.org> (raw)
In-Reply-To: <20220615141140.96557C3411C@smtp.kernel.org>


Hi,

I tested this snapshot on my setup for 10 days now and it works 
perfectly without any problems.

My setup is fairly simple: central VPN server (FreeBSD 13.1), two 
servers on branch sites (each behind NAT) and a mobile Android client.
VPN's are used for management type activities, so no high bandwidth or 
low latency requirements needed.
So not sure if this setup is representative enough, but I'm happy with 
how it behaves.

There is one small feature that I would like to see: My central server 
has multiple public IP addresses and sometimes Wireguard needs to 
initiate a connection to one of the branch servers. Unfortunately, there 
is no way to specify which source address to use for that. Currently it 
appears to use a random IP address from the outgoing interface (mostly 
the first IP address configured on the external interface).
I would like to see the option to specify the IP address to be used for 
outgoing connections, that would be  much more convenient when you have 
to deal with upstream firewalls.
Not sure if this is a difficult thing to implement, but I would love to 
have it.

Anyway, thanks for all the work you guys did on this great product!!!

Kind regards,

Frank


Op 15-6-2022 om 16:11 schreef Jason A. Donenfeld:
> Hi,
>
> An experimental snapshot, v0.0.20220615, of WireGuard for FreeBSD has been
> been tagged in the git repository.
>
> At this time this code is new, unvetted, possibly buggy, and should be
> considered "experimental". It might contain security issues. We gladly
> welcome your testing and bug reports, but do keep in mind that this code
> is new, so some caution should be exercised at the moment for using it
> in mission critical environments.
>
> == Changes ==
>
>   * ci: add FreeBSD 12.3 and 13.1
>   * compat: update version to handle sbcreatecontrol() changes
>
>   More fixes to the compat layer.
>
>   * wg_noise: import hmac from crypto
>   * crypto: inline blake2s convenience function
>
>   A few crypto cleanups.
>
> This snapshot contains commits from: Jason A. Donenfeld, Joseph 
> Mingrone, and
> Ed Maste.
>
> The source repository is available at the usual location:
>   git clone https://git.zx2c4.com/wireguard-freebsd
>
> This snapshot is available in compressed tarball form:
> https://git.zx2c4.com/wireguard-freebsd/snapshot/wireguard-freebsd-0.0.20220615.tar.xz
>   SHA2-256: 
> ad6c42d20a7c0ad2989e729dd41ea5a6a019426b762dfd0c6417e340935cca82
>
> Thank you,
> Jason Donenfeld
>
>
 >



      reply	other threads:[~2022-06-26 17:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15 14:11 Jason A. Donenfeld
2022-06-26 17:51 ` 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=672909d9-560f-3e83-3c9b-e3d69e8e70fa@deze.org \
    --to=frank@deze.org \
    --cc=Jason@zx2c4.com \
    --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).