From: Egbert Verhage <egbert@eggiecode.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>, jomat+wireguard.io@jmt.gr
Cc: wireguard@lists.zx2c4.com
Subject: Re: Debian-based configuration for wireguard
Date: Mon, 10 Jul 2017 21:53:57 +0200 [thread overview]
Message-ID: <1499716437.988.1.camel@eggiecode.org> (raw)
In-Reply-To: <20170710025323.GC31153@zx2c4.com>
Hey Baptiste,
Jep, I did that.
See the ifupdown package of my own wireguard ppa:
https://launchpad.net/~eggiecode/+archive/ubuntu/wireguard
And here is the diff:
http://test.egbert.online/diff_ifupdown_ppa.txt
Greetz,
Egbert
On Mon, 2017-07-10 at 04:53 +0200, Jason A. Donenfeld wrote:
> On Sun, Jul 09, 2017 at 11:17:04PM +0000, jomat+wireguard.io@jmt.gr
> wrote:
> > Nice! I also don't like wg-quick too much, but also dislike the
> > pre-/post-/-up/-down directives in my /etc/network/interfaces, so
> > I put this script to /etc/network/if-pre-up.d/ and if-post-down.d
> > which could work for Debian, too:
> >
> > https://github.com/jomat/aports/blob/master/testing/wireguard/wireg
> > uard.ifupdown
>
> I think Egbert might have also written an ifupdown thing? Adding him
> to
> the CC in case you guys want to standardize on one Debian way of
> doing
> things?
>
> Jason
next prev parent reply other threads:[~2017-07-10 19:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 21:30 Debian-based configuration for wireguard Baptiste Jonglez
2017-07-09 23:17 ` jomat+wireguard.io
2017-07-10 2:53 ` Jason A. Donenfeld
2017-07-10 19:53 ` Egbert Verhage [this message]
2017-07-10 21:20 ` Daniel Kahn Gillmor
2017-07-11 1:59 ` Jason A. Donenfeld
2017-07-11 10:22 ` Egbert Verhage
2017-07-11 13:04 ` jomat+wireguard.io
2017-07-11 22:19 ` Daniel Kahn Gillmor
2017-07-11 22:48 ` Jason A. Donenfeld
2017-07-11 23:12 ` Daniel Kahn Gillmor
2017-07-10 2:51 ` Jason A. Donenfeld
-- strict thread matches above, loose matches on Subject: below --
2017-07-10 20:14 raul
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=1499716437.988.1.camel@eggiecode.org \
--to=egbert@eggiecode.org \
--cc=Jason@zx2c4.com \
--cc=jomat+wireguard.io@jmt.gr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.