[
https://issues.apache.org/jira/browse/CLOUDSTACK-9117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863450#comment-15863450
]
ASF subversion and git services commented on CLOUDSTACK-9117:
-------------------------------------------------------------
Commit 8efdcfc1cdbda9d0a90c701e83a525c64d613e03 in cloudstack's branch
refs/heads/master from [~rajanik]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8efdcfc ]
Merge pull request #1183 from sanju1010/tcpports
Marvin test to verify that adding TCP ports 500,4500 and 1701 in vpn should not
failPlease refer to JIRA ticket for more details
https://issues.apache.org/jira/browse/CLOUDSTACK-9117
Following is the result info:
Test to add TCP Port Forwarding rule for specific ports(500,1701 and 4500) in
VPN ... === TestName: test_08_add_TCP_PF_Rule_In_VPN | Status : SUCCESS ===
ok
---
Ran 1 test in 166.799s
OK
* pr/1183:
Marvin test to verify that adding TCP ports 500,4500 and 1701 in vpn should
not fail Bug-Id: CS-43653 Reviewed-by: Self
Signed-off-by: Rajani Karuturi <[email protected]>
> Add marvin test to verify adding some TCP ports in vpn won't fail
> -----------------------------------------------------------------
>
> Key: CLOUDSTACK-9117
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9117
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Sanjeev N
> Assignee: Sanjeev N
>
> Add marvin test to verify adding some TCP ports in vpn won't fail
> Steps to follow:
> ============
> In an advanced zone
> 1.Create Remote access vpn on SourceNAT IP address
> 2.Create PortForwarding rules on the same ip address with TCP ports 500,4500
> and 1701.
> This is to make sure that VPN ports (UDP ports 500,4500 and 1701) won't give
> conflict when configuring PF with TCP ports.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
