Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Jeff Squyres <jeff@squyres.com>
To: Laura Smith <n5d9xq3ti233xiyif2vp@protonmail.ch>
Cc: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: Two small Wireguard frustrations on Mac & Apple iOS
Date: Mon, 28 Sep 2020 09:53:20 -0400	[thread overview]
Message-ID: <CAOmeisXta6daStnhuh2J9U6TL=7N6QOfY7G-O_e4OnWV9JT+4Q@mail.gmail.com> (raw)
In-Reply-To: <_6C1kLqz08ZzDSlyJFksWGJkEabvSXjImi0ZpRw7s5bjUcMYcUlzSTUg1aUVzhnmAyYvGtMpSYff1DvoDw_vbLxel15gdVmkxtAjZWDp-w8=@protonmail.ch>

FWIW, I first publicly reported this same problem with iOS in Jan
2020: https://lists.zx2c4.com/pipermail/wireguard/2020-January/004860.html
(with much more followup information in
https://lists.zx2c4.com/pipermail/wireguard/2020-January/004874.html).

It still happens periodically on my iOS 13 (and now iOS 14) iPhone 8+.
It happens with much lower frequency than it used to, but it still
definitely happens sometimes.

-- 
{+} Jeff Squyres

  parent reply	other threads:[~2020-10-01 11:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-23 18:34 Laura Smith
2020-08-27  8:29 ` Alexander Burke
2020-09-11  1:08   ` Eddie Jones
2020-09-28 12:59     ` Laura Smith
2020-09-28 13:20       ` Jonny
2020-09-28 13:53       ` Jeff Squyres [this message]
     [not found]       ` <CAPMuNSpqK6BOL4h9zkSNyEO4UJroDDMnU5GJprvAyDeTdXW=kw@mail.gmail.com>
2020-09-28 20:49         ` Dimitri J. Panagiotou
2020-09-30  1:25       ` Jeff Squyres
2020-10-01  1:04       ` Brian Gregory
2020-10-01 11:17       ` Jason A. Donenfeld
2020-10-08 14:04         ` Laura Smith
     [not found]   ` <a473a088-91f8-10bb-7522-67c989c7a052@k8s.local>
2020-09-15 23:29     ` Eddie Jones
2020-10-01 11:14 ` Jason A. Donenfeld
2020-10-01 11:23 ` Jasper Knockaert
2020-10-01 11:57   ` Jason A. Donenfeld

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='CAOmeisXta6daStnhuh2J9U6TL=7N6QOfY7G-O_e4OnWV9JT+4Q@mail.gmail.com' \
    --to=jeff@squyres.com \
    --cc=n5d9xq3ti233xiyif2vp@protonmail.ch \
    --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).