From: "Joachim Tingvold" <joachim@tingvold.com>
To: wireguard@lists.zx2c4.com
Subject: Mac OS + IPv6 via WireGuard: "Network is down"
Date: Sat, 03 Aug 2019 16:54:18 +0200 [thread overview]
Message-ID: <3C95A64B-469C-4291-BB7D-51C80FBB8CA9@tingvold.com> (raw)
Hi,
I've been trying out WireGuard for some time now, and I've encountered
somewhat of an issue.
Whenever I try to reach resources via IPv6 using their FQDN, when the
Mac only has IPv4 available via it's default interface (but IPv6 via
WireGuard), things behave strangely; I can communicate with IPv6-hosts
using their IPv6 address, but not their FQDN.
Anyone knows what could cause this, and how to solve it?
jocke@keklolwtf: ~ $ ssh foo.jocke.no
ssh: Could not resolve hostname foo.jocke.no: nodename nor servname
provided, or not known
jocke@keklolwtf: ~ $ ssh -6 foo.jocke.no
ssh: connect to host foo.jocke.no: Network is down
jocke@keklolwtf: ~ $ dig foo.jocke.no aaaa +short
2001:67c:197c:bar::1
jocke@keklolwtf: ~ $ host foo.jocke.no
foo.jocke.no has IPv6 address 2001:67c:197c:bar::1
jocke@keklolwtf: ~ $ ping6 foo.jocke.no -c1
PING6(56=40+8+8 bytes) 2001:67c:197c:foo::1 --> 2001:67c:197c:bar::1
16 bytes from 2001:67c:197c:bar::1, icmp_seq=0 hlim=61 time=38.701 ms
--- foo.jocke.no ping6 statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 38.701/38.701/38.701/0.000 ms
jocke@keklolwtf: ~ $ ssh 2001:67c:197c:bar::1 "date"
Sat Aug 3 16:45:50 CEST 2019
jocke@keklolwtf: ~ $ netstat -rn
[…]
Internet6:
Destination Gateway
Flags Netif Expire
default 2001:67c:197c:foo::
UGcI utun1
2001:67c:197c::/48 link#29
UCS utun1
jocke@keklolwtf: ~ $ ifconfig utun1
utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1420
inet6 fe80::<snip>%utun1 prefixlen 64 scopeid 0x1d
inet6 2001:67c:197c:foo::1 prefixlen 120
nd6 options=201<PERFORMNUD,DAD>
###
[Interface]
PrivateKey = <snip>
Address = 2001:67c:197c:foo::1/128
[Peer]
PublicKey = <snip>
AllowedIPs = 2001:67c:197c::/48
Endpoint = <snip>
###
--
Joachim
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-08-25 15:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3C95A64B-469C-4291-BB7D-51C80FBB8CA9@tingvold.com \
--to=joachim@tingvold.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).