[
https://issues.apache.org/jira/browse/CLOUDSTACK-10010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16275624#comment-16275624
]
ASF subversion and git services commented on CLOUDSTACK-10010:
--------------------------------------------------------------
Commit 6524593268f38af26afbbd68635950fe09bca334 in cloudstack's branch
refs/heads/debian9-systemvmtemplate from [[email protected]]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=6524593 ]
CLOUDSTACK-10010: Port marvin test from #2190 by @swill
This ports the S2S config test by @swill from #2190 with additional
changes to make robust and environment agnostic.
Signed-off-by: Rohit Yadav <[email protected]>
> Some S2S VPN configurations fail to establish a connection
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-10010
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10010
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Virtual Router
> Affects Versions: 4.10.0.0
> Reporter: Will Stevens
>
> I am not sure if a regression was introduced with this PR #2062, but we have
> found issues with this configuration now that we have it in production.
> The core of this change is to change the S2S VPN config from {{auto=start}}
> to {{auto=route}}. Read more about this setting here:
> https://wiki.strongswan.org/projects/strongswan/wiki/ConnSection
> We found there to be issues when using {{auto=start}} for both sides of the
> connection as there was problem negotiating the connection. Instead the
> {{auto=route}} config will only establish a connection once there is an
> attempt to send traffic over the connection. In order to attempt to open the
> connection as soon as the VPN connection is configured, a ping to the other
> side of the connection has been added to establish the connection.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
