From: Glenn Schmidt <glenn@glenn.id.au>
To: wireguard@lists.zx2c4.com
Subject: WireGuard on macOS stopped working after 1.0.10 update
Date: Wed, 16 Dec 2020 23:52:31 +0000 [thread overview]
Message-ID: <A9F23E70-C8AA-4C54-99E4-63E2E40FE0FA@glenn.id.au> (raw)
After I installed the new WireGuard update from the Mac app store, I can’t connect my tunnel. The message in the UI is "Unable to apply network settings to tunnel object."
I’m using macOS 10.15.7. I've tried rebooting, removing and re-importing tunnel configs, deleting and re-installing the WireGuard app.
Here’s a dump of possibly-relevant warnings in Console.app during a connection attempt:
error 10:47:01.801958+1100 WireGuardNetworkExtension Bootstrapping; external subsystem UIKit_PKSubsystem refused setup
error 10:47:01.837971+1100 nehelper -[NWPrivilegedHelper startXPCListener]_block_invoke client pid 111 does not have any known entitlement
error 10:47:01.838068+1100 configd networkd_privileged_check_interface_settings_block_invoke received XPC_ERROR_CONNECTION_INVALID
error 10:47:06.947361+1100 WireGuardNetworkExtension Starting tunnel failed with setTunnelNetworkSettings timing out
error 10:47:06.955318+1100 nesessionmanager address is loopback
error 10:47:06.959919+1100 nesessionmanager address is loopback
error 10:47:11.985280+1100 WireGuardNetworkExtension SIOCGIFMTU failed: Device not configured
error 10:47:11.985358+1100 WireGuardNetworkExtension NEVirtualInterfaceAdjustReadBufferSize: interface_get_mtu failed (6), defaulting to max mtu
error 10:47:11.988228+1100 neagent [u E64DEC42-DC15-401F-8590-DAFE723FB670:m (null)] [<private>(<private>)] Connection to plugin interrupted while in use.
error 10:47:11.989727+1100 neagent [u E64DEC42-DC15-401F-8590-DAFE723FB670:m (null)] [<private>(<private>)] Connection to plugin invalidated while in use.
next reply other threads:[~2020-12-17 1:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 23:52 Glenn Schmidt [this message]
2020-12-17 1:43 ` WireGuard on macOS stopped working after 1.0.10 update Jason A. Donenfeld
2020-12-17 2:09 ` Glenn Schmidt
2020-12-17 21:53 ` Jason A. Donenfeld
2020-12-17 22:34 ` Nicolas CAPEYRON
[not found] ` <CAA6-MF8ZZ1eD+7wTfgzuGaiw8JPM+WiivJ0CxBja3-GZ=GXMaA@mail.gmail.com>
2020-12-18 9:19 ` Jason A. Donenfeld
2020-12-18 23:53 ` Jason A. Donenfeld
2020-12-19 0:11 ` Jacob Lambert
2020-12-19 10:40 ` Jason A. Donenfeld
2020-12-17 15:19 Nicolas CAPEYRON
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=A9F23E70-C8AA-4C54-99E4-63E2E40FE0FA@glenn.id.au \
--to=glenn@glenn.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.