From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Kalin KOZHUHAROV <me.kalin@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] What is a good way to ingrate (as of now) wireguard into openrc in Gentoo?
Date: Sat, 19 Nov 2016 02:14:00 +0100 [thread overview]
Message-ID: <CAHmME9rfB709DCnqiXG2L7kMwCx0bgiSXi2C2LwYR=bX-trNzw@mail.gmail.com> (raw)
In-Reply-To: <CAKXLc7fAG5xErC_vU40qOwxKxWbLAavKmomNwjOiRP=Fh+0tGg@mail.gmail.com>
Hey Kalin,
Funny enough, I can't remember the exact interworkings of that script,
because I didn't write it. A guy named zhasha in #wireguard did. I'll
ask him to document it; that could be useful. I know another gentoo
dev was working on a WireGuard gentoo page for the wiki.
I think, in short, the way it works is you add this to your /etc/conf.d/net:
wireguard_wg0="/path/to/file.conf"
or,
wireguard_wg0="private-key /path/to/whatever listen-port 1234 peer
ABCDEF= endpoint 1.2.3.4:2468"
In other words, if the argument is a file path, it is passed to
setconf, and otherwise they're passed to set. You can then use the
other ordinary netifrc values for setting the IP addresses.
A somewhat reasonable place to store config files would be in
/etc/wireguard, and make sure that directory is chmod'd to 700, since
it contains private keys.
Jason
next prev parent reply other threads:[~2016-11-19 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 11:42 Kalin KOZHUHAROV
2016-11-19 1:14 ` Jason A. Donenfeld [this message]
2016-11-21 5:15 ` Kalin KOZHUHAROV
2016-11-21 14:06 ` Joakim Sindholt
2016-11-21 13:55 ` Joakim Sindholt
2016-11-21 17:00 ` Jason A. Donenfeld
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='CAHmME9rfB709DCnqiXG2L7kMwCx0bgiSXi2C2LwYR=bX-trNzw@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=me.kalin@gmail.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).