Wired Intelligent Edge

 View Only
  • 1.  Block Vlan communication - ACL

    Posted Jan 19, 2025 01:54 AM
    Edited by William_86 Jan 19, 2025 02:04 AM

    Good Day,  

    Aruba 2930f switch - ACL

    I need to be able to block certain vlans from communicating to a specific server IP on the local network and only allow one vlan to communicate with the server IP. 

    Vlan 100
    Server IP : 172.16.100/24

    Vlan 129
    172.16.129.0/24
    Vlan 129 - Must be able to communicate to server IP 

    All below vlans must be blocked from being able to communicate to the server IP.
    Vlan 133,134,135,136
    172.16.133.0/24
    172.16.134.0/24
    172.16.135.0/24
    172.16.135.0/24





  • 2.  RE: Block Vlan communication - ACL

    Posted Jan 21, 2025 11:45 AM

    Hi, a generally strict approach would be the one that will deny the specific traffic from leaving the VLANs with the particular destination you want to restrict the communication to (the specified Host/Network) but, at the same time, it will let other traffic to flow to other destinations. It's denying at source (near the source).

    On the VLAN hosting the specified server (say it is 172.16.100.1) which is providing a service (or more services) you want to connect to you could setup an (in)bound ACL with at least an ACE that will permit traffic on response only (or that will permit any traffic originated by or on response to) that legitimate VLAN excluding all the other VLANs.

    ACL on (in)bound VLAN 100:


    ACE SRC VLAN 100 (172.16.100.1 0.0.0.0) -> permit IP -> DST 172.16.129.0 0.0.0.255 (the Net with a /24 notation) <- case "A" if generic IP response/communication from SRC to DST is allowed (the Server will answer any IP requests or start communication with any IP protocol to the DST)
    ACE SRC VLAN 100 (172.16.100.1 0.0.0.0) -> permit TCP -> eq nnn DST 172.16.129.0 0.0.0.255 (the Net with a /24 notation) <- case "B" if specific TCP response for communication to DST when originated by DST calling the TCP/nnn port of the Server Host is allowed only (strict response). Any other response (for other protocols/ports) or communication starting by the Host will be denied because of the match "eq port" valid only for TCP protocol.
    ACE SRC VLAN 100 (172.16.100.1 0.0.0.0) -> deny IP -> DST 172.16.133.0 0.0.0.255
    ACE SRC VLAN 100 (172.16.100.1 0.0.0.0) -> deny IP -> DST 172.16.134.0 0.0.0.255
    ACE SRC VLAN 100 (172.16.100.1 0.0.0.0) -> deny IP -> DST 172.16.135.0 0.0.0.255
    ACE SRC VLAN 100 (172.16.100.1 0.0.0.0) -> deny IP -> DST 172.16.136.0 0.0.0.255
    ACE all other traffic not explicitly denied is permitted

    ACL on (in)bound VLAN 129:


    ACE SRC VLAN 129 (172.16.129.0 0.0.0.255) -> permit IP -> DST 172.16.100.1 0.0.0.0 (the Host with a /32 notation)
    ACE with denies, if any
    ACE all other traffic not explicitly denied is permitted


    ACL on (in)bound VLAN 133:


    ACE SRC VLAN 133 (172.16.133.0 0.0.0.255) -> deny IP -> DST 172.16.100.1 0.0.0.0 (or DST 172.16.100.0 0.0.0.255 in case the communication with the whole DST segment shall be denied)
    ACE all other traffic not explicitly denied is permitted

    ACL on (in)bound VLAN 134:


    ACE SRC VLAN 134 (172.16.134.0 0.0.0.255) -> deny IP -> DST 172.16.100.1 0.0.0.0 (or DST 172.16.100.0 0.0.0.255 in case the communication with the whole DST segment shall be denied)
    ACE all other traffic not explicitly denied is permitted

    ACL on (in)bound VLAN 135:


    ACE SRC VLAN 135 (172.16.135.0 0.0.0.255) -> deny IP -> DST 172.16.100.1 0.0.0.0 (or DST 172.16.100.0 0.0.0.255 in case the communication with the whole DST segment shall be denied)
    ACE all other traffic not explicitly denied is permitted

    ACL on (in)bound VLAN 136:


    ACE SRC VLAN 136 (172.16.136.0 0.0.0.255) -> deny IP -> DST 172.16.100.1 0.0.0.0 (or DST 172.16.100.0 0.0.0.255 in case the communication with the whole DST segment shall be denied)
    ACE all other traffic not explicitly denied is permitted

    You can translate them in ACEs, let we know if you require further help.




  • 3.  RE: Block Vlan communication - ACL

    Posted Jan 22, 2025 08:07 AM
    Edited by DP-7f7ca3 Jan 22, 2025 08:07 AM

    Hi, given that you're dealing with an ArubaOS-Switch based switch and supposing it is the routing switch (SVIs of involved VLANs are defined into the Switch and IP Routing is enabled), then below a very basic ACL to protect VLAN 100 just to start with (YMMV):

    ip access-list extended "VLAN-100" 
    1000 remark "Permit VLAN 100 ICMP echo-reply to any permitted destination" 
    1000 permit icmp 172.16.100.0 0.0.0.255 0.0.0.0 255.255.255.255 0 
    1010 remark "Permit VLAN 100 ICMP echo to any permitted destination" 
    1010 permit icmp 172.16.100.0 0.0.0.255 0.0.0.0 255.255.255.255 8 
    1020 remark "Permit VLAN 100 to dns1+ntp1" 
    1020 permit ip 172.16.100.0 0.0.0.255 <DNS1-NTP1-IP> 0.0.0.0 
    1030 remark "Permit VLAN 100 to dns2+ntp2" 
    1030 permit ip 172.16.100.0 0.0.0.255 <DNS2-NTP2-IP> 0.0.0.0

    1100 remark "Permit VLAN 100 Server to VLAN 129 segment" 
    1100 permit ip 172.16.100.1 0.0.0.0 172.16.129.0 0.0.0.255 <------------- permit any IP traffic to the VLAN 129 (communication started by Server with destination the VLAN 129 or server's answers to any IP request coming from the VLAN 129)

    OR a more strict ACE:

    1100 remark "Permit VLAN 100 Server to VLAN 129 segment (response to TCP/80 attempts)" 
    1100 permit tcp 172.16.100.1 eq 80 0.0.0.0 172.16.129.0 0.0.0.255 <------ permit only responses to TCP requests to Port 80 coming from the VLAN 129 (Server is denied to start any other type of communication to VLAN 129)

    1200 remark "Deny VLAN 100 to VLAN 133 segment (logged)"
    1200 deny ip 172.16.100.0 0.0.0.255 172.16.133.0 0.0.0.255 log 
    1201 remark "Deny VLAN 100 to VLAN 134 segment (logged)"
    1201 deny ip 172.16.100.0 0.0.0.255 172.16.134.0 0.0.0.255 log
    1202 remark "Deny VLAN 100 to VLAN 135 segment (logged)"
    1202 deny ip 172.16.100.0 0.0.0.255 172.16.135.0 0.0.0.255 log
    1203 remark "Deny VLAN 100 to VLAN 136 segment (logged)"
    1203 deny ip 172.16.100.0 0.0.0.255 172.16.136.0 0.0.0.255 log

    ...
    deny or permits, as required
    ...

    1500 remark "Permit any other traffic previously not explicitly denied to any other possible destination"
    1500 permit ip 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255 
    exit

    Apply the ACL "VLAN-100" at (in)bound direction into the VLAN 100 context and it will control traffic leaving the VLAN 100 (as it is seen by the VLAN 100 gateway on the routing Switch) to other destinations (the source is the 172.16.100.0 segment and any system hosted into that segment <-- ACE can be built by matching a SRC/DST Net and/or SRC/DST Host).

    Below a very basic ACL to protect VLAN 129:

    ip access-list extended "VLAN-129" 
    1000 remark "Permit VLAN 129 ICMP echo-reply to any permitted destination" 
    1000 permit icmp 172.16.129.0 0.0.0.255 0.0.0.0 255.255.255.255 0 
    1010 remark "Permit VLAN 129 ICMP echo to any permitted destination" 
    1010 permit icmp 172.16.129.0 0.0.0.255 0.0.0.0 255.255.255.255 8 
    1020 remark "Permit VLAN 129 to dns1+ntp1" 
    1020 permit ip 172.16.129.0 0.0.0.255 <DNS1-NTP1-IP> 0.0.0.0 
    1030 remark "Permit VLAN 129 to dns2+ntp2" 
    1030 permit ip 172.16.129.0 0.0.0.255 <DNS2-NTP2-IP> 0.0.0.0

    1100 remark "Permit VLAN 129 to VLAN 100 Server" 
    1100 permit ip 172.16.129.0 0.0.0.255 172.16.100.1 0.0.0.0 <------------ permit any IP traffic to the VLAN 100 Server host from the VLAN 129 segment

    OR a more strict ACE (matching what the Server exactly expects to receive from VLAN 129 segment):

    1100 remark "Permit VLAN 129 TCP/80 to VLAN 100 Server" 
    1100 permit tcp 172.16.129.0 0.0.0.255 172.16.100.1 0.0.0.0 eq 80 <----- permit only TCP/80 requests to VLAN 100 Server host from the VLAN 129 segment

    ...
    deny or permits, as required
    ...

    1500 remark "Permit any other traffic previously not explicitly denied to any other possible destination"
    1500 permit ip 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255 
    exit

    Apply the ACL "VLAN-129" at (in)bound direction into the VLAN 129 context and it will control traffic leaving the VLAN 129 (as it is seen by the VLAN 129 gateway on the routing Switch) to other destinations (the source is the 172.16.129.0 segment and any system hosted into that segment <-- ACE can be built by matching a SRC/DST Net and/or SRC/DST Host).

    Below a very basic ACL to protect VLAN 133 (create other ACLs by adapting/changing the VLAN Ids with 134, 135 and 136):

    ip access-list extended "VLAN-133" 
    1000 remark "Permit VLAN 133 ICMP echo-reply to any permitted destination" 
    1000 permit icmp 172.16.133.0 0.0.0.255 0.0.0.0 255.255.255.255 0 
    1010 remark "Permit VLAN 133 ICMP echo to any permitted destination" 
    1010 permit icmp 172.16.133.0 0.0.0.255 0.0.0.0 255.255.255.255 8 
    1020 remark "Permit VLAN 133 to dns1+ntp1" 
    1020 permit ip 172.16.133.0 0.0.0.255 <DNS1-NTP1-IP> 0.0.0.0 
    1030 remark "Permit VLAN 133 to dns2+ntp2" 
    1030 permit ip 172.16.133.0 0.0.0.255 <DNS2-NTP2-IP> 0.0.0.0

    1200 remark "Deny VLAN 133 to VLAN 100 Server (logged)"
    1200 deny ip 172.16.133.0 0.0.0.255 172.16.100.1 0.0.0.0 log

    ...
    deny or permits, as required
    ...

    1500 remark "Permit any other traffic previously not explicitly denied to any other possible destination"
    1500 permit ip 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255 
    exit

    Apply the ACL "VLAN-133" at (in)bound direction into the VLAN 133 context and it will control traffic leaving the VLAN 133 (as it is seen by the VLAN 133 gateway on the routing Switch) to other destinations (the source is the 172.16.133.0 segment and any system hosted into that segment <-- ACE can be built by matching a SRC/DST Net and/or SRC/DST Host).

    ACEs numbering starting with 1000 could be changed (and start with the usual 10).

    I supposed the Server IP is 172.16.100.1.

    Applying an ACL to a VLAN (example for VLAN 100 and its ACL VLAN-100) at (in)bound:

    vlan 100
       name "Net-172.16.100.0-24"
       ip address 172.16.100.254 255.255.255.0
       ip access-group "VLAN-100" in
       jumbo
    exit