Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Cc: Pascal Vorwerk <info@fossores.de>,
	Nils Andreas Svee <me@lochnair.net>,
	 Aleksandrs Fomins <alex.fomins@ui.com>,
	Feng Lin <feng.lin@ui.com>
Subject: [ANNOUNCE] WireGuard for Ubiquiti devices/EdgeOS has returned
Date: Mon, 4 May 2020 13:16:11 -0600	[thread overview]
Message-ID: <CAHmME9oWPDuR4OAeHH7Fcau26bLKA0grVgbEzTQ3pF96AzUjqg@mail.gmail.com> (raw)

Hi all,

After a period of darkness, our builds of WireGuard for EdgeOS and
Ubiquiti devices have returned, thanks to Pascal Vorwerk stepping up
to takeover maintenance and CI. We've also moved this from Nils'
personal github account into the WireGuard organization. You can get
started here:

https://github.com/WireGuard/wireguard-vyatta-ubnt/blob/master/README.md
https://github.com/WireGuard/wireguard-vyatta-ubnt/releases
https://www.wireguard.com/install/#edgeos-module-tools

We also expect and hope that Ubiquiti will be shipping WireGuard
built-in in the mid-term future, which will be an exciting
development. Until then, here's how to get things running. The .deb
available on that site should have full Vyatta integration, which
hopefully will provide some basis for Ubiquiti's own integration work.

Please direct any questions toward Pascal, as he'll be maintaining this.

Enjoy,
Jason

             reply	other threads:[~2020-05-04 19:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04 19:16 Jason A. Donenfeld [this message]
2020-05-05  0:53 ` Brian Gregory

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=CAHmME9oWPDuR4OAeHH7Fcau26bLKA0grVgbEzTQ3pF96AzUjqg@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=alex.fomins@ui.com \
    --cc=feng.lin@ui.com \
    --cc=info@fossores.de \
    --cc=me@lochnair.net \
    --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).