buggy wrote
I did some investigation on the mobile network. "ip a" command returns 192.0.0.4 and an ip check online returns 77.63.xx.xxx . So it seems the mobile network is behind a nat router. Now it makes sense I have Issues.
I will try a different wifi network and see if it will work there
Still looking for a solution. The whole point of my vpn server is to connect to my home network on the road using the phones hotspot.
I guess have to change The subject title 🙂
I'm fighting the same issue and as I currently own a spare mobile carrier connectivity, I've discovered that using the mobile network of one of the mobile carrier, my VPN works fine both using UDP and TCP whereas the other ISP mobile network works only using TCP protocol.
This happens on Android version 14 and "OpenVPN Connect" app version 3.4.0.
Client side, the "OpenVPN Connect" app logs does not show any relevant clue, just a connection timeout message. I've also tested that there where no problems trying to send and receive UDP packets on Android using a terminal app.
Server side, during my tests, I've found that:
tcpdump -ni <my_network_interface> udp and port <my_openvpn_listening_port>
reports some incoming packets but the OpenVPN server running in a terminal session does report nothing. I've also tried with a different port and, yes, obviously I've tried completely disabling the running firewall and my router ports are correctly forwarded.
Temporarily solved using TCP, altough connection seems generally very slow.
A further test demonstrates that using the mobile carrier which as stated above worked only in TCP mode, also works using UDP protocol with a Linux laptop configured as OpenVPN client, connected throught the Android phone used as mobile wifi hotspot.
This seems really no-sense, I can only think of the involved mobile carrier blocking some packets for some unknown reason.