From: Michael Lennartz <miclman.0x0efbd3@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Wireguard on Mac not working through a corporate VPN
Date: Thu, 25 Feb 2021 17:56:50 +0100 [thread overview]
Message-ID: <80702DEB-2D7D-4B4C-A268-3E4C8FCB746C@gmail.com> (raw)
Hi team,
Since a while already we’re testing Wireguard in our environment and I think, it’s a great project.
The focus is currently on Mac clients, where we’ve used the CLI version from homebrew so far very successfully.
It’s important to note, the we’re reaching the server peer via another (Corporate) VPN interface.
Recently we’ve updated to MacOS 11.2 (Big Sur) on the M1 architecture and the (most recent) CLI version of Wireguard stopped working:
When I now try to connect to the server peer, the "wg-quick up …” hangs at the first ‘wg set utun3 peer …’ command.
Then we try to use the GUI version from the AppStore, which seems to establish the tunnel interface and routing correctly. But we can’t see any traffic passing the corporate VPN interface towards the server peer. Even not the initial handshake.
Do you have some hints, if this setup is supposed to be working ? Or any suggestion where to look at ?
Br,
Michael
reply other threads:[~2021-02-25 18:01 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=80702DEB-2D7D-4B4C-A268-3E4C8FCB746C@gmail.com \
--to=miclman.0x0efbd3@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).