ACL rule blocking traffic from "A" to "B" is also preventing communication from "B" into "A"?
ACL rule blocking traffic from "A" to "B" is also preventing communication from "B" into "A"?
I have two "Interface" networks set up:
- "Core" for the network devices and home computers
- "Outer Core" for my wireless printer
Everything is successfully connected with IPs that show that they are in the correct subnets. I can ping the printer from my desktop.
Now I'm trying to create an ACL so that the printer cannot touch the Core devices.
The ACL has the following properties:
- Policy: Deny
- Protocols: All
- Rule:
- Source: Network "Outer Core"
- Destination: Network "Core"
- ACL Binding (can't change these):
- Binding type: Ports
- Ports: All ports
- Advanced settings:
- Time Range: not enabled
- Ethertype: not enabled
That's it. When I create that rule, I can no longer even ping the printer that's in "Outer Core" from my desktop that's in "Core". Disable the rule, wait a few seconds and I can ping again.
Not sure what I'm doing wrong. Thoughts?
1 Accepted Solution