From: timsan <timsan@xs4all.nl>
To: wireguard@lists.zx2c4.com
Subject: Re: wireguard ipv6 conf
Date: Fri, 10 Nov 2017 20:01:05 -0800 [thread overview]
Message-ID: <CALrp0MGuzcT=Z_xwTjjWnw3LPXOLvBqm0pZua01jCSou93D=Yg@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9o0f=K7g84fO_ba2=n_WtsQZHxZR+SvEPAbLKmdJwzhEg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
Thanks for the nice reply, I've inched just one step further.
I'm now on the routing -- IPv4 routes with no problem, but IPv6 is not
routing.
Still working on it. Once I got the whole picture figured out, I'll write
some easy to follow documentation on a basic setup.
ta, t.
On 10 November 2017 at 18:49, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> You can add v6 addresses to Address= and AllowedIPs=. These take comma
> separated lists.
>
[-- Attachment #2: Type: text/html, Size: 834 bytes --]
prev parent reply other threads:[~2017-11-11 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 2:35 timsan
2017-11-11 2:49 ` Jason A. Donenfeld
2017-11-11 4:01 ` timsan [this message]
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='CALrp0MGuzcT=Z_xwTjjWnw3LPXOLvBqm0pZua01jCSou93D=Yg@mail.gmail.com' \
--to=timsan@xs4all.nl \
--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).