not connecting with iOS devices

[oIche]

Hi there,

we have some iPhones which can not connect. It is with actual OpenVPN Connect 3.4. (5457)

iPhones have actual firmware. Only a handfull devices are affected. The connection can etablish if the device is WLAN, but if it is connected via LTE/5G it is not working. Any ideas?

Code: Select all

[Oct 12, 2023, 11:48:05] START CONNECTION

[Oct 12, 2023, 11:48:05] ----- OpenVPN Start -----
OpenVPN core 3.8.2connect1 ios arm64 64-bit

[Oct 12, 2023, 11:48:05] OpenVPN core 3.8.2connect1 ios arm64 64-bit

[Oct 12, 2023, 11:48:05] Frame=512/2112/512 mssfix-ctrl=1250

[Oct 12, 2023, 11:48:05] NOTE: This configuration contains options that were not used:

[Oct 12, 2023, 11:48:05] Unsupported option (ignored)

[Oct 12, 2023, 11:48:05] 1 [persist-tun]

[Oct 12, 2023, 11:48:05] 2 [persist-key]

[Oct 12, 2023, 11:48:05] 3 [data-ciphers] [AES-128-CBC:AES-256-GCM:AES-256-CBC:AES-256-OFB]

[Oct 12, 2023, 11:48:05] 4 [data-ciphers-fallback] [AES-256-OFB]

[Oct 12, 2023, 11:48:05] 8 [resolv-retry] [infinite]

[Oct 12, 2023, 11:48:05] 13 [explicit-exit-notify]

[Oct 12, 2023, 11:48:05] EVENT: RESOLVE

[Oct 12, 2023, 11:48:05] Endpoint address family (IPv6) is incompatible with transport protocol (udp4)

[Oct 12, 2023, 11:48:05] EVENT: DISCONNECTED

[Oct 12, 2023, 11:48:05] EVENT: CORE_THREAD_ERROR remote_list_error: current remote server endpoint is undefined [ERR]

[Oct 12, 2023, 11:48:05] EVENT: CORE_THREAD_DONE

[Oct 12, 2023, 11:48:05] EVENT: DISCONNECT_PENDING

[Oct 12, 2023, 11:48:05] Raw stats on disconnect:

[Oct 12, 2023, 11:48:05] Performance stats on disconnect:
CPU usage (microseconds): 27954
Network bytes per CPU second: 0
Tunnel bytes per CPU second: 0

And Endpoint address family (IPv6) is incompatible with transport protocol (udp4) seems the problem.

kind regards
Dirk

[Sunny9999]

Exactly same issues with some of your iphones.......
We run openvpn on pfsense 23.01
Any solutions yet ?

[oIche]

Hi,
I guess it is related to Deutsche Telekom. All our devices use this carrier. They switched their LTE/5G settings to pure IPv6. (APN internet.v6.telekom)
If you switch to the older APN ( internet.t-d1.de) all is fine. But changing the setting on all iphones is crap.
We connect to a pfsense 23.01 too. This pfsense is pure IPv4.
Now I am looking for a working solution to set up the pfsense correctly.

[Sunny9999]

f.... you´r right...working with the old ap.......
also try to get a solution....lets keep updated here.....

[bikefright]

I joined the forum just to reply to this thread with my current workaround(/fix?) for this. Quick and dirty!

I too use pfSense. Out of desperation I checked the "Legacy Client" checkbox in the pfSense OpenVPN Client Export Utility and re-imported the generated profile into iOS OpenVPN Connect.......voila, it worked . Brute force and ignorance FTW!

Comparing the old non-working profile with the "legacy" profile, the thing that stood out was the "remote" line:

not working
remote f.q.d.n 1194 udp4

working
remote f.q.d.n 1194 udp

I simply edited my original exported profiles that were created WITHOUT the "Legacy Client" box checked to this effect (changed udp4 to udp) and imported them into the iOS client. Didn't need to make any other "legacy" changes like ciphers etc.
Works for me - hope this helps someone

bikefright

[Graham]

Following on from the quick workaround from bikefright caused me to look further at my configuration.

I do not have 'UDP' added at the end of the 'remote' statement but opening up my .ovpn file in vi (unix editor) I saw that many lines had been terminated with ^M (carriage return "\r"), including the 'remote' line. I assume I had updated the file with another editor at some time, although it had worked on my iPhone with IOS 16, my new iPad just wouldn't play. After cleaning up the file by removing all carriage returns, it all worked fine.

just another slant on the above solution, in case it makes a difference. You will need an editor that shows up unwanted characters though - not Windows type editors.

Graham