Port dependent issues on iOS 13

Port dependent issues on iOS 13

[wireguard]

[-- 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

Re: Port dependent issues on iOS 13

[John huttley]

[-- 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

Re: Port dependent issues on iOS 13

[Reid Rankin]

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

FWIW, all those ports (4500, 1500, 500) seem to work for me with iOS 13 and
WireGuard for iOS build 0.0.20190610 (13).

On Wed, Sep 25, 2019 at 6:03 PM John huttley <john@mib-infotech.co.nz>
wrote:

> 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 listWireGuard@lists.zx2c4.comhttps://lists.zx2c4.com/mailman/listinfo/wireguard
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>

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

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

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