From: Alan Graham <alan@meshify.app>
To: Anatoli <me@anatoli.ws>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard Configurations Gone After iOS 15 Upgrade
Date: Wed, 22 Sep 2021 16:53:59 -0700 [thread overview]
Message-ID: <CAMeHLtyiG_nKz2BAi+_bD4HBZu-CCVb8N7nqBn6H42rZ5QKv0w@mail.gmail.com> (raw)
In-Reply-To: <23be4054-af4f-b9a2-c01f-6e6dc33096a4@anatoli.ws>
Hi,
I have an iOS 15 iPhone 12 Pro Max with three tunnels configured. The
upgrade from 14 to 15 busted the configs as described. I deleted and
recreated one of the tunnels and it worked fine. I updated to today's
bits (which appear to have been released in record time). The tunnel
that I deleted and recreated is still working fine. The other two
tunnels now have red backgrounds and I can no longer click them to see
the (empty) details like I could in the older build. Trying to
activate it does not work (it does not, however, rapidly switch
between on and off). It looks like I can delete them by swiping left
to reveal a delete button, but I can leave them in their current state
for more testing. I did not have on-demand turned on for any of the
tunnels so I cannot speak to that partially working state. I have
iCloud keychain on, so that doesn't appear to be a fix/workaround. I
also have an iPad that I haven't upgraded yet, so I should be able to
test the upgrade path, but I'm not sure these bits resolve the
problem.
Best regards,
Alan
On Wed, Sep 22, 2021 at 4:26 PM Anatoli <me@anatoli.ws> wrote:
>
> Sorry, I replied before I've got your mail about the new version.
>
> This is how the old version was behaving. Haven't tested yet the new version.
> I'll test it and report today or tomorrow.
>
>
> On 22/9/21 19:26, Jason A. Donenfeld wrote:
> > On Wed, Sep 22, 2021 at 4:24 PM Anatoli <me@anatoli.ws> wrote:
> >>
> >> I can confirm that recreating the tunnel from scratch does work. So the problem is that the tunnel settings become corrupted when iOS is upgraded from 13.x / 14.x to 15.0.
> >
> > What are you testing? The new version of the app or the old one? Does
> > the new one corrupt settings or only the old one? Precision is
> > important here.
> >
prev parent reply other threads:[~2021-09-22 23:54 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 0:23 WireGuard Configurations Gone After iOS 15 Upgrade Eddie
2021-09-22 0:28 ` Eddie
2021-09-22 0:45 ` Miguel Arroz
2021-09-22 3:14 ` Jason A. Donenfeld
2021-09-22 4:04 ` Anatoli
2021-09-22 4:50 ` Jason A. Donenfeld
2021-09-22 5:17 ` Jason A. Donenfeld
[not found] ` <CAMaqUZ2dTaOJ3oPex0pQxBM9njHA7rW5Hb69MvG645n+ya_jhQ@mail.gmail.com>
2021-09-22 13:59 ` Jason A. Donenfeld
2021-09-22 14:47 ` Andrew Fried
2021-09-22 15:23 ` Eddie
2021-09-22 16:50 ` Miguel Arroz
2021-09-22 19:28 ` Jason A. Donenfeld
2021-09-22 19:58 ` Jeffrey Walton
2021-09-22 22:15 ` Jason A. Donenfeld
2021-09-22 22:31 ` Miguel Arroz
2021-09-22 22:35 ` Jason A. Donenfeld
2021-09-22 22:42 ` Miguel Arroz
2021-09-22 22:43 ` Jason A. Donenfeld
2021-09-22 22:45 ` Eddie
2021-09-22 22:55 ` Eddie
2021-09-22 22:55 ` Jason A. Donenfeld
[not found] ` <814501e8-c2c8-1e0a-2f30-fd83fb7769ec@attglobal.net>
[not found] ` <CAHmME9p5C3bGT=gXV6WQ5HNOBTtitXdGwKm7EaOv_bnVVvX5vA@mail.gmail.com>
2021-09-22 22:56 ` Eddie
2021-09-23 1:34 ` Jason A. Donenfeld
2021-09-23 2:49 ` Jason A. Donenfeld
2021-09-23 2:54 ` Miguel Arroz
2021-09-23 3:06 ` Miguel Arroz
2021-09-23 3:09 ` Jason A. Donenfeld
2021-09-23 3:19 ` Miguel Arroz
2021-09-23 3:22 ` Jason A. Donenfeld
2021-09-23 3:57 ` Jason A. Donenfeld
2021-09-23 4:13 ` Jason A. Donenfeld
2021-09-23 4:21 ` Miguel Arroz
2021-09-23 14:41 ` Anatoli
2021-09-23 17:26 ` Jason A. Donenfeld
2021-09-24 2:17 ` Jason A. Donenfeld
2021-09-24 8:05 ` Alan Graham
2021-09-22 22:24 ` Anatoli
2021-09-22 22:26 ` Jason A. Donenfeld
2021-09-22 23:12 ` Anatoli
2021-09-22 23:53 ` Alan Graham [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=CAMeHLtyiG_nKz2BAi+_bD4HBZu-CCVb8N7nqBn6H42rZ5QKv0w@mail.gmail.com \
--to=alan@meshify.app \
--cc=Jason@zx2c4.com \
--cc=me@anatoli.ws \
--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).