• General

  • Built-in IPSec tunnel networking quirks

Hello, a new member here.

I configured a GOS phone to use the native android IPSec client with a few different IVPN gateways (they use MSCHAPv2). It connects succesfully, I can browse the internet, banking apps work too, hovever, Signal app is showing as offline, then Play Store app installations go into "pending" state. When using the strongSwan implementation, I have none of these issues. I also tried to use Mullvad's external DNS servers without AD blocking. No difference. I was wondering if you have any ideas/recommendations on that, potentially experienced something similar on your own, where to start with troubleshooting? Maybe the default MTU needs adjusting, I could not find where to change that unfortunately.

    22 days later

    876fi Can you please post what settings you used with the native VPN client screen, e.g. IPSec identifier? Thank you 🌷

        DeletedUser115 The IPsec identifier is the same as the username IVPN provides (format i-XXXX-XXXX-XX), type "MSCHAPv2", server for instance "gb2.gw.ivpn.net", username "i-XXXX-XXXX-XXXX", password "ivpn". Apologies I have no place where to share a screenshot, on the other hand that is actually all you need in this post. Good luck!

            5 months later

            I faced with the some problem. With surfshark, ivpn and my own server. With certificate, with psk or username and pass. No matter.
            I was notice that problem appears in apps that can work with networking by the right way : check network type (mobile, WiFi, undefined) and change itself behavior.
            I think the problem is in "type of carrier" when you activate built-in client, in my opinion set to "something like undefined" instead of defined status of carrier.

            I found the source of the problem. This is really a NetworkType. When we using the built-in android vpn client (ipsec ikev2), type of network changes from WIFI to VPN (see attached logs). In the case of using a VPN through an application, the NetworkType does not change and remains the original one, for example WIFI. This is the problem for applications that uses the current type of network in their work. Even the built-in DataSaver does not work normally with this.
            10-20 04:19:53.713 10161 3288 3801 I BugleRcsEngine: Connected state: [2], networkType: [WIFI] [CONTEXT thread_id=26 ]
            10-20 04:19:53.744 10161 3288 3801 I BugleRcsEngine: Connected state: [2], networkType: [null] [CONTEXT thread_id=26 ]
            10-20 04:19:55.069 10161 3288 3801 I BugleRcsEngine: Connected state: [2], networkType: [VPN] [CONTEXT thread_id=26 ]
            10-20 04:19:55.071 10161 3288 3801 I BugleRcsEngine: Connected state: [2], networkType: [VPN] [CONTEXT thread_id=26 ]

            So, solution is uncheck "Always-on VPN" checkbox. After that, network type will be "original", without changing to " VPN".
            Not the best solution, but better that nothing.