From: wireguard@p-np.de
To: wireguard@lists.zx2c4.com
Subject: Port dependent issues on iOS 13
Date: Tue, 24 Sep 2019 11:36:48 +0200 (CEST) [thread overview]
Message-ID: <1394974820.30160.1569317808871@office.mailbox.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 985 bytes --]
Hello,
in place upgrades from iOS 12 -> iOS 13 (release) seem to work well in general. But there is a bizarre issue depending on remote endpoint ports. If you have, in my case, 4500/UDP configured as remote endpoint the tunnel does not send or receive traffic. Changing it to any other port works. Changing back to 4500/UDP breaks it again reproducibly. For others, documented here https://www.reddit.com/r/WireGuard/comments/d6in39/wg_broken_on_ios_13/ , it is 1500/UDP, in #WireGuard there has been a documented issue for 500/UDP not working.
I have AnyConnect installed in parallel and checked, whether that's related. But removing and resetting Network settings did not fix port 4500 for me.
As there is no port number dependent branching in the WireGuard-iOS code base, this is likely an iOS regression. Does any one of you have a working channel to Apple to report this?
Thank you for an else excellent product. Let me know if I can be of any help.
Best regards,
Christian
[-- Attachment #1.2: Type: text/html, Size: 1408 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-09-25 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 9:36 wireguard [this message]
2019-09-25 22:01 ` Port dependent issues on iOS 13 John huttley
2019-09-26 0:13 ` Reid Rankin
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=1394974820.30160.1569317808871@office.mailbox.org \
--to=wireguard@p-np.de \
--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).