From: "Aaron W. Swenson" <aaron@grandmasfridge.org>
To: Roman Mamedov <rm@romanrm.net>
Cc: wireguard@lists.zx2c4.com
Subject: Re: IPv6 Not Getting Past Server
Date: Sat, 23 Feb 2019 07:28:57 -0500 [thread overview]
Message-ID: <c44b33fee92ce54d1cf5bc7f308b07a4@grandmasfridge.org> (raw)
In-Reply-To: <20180925102051.025c281f@natsu>
On 2018-09-25 01:20, Roman Mamedov wrote:
> On Sat, 22 Sep 2018 15:55:22 -0400
> "Aaron W. Swenson" <aaron@grandmasfridge.org> wrote:
>
>> I’m going to use the official documentation IP addresses. I am using
>> real IPv6
>> addresses and not using NAT66. Naturally, NAT is being used for IPv4.
>> Here are
>> the definitions I’m using:
>>
>> Server Public IPv6: 2001:DB8::DEAD:F00D/64
>> Server Public IPv4: 192.0.2.1
>> Routed /116: 2001:DB8::BEEF:3000/116
>
> Are you sure you have a *routed* subnet from your ISP? Moreover, does
> this /116 lie within the above /64? (in your obfuscated example it
> does)
Took me a little while to follow up, I know, but this was the issue
precisely.
I requested a /64 to replace the /116, and now everything is working
beautifully. I made no other changes besides updating the IPv6
addresses.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-02-23 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-22 19:55 IPv6 Not Getting Past Server Aaron W. Swenson
2018-09-25 5:20 ` Roman Mamedov
2019-02-23 12:28 ` Aaron W. Swenson [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=c44b33fee92ce54d1cf5bc7f308b07a4@grandmasfridge.org \
--to=aaron@grandmasfridge.org \
--cc=rm@romanrm.net \
--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).