Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 23 Feb 2017 23:41:44 +0000 (UTC)
From: "Sean Lair (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13045831.1487893279000.49261.1487893304021@Atlassian.JIRA>
In-Reply-To: <JIRA.13045831.1487893279000@Atlassian.JIRA>
References: <JIRA.13045831.1487893279000@Atlassian.JIRA> <JIRA.13045831.1487893279099@jira-lw-us.apache.org>
Subject: [jira] [Created] (CLOUDSTACK-9801) IPSec VPN does not work after
 vRouter reboot or recreate
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 23 Feb 2017 23:41:52 -0000

Sean Lair created CLOUDSTACK-9801:
-------------------------------------

             Summary: IPSec VPN does not work after vRouter reboot or recreate
                 Key: CLOUDSTACK-9801
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9801
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Virtual Router
    Affects Versions: 4.9.0.1, 4.9.0, 4.9.2.0
         Environment: Tested in XenServer as hypervisor.  With RemoteAccess VPN enabled.  Both Remote Access VPN and Site to Site VPN functionality won't work.
            Reporter: Sean Lair
            Priority: Critical


After a vRouter is recreated (which happens when a reboot via CloudStack UI for example) and Remote Access VPN enabled, VPN won't work anymore.  Here is the abbreviated output of "ipsec auto -status" while we were having the issue:

root@r-10-VM:~# ipsec auto --status
000 using kernel interface: netkey
000 interface lo/lo 127.0.0.1
000 interface lo/lo 127.0.0.1
000 interface eth0/eth0 169.254.1.45
000 interface eth0/eth0 169.254.1.45
000 %myid = (none)

Notice that only eth0 is shown, not the public interface eth1.  Because of that ipsec is broken.

However, if we manually stopped and started ipsec, then issued a "ipsec auto -status", the abbreviated output would be:

root@r-10-VM:~# ipsec auto --status
000 using kernel interface: netkey
000 interface lo/lo 127.0.0.1
000 interface lo/lo 127.0.0.1
000 interface eth0/eth0 169.254.1.45
000 interface eth0/eth0 169.254.1.45
000 interface eth1/eth1 xxx.xxx.xxx.172
000 interface eth1/eth1 xxx.xxx.xxx.172
000 interface eth2/eth2 192.168.1.1
000 interface eth2/eth2 192.168.1.1
000 %myid = (none)

eth1 interface IP is masked, but now ipsec sees all the interfaces and VPN works.  

Looks like this bug was introduced by Pull Request #1423

https://github.com/apache/cloudstack/pull/1423

It added code to start ipsec (cloudstack/systemvm/patches/debian/config/opt/cloud/bin/configure.py)

if vpnconfig['create']:
                logging.debug("Enabling  remote access vpn  on "+ public_ip)
                CsHelper.start_if_stopped("ipsec")
                self.configure_l2tpIpsec(public_ip, self.dbag[public_ip])


The issue is that if a reboot is issued from the CloudStack UI (as opposed to manually by logging into the vRouter), the NICS (except eth0) are not added to the VM until the cloud service is running.

Since ipsec was started before the nics were added to the VM and before the public IP address is added to the nic, ipsec is not listening on the public IP address and all VPNs are broken.

This is not a problem with the Site2Site VPN section of configure.py, because that section does not start ipsec if the public IP is not on the system yet...  


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)