Aruba & ProVision-based
cancel
Showing results for 
Search instead for 
Did you mean: 

ACL for VLANS

 
auddog007
Occasional Visitor

ACL for VLANS

Have a HPE 1920 (JG925A) that I'm attempting to isolate vlan traffic between.  I currently have the vlans created and talking between each other.  Now I would like to isolate the traffic with one vlan being open to everyone (printer and shared resources) while keeping the other two vlans from talking with each other.

vlan1 (default - (192.168.10.0/24)) - printers and shared resources
vlan2  (192.168.11.0/24) - office employees
vlan3 (192.168.12.0/24) - consultants

My question is about creating the ACL.  I have created an advanced ACL with a deny action and have set the source ip 192.168.12.0 wildcard 0.0.0.0 and destination ip 192.168.11.0 wildcard 0.0.0.0.  Is that the correct setup needed before I apply the classifier, behavior and assign policy.  I'm also assuming that I would need to create another ACL going the other direction also.

1 REPLY 1
3Naga
HPE Pro

Re: ACL for VLANS

Hi ,

Thank you for writing 

Yes you are right in the way of creating the ACL and there should an ACL created for allowing the other direction too.

Also share us with the basic vlan configuration and the ACL for us to have a look post applying it and see if the results are as expected

Thanks

I work for HPE
Accept or Kudo