te VPN section of configure.py, because
that section does not start ipsec if the public IP is not on the system yet...
That is my synopsis at least.
Thanks
Sean
-Original Message-
From: Sean Lair
Sent: Thursday, February 23, 2017 2:27 PM
To: dev@cloudstack.apache.org
Subject: VPN/IP
We just upgraded from 4.8.1.1 to 4.9.2.0. After upgrading we rebooted the
virtual routers, and noticed that our site-to-site VPNs and remote-access VPNs
would no longer connect. After troubleshooting, we noticed that Openswan
(ipsec.d) wasn't listening on the vRouter's IPs. Here is the abbrev
