Development discussion of WireGuard
 help / color / mirror / Atom feed
* macOS: WireGuard traffic sent over wrong interface
@ 2022-03-19 18:34 Ryan Govostes
  0 siblings, 0 replies; only message in thread
From: Ryan Govostes @ 2022-03-19 18:34 UTC (permalink / raw)
  To: wireguard

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

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


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-03-21 19:44 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-03-19 18:34 macOS: WireGuard traffic sent over wrong interface Ryan Govostes

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).