cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sheng Yang (JIRA)" <>
Subject [jira] [Resolved] (CLOUDSTACK-238) vpn:fail to connect to vpnserver using non-sourceNAT IP
Date Tue, 23 Sep 2014 18:32:34 GMT


Sheng Yang resolved CLOUDSTACK-238.
    Resolution: Invalid

We don't support enable VPN on non-source NAT IP. We only support enable it on source NAT

UI part is already fixed in: 

commit 87effa40ea267d2e334aadb0a201fc031d9c09a8
Author: Jessica Wang <>
Date:   Fri Jul 11 13:46:29 2014 -0700

    UI > IP Address > hide EnableVPN option on acquired IP.

> vpn:fail to connect to vpnserver using non-sourceNAT IP
> -------------------------------------------------------
>                 Key: CLOUDSTACK-238
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: pre-4.0.0
>            Reporter: sadhu suresh
>            Assignee: sadhu suresh
>             Fix For: 4.4.0
>         Attachments: management-server.rar, screenshot_vpn1.jpg
> fail to connect to vpn server when we enable vpn on non-sourcenat ip where as able to
connect to vpn server when we enable vpn on sourcenat ip.
> Steps:
> 1.Installed new build  and configure advance zone with hypervisor xen
> 2.deploy a VM
> 3.acquire new ip
> 4.enable the vpn on new accquired IP
> 5.try to open vpn connection with above details
> Actual results:
> It fail to connect VPN and it  throws error "809" i.e netwrk connection between  your
computer and the vpn server could not established becoase remote server is not responding.
> But when we enable vpn on sourcenat IP then able to connect  to VPNserver successfully.
> Expected results:
> It shoud connect the vpnserver when we use non-sourcenat IP.
> [root@rhel63 ~]# cloud-sccs
> Git Revision: 8ed8b8b8b66084e0e5409ae5fcc9dc1caca53519
> Git URL:
> Note:same behavior observed in 3.0x  also

This message was sent by Atlassian JIRA

View raw message