wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Chris Gaffney <gaffneyc@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard on MacOS Catalina randomly deletes config
Date: Wed, 16 Oct 2019 22:34:50 +0200	[thread overview]
Message-ID: <CAHmME9p4PF=FA0yxQh_vmTgf7SZfiUuTqx0RPip1gBXPmrH2Xw@mail.gmail.com> (raw)
In-Reply-To: <761368C4-83F7-41E0-85BD-EDFC51D3F3A0@gmail.com>

This appears to be a bug in macOS 10.15. I've informed Apple, and
they're looking into it.

The log file you gave has the line in it:

> 2019-10-10 07:25:16.071772: [APP] Tunnel 'Office' connection status changed to 'invalid'

If you look at your system logs for that timestamp, that will
correspond with a line emitted from com.apple.networkextension like:

> Removing configuration Office because the corresponding VPN application has been removed.

Reverse engineering
/System/Library/Frameworks/NetworkExtension.framework/Versions/A/NetworkExtension
indicates that this comes from the call chain:

-[NEConfigurationManager
handleApplicationsRemoved:completionQueue:withCompletionHandler:]
-->
__90__NEConfigurationManager_handleApplicationsRemoved_completionQueue_withCompletionHandler___block_invoke
-->
__90__NEConfigurationManager_handleApplicationsRemoved_completionQueue_withCompletionHandler___block_invoke_2

So I assume that some kind of inclusion check is failing when it
shouldn't, or some kind of app store notification is being triggered
when it shouldn't.

Jason
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2019-10-16 20:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10 13:01 Wireguard on MacOS Catalina randomly deletes config Chris Gaffney
2019-10-16 20:34 ` Jason A. Donenfeld [this message]

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='CAHmME9p4PF=FA0yxQh_vmTgf7SZfiUuTqx0RPip1gBXPmrH2Xw@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=gaffneyc@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).