Are access lists handled differently in ms and mx?

Satoh3
Comes here often

Are access lists handled differently in ms and mx?

I have set up an access list for layer3 of mx using the same design concept as the access list for layer3 of ms, but I cannot confirm the expected behavior.
Is there a difference in the way the access list is processed in mx and in ms?

 

Actually Configration

 

List num1 Deny any 192.168.10.0/24 any 192.168.20.0/24 any

List num2 deny any 192.168.20.0/24 any 192.168.10.0/24 any

List num3 allow any any any any any

 

I would think the  192.168.10.0/24 to 192.168.20.0/24 packet would be denied, but for some reason it is allowed.

2 Replies 2
ww
Kind of a big deal
Kind of a big deal

You did not deny 192.168.10.0/24 to 192.168.10.0/24. And both client most propably do not traverse the mx when communicating in the same vlan

 

Also note that the acl in the switch is stateless and at the mx the normal fw rules statefull

PhilipDAth
Kind of a big deal
Kind of a big deal

The other thing to note is the MS access lists are always stateless.  MX group policy firewall rules are also stateless.

 

The "general" or standard MX firewall rules are stateful.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels