iOS Ziti Mobile Edge not working on iOS 18.5 anymore

Tunneler Apps
1

Hi there,
@scareything thanks for the reply in the other thread.
I did submit the “send feedback” bundle and tried reinstalling the VPN config, however it still doesn’t work.
The service works on other devices, only on the iOS devices it doesn’t. Any other service doesn’t work as well.
I suspect it has something to do with iOS 18.5 because it stopped working on multiple devices.

Thanks
Dominik

2

Thanks Dominik, I see the feedback email and I'm looking at it now.

1 Like
3

Does it look to you like the tunnel is stopping itself? I see a lot of shutdowns that happen very shortly after the tunnel is started. They look like this:

[2025-06-13T05:44:44:692Z]    INFO MobilePacketTunnelProvider:PacketTunnelProvider.swift:227 stopTunnel()

I'm still looking at it, but wanted to ask if you've observed the the tunnel seeming to turn itself off. Also are there any crash reports from MobilePacketTunnelProvider? They would be in iOS Settings -> Privacy & Security -> Analytics & Improvements -> Analytics Data.

Thanks

4

I don’t see any crash reports for the tunnel. I did try though to deactivate and reactivate the tunnel quite a couple times so if it’s with a couple of seconds delay, that might be it?

1 Like
5

As you mentioned there is a lack of any incoming packets (other than DNS packets), until the very last run in your log, where the exclusion routes (which prevent us from intercepting controller and edge router connections) had not yet been applied. So in this run we see a few of these connections. While we don't normally want to intercept these connections, seeing it happen did give me some confidence that it is possible to intercept packets at all:

[2025-06-13T11:50:44:230Z]   TRACE MobilePacketTunnelProvider:PacketTunnelProvider.swift:287 readPacketFlow() read 1 packets
(60045)[2025-06-13T11:50:44.233Z]   TRACE tunnel-sdk:tunnel_tcp.c:372 recv_tcp() received segment src[tcp:100.64.0.1:51653] dst[tcp:54.228.101.175:443] flags[SYN]
(60045)[2025-06-13T11:50:44.233Z]   TRACE tunnel-sdk:tunnel_tcp.c:383 recv_tcp() no intercepted addresses match tcp:54.228.101.175:443

This makes me wonder if our tun interface subnet 100.64.0.1/18 is conflicting with one that's supplied by your cellular provider or ISP. Could you try changing the tunnel IP address and subnet mask to something different and smaller? Like ip 100.68.0.1 and mask 255.240.0.0 in tunnel settings?

1 Like
6

Thank you that was indeed the problem.
After I changed the IP address and subnet, it started to work fine again.
I suppose the ISP made some kind of change within their subnet as the other device also has the same ISP.