From: Ryan Govostes <rgovostes@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: macOS: WireGuard traffic sent over wrong interface
Date: Sat, 19 Mar 2022 14:34:30 -0400 [thread overview]
Message-ID: <CAMtyXZYQ6_Y9Tfa+3dHgXS1yWfV7xBpYBK7tO8_yegLJgxKGoQ@mail.gmail.com> (raw)
I wasn't able to find a bug tracker so apologies if this is a known issue.
I’m running macOS 12.3 with WireGuard 1.0.15 from the App Store.
My WireGuard peer is on my corporate network, to which I am first
connecting via Palo Alto Networks GlobalProtect.
If I use `route get <peer IP>` then macOS reports that it will send
traffic to the peer via the GlobalProtect tunnel interface. And I can
confirm this by sending UDP traffic from macOS to the peer server and
monitoring it going over that interface using Wireshark.
However, when I then turn on the WireGuard tunnel, it sends its
traffic over en0, my Wi-Fi interface, over which the peer is not
reachable.
As a workaround, I can have my endpoint configured as localhost and
use socat to redirect traffic over the correct interface:
socat -T 3600 udp-listen:51820,reuseaddr,fork udp:<peer>:51820
Ryan
reply other threads:[~2022-03-21 19:44 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=CAMtyXZYQ6_Y9Tfa+3dHgXS1yWfV7xBpYBK7tO8_yegLJgxKGoQ@mail.gmail.com \
--to=rgovostes@gmail.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).