WireGuard Archive on lore.kernel.org
 help / color / Atom feed
From: Jeff Squyres <jeff@squyres.com>
To: wireguard@lists.zx2c4.com
Subject: Problem with iOS WireGuard client
Date: Sun, 12 Jan 2020 10:17:00 -0500
Message-ID: <CAOmeisV22+6uKgX0ja+i4gnGWo5fUWhk6Je9PiFvf7itcY+3uQ@mail.gmail.com> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 1226 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 2430 bytes --]

<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:#000000">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.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:#000000"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:#000000">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.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:#000000"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:#000000">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?</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:#000000"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:#000000">Additionally, another oddity: when my Wireguard tunnel is connected properly and I visit <a href="http://whoer.net">whoer.net</a> or <a href="http://zx2c4.com/ip" rel="noreferrer" target="_blank" style="font-family:Arial,Helvetica,sans-serif">zx2c4.com/ip</a>, sometimes I see my WireGuard endpoint&#39;s IPv6 address, and sometimes I see my WireGuard endpoint&#39;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&#39;s IPv4 address.</div><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">Thanks!</div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">{+} Jeff Squyres</div></div></div>

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

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

             reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-12 15:17 Jeff Squyres [this message]
2020-01-15 18:47 ` John
2020-01-16  2:44   ` Jeff Squyres

Reply instructions:

You may reply publically 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=CAOmeisV22+6uKgX0ja+i4gnGWo5fUWhk6Je9PiFvf7itcY+3uQ@mail.gmail.com \
    --to=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

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com
	public-inbox-index wireguard

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git