Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Egbert Verhage <egbert@eggiecode.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] Seeking Ubuntu PPA Maintainer
Date: Wed, 16 Nov 2016 00:41:25 +0100	[thread overview]
Message-ID: <7a9a422b-ad5e-f6a2-7078-26930f2177f5@eggiecode.org> (raw)
In-Reply-To: <CAHmME9r24tV2RmNYQfxvdF_0L_egYFek0xeqNZS5UNuZjN5N4Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1932 bytes --]

On 2016-11-15 21:44, Jason A. Donenfeld wrote:
> Hey folks,
>
> Looks like there are various Ubuntu PPAs for WireGuard floating
> around. I'd like to officially endorse one on the install section of
> the website. Is anybody interested in being the Ubuntu downstream for
> WireGuard?
>
> Thanks,
> Jason
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> http://lists.zx2c4.com/mailman/listinfo/wireguard

Hey Jason,

I'm trying to maintain one now, but it is my first one and trying to
keep it up to date.
https://launchpad.net/~eggiecode/+archive/ubuntu/wireguard

Testing it constantly on 4 of my servers and works it great!
Even added a patch for ifupdown to setup WireGuard in
/etc/network/interfaces

The only downside is that I disabled AVX2 cpu extention in the code,
because of kernel panics on VPS's by a hosting company
(https://eggiecode.org/wg-kernel-panic.png).

Greetz,
Egbert Verhage

Below example config of wireguard in network/interfaces

iface wg0 inet wireguard
        netmask 255.255.255.0
        address 192.168.2.254
        wg_config /etc/network/wg0.ini

        up ip -4 route add 10.20.1.0/24 dev wg0
        pre-down ip -4 route del 10.20.1.0/24 dev wg0
        up ip -4 route add 10.20.3.0/24 dev wg0
        pre-down ip -4 route del 10.20.3.0/24 dev wg0
        up ip -4 route add 10.20.2.0/24 dev wg0
        pre-down ip -4 route del 10.20.2.0/24 dev wg0

iface wg0 inet6 wireguard
        netmask 64
        address fd4a:2831:fc20:f528:fe::1

        up ip -6 route add 2001:41d0:2:5c39::/64 dev wg0
        pre-down ip -6 route del 2001:41d0:2:5c39::/64 dev wg0
        up ip -6 route add 2a00:f10:700:5f::/60 dev wg0
        pre-down ip -6 route del 2a00:f10:700:5f::/60 dev wg0
        up ip -6 route add 2001:41d0:d:2a83::/64 dev wg0
        pre-down ip -6 route del 2001:41d0:d:2a83::/64 dev wg0

(Forgot to send it to the mailinglist.)


[-- Attachment #2: Type: text/html, Size: 2639 bytes --]

  reply	other threads:[~2016-11-15 23:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 20:44 Jason A. Donenfeld
2016-11-15 23:41 ` Egbert Verhage [this message]
     [not found] ` <454ad249-3313-9423-c2d4-7602d56849fc@eggiecode.org>
2016-11-16  0:12   ` Jason A. Donenfeld
2016-11-16  0:34     ` Egbert Verhage
2016-11-16  1:31       ` Jason A. Donenfeld
2016-11-16  6:20         ` Dan Luedtke
2016-11-16 11:18           ` Egbert Verhage
2016-11-16 11:34             ` Dan Lüdtke
2016-11-16 14:04               ` Jason A. Donenfeld
2016-11-16 10:03         ` Egbert Verhage
2016-11-16 14:09           ` Jason A. Donenfeld
2016-11-16 14:22             ` Egbert Verhage
2016-11-16 14:25               ` Jason A. Donenfeld
2016-11-16  6:45       ` Daniel Kahn Gillmor
2016-11-16 11:10         ` Egbert Verhage
2016-11-16 14:24           ` Jason A. Donenfeld
2016-11-16 22:17             ` Daniel Kahn Gillmor
2016-11-16 22:52               ` Jason A. Donenfeld
2016-11-16 14:11 ` Jason A. Donenfeld
2016-11-16 14:37 Anonymous Anonymous
2016-11-16 15:00 ` Jason A. Donenfeld
2016-11-16 15:08   ` Egbert Verhage
2016-11-16 14:47 Anonymous Anonymous

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=7a9a422b-ad5e-f6a2-7078-26930f2177f5@eggiecode.org \
    --to=egbert@eggiecode.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).