assistanz247 opened a new issue, #7483:
URL: https://github.com/apache/cloudstack/issues/7483
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
* Improvement Request
##### COMPONENT NAME
VPC
##### CLOUDSTACK VERSION
Cloudstack 4.18.0.0
##### CONFIGURATION
VPC Network
##### OS / ENVIRONMENT
N/A
##### SUMMARY
I have allowed only port 3389 in the VPC ACL but able to access using other
port which is not in allowed list.
##### STEPS TO REPRODUCE
Here is my scenario.
I have created a VPC then create a new ACL list name my-ACL and added the
below rules.
*For Egress:*
ALL Egress allow
*For Ingress:*
CIDR: [0.0.0.0/0](http://0.0.0.0/0)
Protocol: TCP
From Port: 3389
To Port: 3389
Then I created two Windows VMs under this new network. Then I acquire a
Public IP address and add the below port forwarding.
For VM1:
Private port: 3389
Public Port: 3389
For VM2:
Private Port: 3389
Public Port: 2812
In my scenario, I need to access only VM1 through RDP using the public IP
address using the 3389 port. But, I'm able to access the VM2 with 2812
also.
But in my network ACL, I have allowed only port 3389.
##### EXPECTED RESULTS
Should access only the VM1 from 3389 port not VM2 from 2812 port.
##### ACTUAL RESULTS
I was able to access VM2 using 2812 port.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
