You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2013/06/03 23:18:19 UTC
[jira] [Commented] (CLOUDSTACK-2731) changing global/account level
parameter "remote.access.vpn.client.iprange" is not allcoacting new ip
address to vpn client
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673584#comment-13673584 ]
Alena Prokharchyk commented on CLOUDSTACK-2731:
-----------------------------------------------
Changing the global config variable will affect only new VPNs. The old ones will continue to run with the old settings. This is by design, so closing the bug.
> changing global/account level parameter "remote.access.vpn.client.iprange" is not allcoacting new ip address to vpn client
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2731
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2731
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Reporter: prashant kumar mishra
> Fix For: 4.2.0
>
> Attachments: Logs.rar
>
>
> Steps to reproduce:
> -----------------------------
> 1-Set global parameter "remote.access.vpn.client.iprange" to some range;restart MS
> 2-create a vpn
> 3-connect to vpn
> 4-check ip address of vpn client;it will get ip address from range define in step1
> 5-chenge global parameter "remote.access.vpn.client.iprange" to some range other that in step 1;restart MS
> 6-connect to vpn
> 7-check ip address of vpn client
> Actual
> ----------
> ----------
> client is still holding previous ip adrress
> Expected
> --------------
> Client should get ip address from new ip range
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira