Wow that was easy! It worked straight away Thank you, i really appreciate it!

Thanks for all your help your comment about the windows firewall got me to look at it a different way. Turns out during one of my previous attempts to get internet to my VPN clients (a different issue not this one) I messed with some other firewall settings and pushed all of the VPN traffic out the WAN interface which worked fine for getting my clients internet access but caused issues when I tried to access the LAN. I removed that and now with the push route command my clients are able to access the Internet and my LAN

@Rico Those are respectable numbers. I'm curious to know how that would scale with 2 simultaneous connections? I'm thinking it's not entirely CPU bound, so maybe 2 by 60 or 70 Mbps?

easy-rsa together with easy-tls might be helpful: https://github.com/OpenVPN/easy-rsa https://github.com/TinCanTech/easy-tls

@viragomann: another very valuable hint - thank you! I adapted the configuration accordingly: [image: 1606901223027-ipsec-3.png] I also limited the ip-range of the DHCP-server to make sure this address cannot be assigned to anybody else.

Glad you have it working now. -Rico

@jimp yes i can get dyndns working with the real IP assigned by the ISP so something like this purple ... 62.116.x.y ... dyndns1.dyndns.org yellow ... 91.113.x.y ... dyndns2.dyndns.org green ... 194.96.x.y ... dyndns3.dyndns.org the budget in COVID times is slim to n00thing thx for the hint with the static IP gonna look into it.

Just in case anybody has this issue as well - I finally was able to resolve it: the issue seems to be that the routing table on the Android phone (version 9 - Pie) seems to have corrupted in some way when the OpenVPN-connection routed is closed and re-opened. The solution is either rebooting the phone or (much faster) turning on and off flight-mode - this seems to reset the routing table and OpenVPN-connections can be initiated again.

@viragomann You are a bloody genius. Thanks SO much.

Just an update. I solved my issue. I switched vpn providers and its working. That tells me there was some nuance in the vpn config of strongvpn that didn't work.

That is interesting and something I hadnt thought about, Assigning user groups per subnet, As they all have already been applied and distributed that will take some work, But it is a solution Thank you

I get that now, I am going to try the routing from the IPSec to the OpenVPN subnet

@mcfly9 said in OpenVPN quits on WAN IP change: Honestly, it does not. I don't know, how knows that the "watchdog" is a forced solution, it means something that you fear(ed) will not work properly yes it has already been described by "@Gertjan " the end will be, if you are a serious provider, buy fixed IP, hihihihihhi BTW: there are pfSense instances in our park, that only need to be restarted, ... on updates... (OS, FW, or etc.) and / or if OpenVPN does not pick up the IP(s) it's a joke...(: they work for months (pfSense + Open VPN servers / clients) without any problems, in this regrettable situation when our employees work from home... the OpenVPN + pfSense works with more than 450 -550 users (in 4 countries, on 28 radio stations)

@Gertjan Everyone knows that Google collects data wherever it can ... I would like to know if it makes a difference while connected to a VPN...

@Bob-Dig I'd say this is the gateway monitoring status (the packet loss) The gateway prob doesnt answer to pings Tune here , or disable System --> Routing --> Gateways [image: 1606556255789-4a4e1053-1070-4054-879c-528cd40ec1e9-image.png]