[
https://issues.apache.org/jira/browse/CLOUDSTACK-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843862#comment-13843862
]
Sheng Yang commented on CLOUDSTACK-5387:
----------------------------------------
BTW, I am using Windows VPN client for remote access vpn.
> RemoteVPNonVPC : Unable to remotely access a VM in a VPC after enabling S2S
> VPN on the VPC VR
> ----------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5387
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5387
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.3.0
> Reporter: Chandan Purushothama
> Assignee: Sheng Yang
> Priority: Critical
> Fix For: 4.3.0
>
>
> ================
> Steps to Reproduce:
> ================
> 1. Deploy a VPC with a network tier in it. Deploy a VM in the network tier.
> Locate router/public ip for the VPC and enable Remote access vpn on it.
> 2. note preshared key
> 3. create a vpn user using addVpnUser API(using valid username and password)
> 4. from a standalone linux machine configure vpn client to point to public ip
> address from Step 1.
> 5. Add a ALLOW ACL Rule on ALL protocols to network tier's ACL List such that
> it blocks ssh access to the client's network.
> 6. ssh (using putty or any other terminal client) to the vm in network tier
> provisioned earlier.
> 7 Create a S2S VPN Connection on this VPC where the VPC VR is the passive end
> of the connection.
> 8. Establish the S2S VPN Connection from another VPC to this VPC.
> 9. Observe that the Remote Access to the VM no longer works.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
