Why did creating a secure list block all communication with PacketShaper?
Last Updated May 13, 2017
I created a security list on the Security setup page and now I can't communicate with PacketShaper. I wanted to limit access to PacketShaper to just a few inside IP addresses so I listed these addresses in the Inside list and left the Outside interface set to "secure."
The inside IP addresses may not be able to communicate with PacketShaper if the unit's default gateway is set to the router address, and PacketShaper needs to communicate through the router to communicate to the inside hosts. In this situation, you have to add the IP address of the default gateway to the Outside security list.
Imported Document ID: 000016164
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe