Hot answers tagged vpn
Use a dynamic DNS service. Get a hostname for each site. configure VPN connections to use hostname for each connection instead of the sites IP address (Since you said its dynamic and subject to change) The dynamic DNS service should come with an application that monitors for an IP address change, and updates the hostname record automatically.
To be REALLY sure, that you have the same client version as on the Firebox, you can download the client directly from the firebox itself by opening https://Firebox_IP/sslvpn.html In your case I'd try to reinstall the client. It looks much like there went something wrong during the installation or something corrupted it later. Takes just 5 minutes, so it's ...
Everything seems normal. When you trace someinstance.mycompany.com the routing travels via VPN as specified in this rule: 10.0.0.0 255.255.0.0 On-link 172.16.0.163 11 while when you trace anything outside the VPN, it uses instead the normal gateway set by this rule: 0.0.0.0 0.0.0.0 192.168.0.254 192.168.0.113 ...
I had an identical problem and solved it by ensuring I had the certificate chain in the certificate file (end-entity cert, intermediate CA, root CA - in that order). TLS is fun. After restarting strongSwan, this stopped working, but started working again when I dropped the intermediate and root CA into /etc/ipsec.d/cacerts.
Only top voted, non community-wiki answers of a minimum length are eligible