Hi Wei ZHOU, Thanks for the update. Let me log it as an issue in GitHub.
Regards, Loges On Sat, Apr 29, 2023 at 2:40 AM Wei ZHOU <ustcweiz...@gmail.com> wrote: > Hi, > > It seems not supported for now. Each ACL rule can have only 1 cidr, which > is the source cidr for Ingress rules, and destination cidr for Egress > rules. > > Can you log an issue or a feature request on github ? > > -Wei > > On Fri, 28 Apr 2023 at 09:24, Lokeswaran T <lokeswa...@gmail.com> wrote: > > > Hi All, > > > > 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 > > 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. > > > > Can anyone help me how to resolve this? > > > > Regards, > > Loges > > > -- Logeswaran.T
