From: Dmitrij Gusev <dmitrij.gusev@zealid.com>
To: wireguard@lists.zx2c4.com
Subject: macOS wireguard client: traffic to wireguard interface self IP travels through VPN server
Date: Wed, 6 Jan 2021 18:46:40 +0200 [thread overview]
Message-ID: <5A7F7841-4B7F-4E7A-AB39-32EC787D14E0@zealid.com> (raw)
Hello.
We just started to use the WireGuard VPN in our company.
Thanks for the great software!
I discovered, that while using the macOS wireguard client a traffic to the wireguard interface self IP travels through VPN server.
So for example if I ping wireguard interface self IP from macOS machine - both echo-request and echo-reply goes through WireGuard VPN server’s nftables “forward" chain.
Normally this kind of traffic is expected to travel locally.
Is it a bug in the WireGuard macOS client or is it related to macOS network (tunnel) stack glitches?
Are you already aware of a such behaviour?
macOS Big Sur version 11.1
WireGuard app version 1.0.12 (22)
macOS wireguard config looks like this:
[Interface]
PrivateKey = <PRIV KEY>
Address = 10.0.0.5/24
DNS = 10.1.0.53, example.local
[Peer]
PublicKey = <PUB KEY>
AllowedIPs = 0.0.0.0/0
Endpoint = vpn-srv.example.com:28283
PersistentKeepalive = 20
Thanks,
Dmitrij Gusev
System Architect
dmitrij.gusev@zealid.com
+370 6330 5550
ZealiD
reply other threads:[~2021-01-07 21:56 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=5A7F7841-4B7F-4E7A-AB39-32EC787D14E0@zealid.com \
--to=dmitrij.gusev@zealid.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).