You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/12/05 00:07:11 UTC
[jira] [Commented] (CLOUDSTACK-9079) ipsec service is not running
after restarting virtual router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042384#comment-15042384 ]
ASF GitHub Bot commented on CLOUDSTACK-9079:
--------------------------------------------
Github user terbolous commented on the pull request:
https://github.com/apache/cloudstack/pull/872#issuecomment-162106175
@jayapalu i believe that is broken in 4.6 already, atleast i filed an issue for it with the current openswan implementation at https://issues.apache.org/jira/browse/CLOUDSTACK-9079
> ipsec service is not running after restarting virtual router
> ------------------------------------------------------------
>
> Key: CLOUDSTACK-9079
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9079
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: SystemVM, Virtual Router
> Affects Versions: 4.6.0
> Environment: ACS 4.5.1 upgraded to 4.6.0
> Reporter: Erik Weber
> Priority: Critical
> Labels: systemvm, virtualrouter, vpn
>
> after upgrading to 4.6.0 the ipsec service does no longer automatically start and as an effect vpn does not work.
> manually starting the ipsec service, or doing any vpn related configuration (adding/deleting users) remedies the problem.
> Steps to reproduce:
> 1) Install ACS 4.6.0
> 2) Configure a VPC (I haven't tested with normal isolated networks)
> 3) Enable remote access VPN, configure a user
> 4) Confirm that VPN works
> 5) Restart the VR
> 6) Confirm that VPN does NOT work, either by trying to connect or by issuing 'service ipsec status' on the VR
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)