cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhinandan Prateek (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-238) vpn:fail to connect to vpnserver using non-sourceNAT IP
Date Fri, 29 Nov 2013 11:21:36 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Abhinandan Prateek updated CLOUDSTACK-238:
------------------------------------------

    Assignee:     (was: Abhinandan Prateek)

> vpn:fail to connect to vpnserver using non-sourceNAT IP
> -------------------------------------------------------
>
>                 Key: CLOUDSTACK-238
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-238
>             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
>             Fix For: 4.3.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: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.gi
> Note:same behavior observed in 3.0x  also



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message