Link to home
Start Free TrialLog in
Avatar of Aaron Street
Aaron StreetFlag for United Kingdom of Great Britain and Northern Ireland

asked on

CISCO ASA blocking own syslog messages from sending back across VPN

Hi,

I have a ASA device at a remote site with a management interface with IP address 192.168.1.1/24

and also on this interface are switches that also have ipaddress on the 192.168.1.x range.

It is connected back to the main site via a site to site VPN.

The rules on the firewall say that any traffic comming in to firewall on the 192.168.1.0/24 subnet to ip address 192.168.10.10 should be sent back across a site to site vpn.

Now for the switches that are using the ASA 192.168.1.1 as there default gateway this all works fine, however the traffic from the ASA its self fails and is blocked be the policy on the interface. (however the interface only has the default rule, traffic allowed to any less secure interface)

doing a trace, traffic from the switch never hit this interface rule they just get routed to the internet and then hit the VPN.

How is traffic from the firewall its self treated different and does hit this rule and is blocked. how do i insure it goes across the VPN and is not blocked.

Cheers
Avatar of arnold
arnold
Flag of United States of America image

See if you allow packets reversing/leaving returning over ....I.e leaving one interface to then come back on itself.
Same-security-traffic permit inter-interface or intra-interface will allow packets leaving the 192.168.1.1 to go through the vpn

https://learningnetwork.cisco.com/thread/20334
ASKER CERTIFIED SOLUTION
Avatar of Pete Long
Pete Long
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial