Development discussion of WireGuard
 help / color / mirror / Atom feed
* [ANNOUNCE] wireguard-freebsd snapshot v0.0.20220615 is available
@ 2022-06-15 14:11 Jason A. Donenfeld
  2022-06-26 17:51 ` Frank Volf
  0 siblings, 1 reply; 2+ messages in thread
From: Jason A. Donenfeld @ 2022-06-15 14:11 UTC (permalink / raw)
  To: WireGuard mailing list

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

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


-----BEGIN PGP SIGNATURE-----

iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAmKp6JIQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrgjTEAC5p4+osYbOTZG0uBlpAQ4ETTmlbJ8yV0av
fZ/P0rLJkL2iYifgynnvO6GyKcRBb9rXa37OKb8+Mt350UU6mgwCB9FaGvWYxEGM
cZYN+BVCN49DdFBtiLeCKnDe8ufeLahs87eSQDI1LDbiX9gYkuWR2cxHfN6b5wZX
r/M80gxbOBR7/pFWm5Hplfj3CRyJkb4i89/BSJ+5Zmbo+qGd2CoKIxHsUXLQeatq
0LhJuFxIrol1Hm/L4pA5k4MTa/UmOVrDkB04cR7eCFp7yxEVKE9aol6tO1uSdD7S
XEdNwsARQ2ehf7DoYdRV+1cl/rTnfaNo7Qp0fAu2+dmd7F0cwRtYCnP45Bcw1F0c
83fImSL4ck0MIFzo9brNK1sa15J+jsYsRsnlqLA0ObPBtOPf+ag/FSp1wfuAwHS6
ugcGNsaX+fOZ9yVf1dxpZHDOiw5TACW221TFb979jaCbHFncf1Ix2GTUeUrEImJa
vuS1uhZOWwJza+ZqdsY2SyNPOewvaaXO5owBPZiD2Qz56Tv7c2v1mdYsT21qldah
+cyffwJKi9if8eGLMH2ao9pfdjZ12Q93GR5nDACqRJtcB4lyMJbX5cMCESmHiCGX
A4C3NUyfiaBxi3Pr4eFWeXuAZLCKmj+/GCoaTdlc34a/LJYuA9GVdR/aIcclRn9e
a6zVVuSnPA==
=Ktyi
-----END PGP SIGNATURE-----

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [ANNOUNCE] wireguard-freebsd snapshot v0.0.20220615 is available
  2022-06-15 14:11 [ANNOUNCE] wireguard-freebsd snapshot v0.0.20220615 is available Jason A. Donenfeld
@ 2022-06-26 17:51 ` Frank Volf
  0 siblings, 0 replies; 2+ messages in thread
From: Frank Volf @ 2022-06-26 17:51 UTC (permalink / raw)
  To: Jason A. Donenfeld, WireGuard mailing list


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
>
>
 >



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-06-26 17:51 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-15 14:11 [ANNOUNCE] wireguard-freebsd snapshot v0.0.20220615 is available Jason A. Donenfeld
2022-06-26 17:51 ` Frank Volf

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).