You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Abhinandan Prateek (JIRA)" <ji...@apache.org> on 2013/07/08 07:53:48 UTC
[jira] [Assigned] (CLOUDSTACK-2779) [VPC N/W ACL UI]:Unable to
define the port range if we specify the protocol number while defining the
network ACL rules.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhinandan Prateek reassigned CLOUDSTACK-2779:
----------------------------------------------
Assignee: Pranav Saxena
Can you verify this ?
> [VPC N/W ACL UI]:Unable to define the port range if we specify the protocol number while defining the network ACL rules.
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2779
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2779
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: UI
> Affects Versions: 4.2.0
> Reporter: manasaveloori
> Assignee: Pranav Saxena
> Priority: Blocker
> Fix For: 4.2.0
>
>
> Steps:
> 1. Have a CS with advanced zone.
> 2. Create a VPC and a tier.
> 3. Create a network ACL list .
> 4. Try to add the network ACL by specifying the protocol number.
> Observation:
> If we select protocol number from “protocol” drop down---there is no option to specify the port range.
> With API able to specify the port range using protocol number
> API fired:
> http://10.147.38.154:8096/client/api?command=createNetworkACL&cidrlist=10.10.0.0%2F24&action=Allow&protocol=6&startport=22&endport=22&traffictype=Egress&aclid=b6508349-26b8-4fe8-9c9d-612a1a28cd2f&_=1369977283724.
--
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