From: "Dan Lüdtke" <mail@danrl.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] Wireguard in OpenWRT/LEDE: FYI: Pull Request
Date: Wed, 16 Nov 2016 18:04:38 +0100 [thread overview]
Message-ID: <1F78626C-0102-4833-8E86-AEC1403507BF@danrl.com> (raw)
In-Reply-To: <CAHmME9pX8iG67Mz_0zN-biOTyGXtm2DjRtQQwJTw9UTxz3ar4w@mail.gmail.com>
> The config value has to be the same to correlate them. In that case,
> you should show an example with multiple peers, so that it's clear
> what's happening.
It says "Peer configurations are managed via one or more =
wireguard_<ifname> sections." to introduce the example. However, won't =
hurt to add another peer for clarification.
Consider it done :)
DUMP:
Create a WireGuard tunnel interface named ''foo'' that connects to one =
peer (VPN server at vpn.example.com) and allows another peer (e.g. road =
warrior) to connect.
Peer configurations are managed via one or more ''wireguard_<ifname>'' =
sections.
<code>
config interface 'foo'
option proto 'wireguard'
option private_key =
'qLvQnx5CpXPDo6oplzdIvXLNqkbgpXip3Yv4ouHWZ0Q=3D'
option preshared_key =
'M1IbkkDVwXsQbFbURiMXiVe/iUCjC5TKHCmemVs+oLQ=3D'
config wireguard_foo
option public_key '9mD+mTiOp7SGIkB4t3ZfWAcfp5iA/WwQRdVypKKwrjY=3D'=
option route_allowed_ips '1'
list allowed_ips 'fd00:13:37::/48'
option endpoint_host 'vpn.example.com'
option persistent_keepalive '25'
config wireguard_foo
option public_key '4mLeSytW6/y4UcOT6rNorw1Ae9nXSxhXUjxsdzMWkUA=3D'=
list allowed_ips 'fd00:13:37:ffff::23'
</code>
To use static addresses on a WireGuard interface, create a static =
address configuration on top of the interface.
<code>
config interface 'bar'
option proto 'static'
option ifname 'foo'
option ip6addr 'fd00:13:37::2/64'
</code>=
next prev parent reply other threads:[~2016-11-16 16:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 22:35 Dan Lüdtke
2016-11-13 22:52 ` Dan Lüdtke
2016-11-15 16:01 ` Dan Lüdtke
2016-11-16 8:15 ` Baptiste Jonglez
2016-11-16 8:48 ` Kalin KOZHUHAROV
2016-11-16 9:34 ` Dan Luedtke
2016-11-16 9:50 ` Kalin KOZHUHAROV
2016-11-16 10:11 ` Dan Lüdtke
2016-11-16 16:55 ` Dan Lüdtke
2016-11-16 16:56 ` Jason A. Donenfeld
2016-11-16 16:58 ` Jason A. Donenfeld
2016-11-16 17:04 ` Dan Lüdtke [this message]
2016-11-16 17:45 ` Jason A. Donenfeld
2016-11-16 17:01 ` Dan Lüdtke
2016-12-12 12:03 Michal Kowalski
2016-12-12 13:27 ` Jason A. Donenfeld
2016-12-14 19:48 ` Dan Lüdtke
2016-12-14 21:07 ` Jason A. Donenfeld
2016-12-16 17:45 ` 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=1F78626C-0102-4833-8E86-AEC1403507BF@danrl.com \
--to=mail@danrl.com \
--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).