WireGuard Archive on lore.kernel.org
 help / color / Atom feed
* Port dependent issues on iOS 13
@ 2019-09-24  9:36 wireguard
  2019-09-25 22:01 ` John huttley
  0 siblings, 1 reply; 3+ messages in thread
From: wireguard @ 2019-09-24  9:36 UTC (permalink / raw)
  To: 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 --]

<!doctype html>
<html>
 <head> 
  <meta charset="UTF-8"> 
 </head>
 <body>
  <div>
   Hello,
  </div>
  <div>
   <br>
  </div>
  <div>
   in place upgrades from iOS 12 -&gt; iOS 13 (release) seem to work well in general. But there is a bizarre issue depending on 
   <strong>remote</strong> 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 
   <a href="https://www.reddit.com/r/WireGuard/comments/d6in39/wg_broken_on_ios_13/">here</a>&nbsp;, it is 1500/UDP, in #WireGuard there has been a documented issue for 500/UDP not working.
  </div>
  <div>
   <br>
  </div>
  <div>
   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.
  </div>
  <div>
   <br>
  </div>
  <div>
   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?
  </div>
  <div>
   <br>
  </div>
  <div>
   Thank you for an else excellent product. Let me know if I can be of any help.
  </div>
  <div>
   <br>
  </div>
  <div>
   Best regards,
  </div>
  <div>
   <br>
  </div>
  <div>
   Christian
  </div> 
 </body>
</html>

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

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, back to index

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-24  9:36 Port dependent issues on iOS 13 wireguard
2019-09-25 22:01 ` John huttley
2019-09-26  0:13   ` Reid Rankin

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