Development discussion of WireGuard
 help / color / mirror / Atom feed
From: John <graysky@archlinux.us>
To: Jeff Squyres <jeff@squyres.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Problem with iOS WireGuard client
Date: Wed, 15 Jan 2020 13:47:38 -0500	[thread overview]
Message-ID: <CAO_nJAa-RFk29B8_qzTJZFA62p3qCPEYXqQHn_-5FXC6YiSM-A@mail.gmail.com> (raw)
In-Reply-To: <CAOmeisV22+6uKgX0ja+i4gnGWo5fUWhk6Je9PiFvf7itcY+3uQ@mail.gmail.com>

Your issue sounds similar to mine linked below.  Do you find this
endless failed handshakes to be when you're connected to any network
or just a specific one?  I routinely connect to 4 networks in my
travels and only 1 of them causes the problem.

Link to my post:
https://lists.zx2c4.com/pipermail/wireguard/2020-January/004858.html

On Wed, Jan 15, 2020 at 1:31 PM Jeff Squyres <jeff@squyres.com> wrote:
>
> Over the past ~2 months, I have been experiencing an intermittent problem with the iOS WireGuard client: sometimes the WireGuard client gets into a loop of endlessly-failing handshakes, which therefore stops all traffic.  If I disconnect/reconnect the WireGuard tunnel, the handshakes succeed, and traffic starts flowing normally again.
>
> This happens multiple times a day.  It has been happening with multiple versions of iOS starting with 12.x, and now with 13.x.  WireGuard for iOS version 0.0.20191015(15), Go Backend 0.0.2019.0909.
>
> I can send more details (logs, screenshots / screencast, etc.), but first: is this the right list to ask questions about the iOS client?  If not, can someone point me in the right direction?
>
> Additionally, another oddity: when my Wireguard tunnel is connected properly and I visit whoer.net or zx2c4.com/ip, sometimes I see my WireGuard endpoint's IPv6 address, and sometimes I see my WireGuard endpoint's IPv4 address.  This happens regardless of what network my iOS device (i.e., my phone) is on.  Sometimes when the IPv6 address is shown and I refresh the page a few times (over the span of a few seconds), it switches to show the endpoint's IPv4 address.
>
> Thanks!
>
> --
> {+} Jeff Squyres
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2020-01-22 19:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-12 15:17 Jeff Squyres
2020-01-15 18:47 ` John [this message]
2020-01-16  2:44   ` Jeff Squyres
2020-01-27  7:38 Problem with iOS WireGuard Client Abner Zhang

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=CAO_nJAa-RFk29B8_qzTJZFA62p3qCPEYXqQHn_-5FXC6YiSM-A@mail.gmail.com \
    --to=graysky@archlinux.us \
    --cc=jeff@squyres.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).