From: "Hasan Berkay Çağır" <berkay@cagir.me>
To: Adam Cooper <adam@acpr.dev>
Cc: wireguard@lists.zx2c4.com
Subject: Re: MacOS IPv6 not functioning without custom static route
Date: Tue, 21 Jul 2020 15:12:48 +0200 [thread overview]
Message-ID: <165a92238115e99b03740768d843a20f@cagir.me> (raw)
In-Reply-To: <CAN00TTomuZoagZF2McBkDW1ZimSouN-jnDLm+Hq7OKeH-sF9zg@mail.gmail.com>
On 15/07/2020 14:14, Adam Cooper wrote:
> ...
> Probably worth mentioning that I tried to replace ::/0 with ::/1,
> 8000::/1 but that just results in completely broken connectivity in
> IPv6 and IPv4 - which may be another issue in and of itself.
Did you try only having "::/1, 8000::/1" in the AllowedIPs option? I had
a default route creation issue myself where I'm only trying to tunnel
IPv6 through; and having this actually solved it.
$ netstat -nr
Routing tables
Internet:
...
Internet6:
Destination Gateway
Flags Netif Expire
::/1 link#14
UCS utun2
default fe80::%utun0
UGcI utun0
default fe80::%utun1
UGcI utun1
default fe80::%utun3
UGcI utun3
default [ public IPv6 ]
UGcI utun2
If just "::/1, 8000::/1" solves the IPv6 issue, I guess you can give it
a try with "0.0.0.0/0, ::/1, 8000::/1" to see if both routes are created
properly?
Best,
Berkay
next prev parent reply other threads:[~2020-07-21 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 12:14 Adam Cooper
2020-07-21 13:12 ` Hasan Berkay Çağır [this message]
2020-07-21 13:29 ` Adam Cooper
2020-07-21 13:49 ` Hasan Berkay Çağır
2020-07-21 13:58 ` Adam Cooper
2020-07-21 14:03 ` Hasan Berkay Çağır
2020-07-21 13:50 ` Adam Cooper
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=165a92238115e99b03740768d843a20f@cagir.me \
--to=berkay@cagir.me \
--cc=adam@acpr.dev \
--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).