New answers tagged

3

Ok apparently that's what the Splunk plugin does as well. See "Splunk Add-on for Cisco ASA" https://splunkbase.splunk.com/app/1620/ # direction is inbound [cisco_asa_message_id_302013_302015_inbound] REGEX = -30201[35]:\s*(\S+)\s+([Ii]nbound)\s+(\S+)(?:\s+connection)?\s+(\d+)\s+for\s+([^:\s]+)\s*:\s*(?:((?:[\d+\.]+|[a-fA-F0-9]*:[a-fA-F0-9]*:[a-fA-...


0

It's a bug in "Cisco Packet Tracer" that causing NAT to no work properly. See here: https://community.cisco.com/t5/routing/packet-tracer-asa-nat-problem/td-p/3936024 (Some workarounds are given in above link) A simple solution (not ideal) is to use Router for NATing (the so called traditional way).


1

It's not just NAT but also routing in your case. For NAT this should do: nat (inside,outside) after-auto source dynamic any interface For routing you will need to route "inside" networks to your inside router: route inside 192.168.10.0 255.255.255.0 172.16.0.1 route inside 192.168.20.0 255.255.255.0 172.16.0.1 route inside 192.168.30.0 255.255.255....


Top 50 recent answers are included