From: John huttley <john@mib-infotech.co.nz>
To: wireguard@p-np.de, wireguard@lists.zx2c4.com
Subject: Re: Port dependent issues on iOS 13
Date: Thu, 26 Sep 2019 10:01:57 +1200 [thread overview]
Message-ID: <bd2be5bf-13c6-8c38-e4e1-705fcfa98f73@mib-infotech.co.nz> (raw)
In-Reply-To: <1394974820.30160.1569317808871@office.mailbox.org>
[-- Attachment #1.1: Type: text/plain, Size: 1387 bytes --]
Hi,
Port 4500 is the IPSec UDP nat port and 500 is IKE.
Anyconnect uses ISPEC so I think those ports are simply in use.
--John
On 24/09/19 9:36 PM, wireguard@p-np.de wrote:
> 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
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
[-- Attachment #1.2: Type: text/html, Size: 2663 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-09-25 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 9:36 Port dependent issues on iOS 13 wireguard
2019-09-25 22:01 ` John huttley [this message]
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=bd2be5bf-13c6-8c38-e4e1-705fcfa98f73@mib-infotech.co.nz \
--to=john@mib-infotech.co.nz \
--cc=wireguard@lists.zx2c4.com \
--cc=wireguard@p-np.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.