IPv6 Not Getting Past Server
Aaron W. Swenson
aaron at grandmasfridge.org
Sat Feb 23 13:28:57 CET 2019
On 2018-09-25 01:20, Roman Mamedov wrote:
> On Sat, 22 Sep 2018 15:55:22 -0400
> "Aaron W. Swenson" <aaron at 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.
More information about the WireGuard
mailing list