Note that I am pinging from inside network on different vlan that 192.168.195.0 /27. As the inside network is fully routed (L3 core switches), the 192.168.195.0 network is considered "directly connected".
From my pc, I am trying to ping 192.168.195.5 (which is dmz host 10.30.5.5).
My ACL is as follows:
access-list inside_in extended permit ip any any access-list inside_in extended permit icmp any any
Again, from inside network I can ping ASA inside interace.
The DMZ server ip address (10.x.x.x) is non-routable on the inside network hence the reason for static to inside ip address.
Packet tracer results show the following:
Phases 1-8 show ALLOW
Phase: 9 Type: NAT Subtype: rpf-check Result: DROP Config: static (DMZ,inside) 192.168.195.5 10.30.5.5 netmask 255.255.255.255 nat-control match ip DMZ host 10.30.5.5 inside any static translation to 192.168.195.5 translate_hits = 0, untranslate_hits = 0 Additional Information: Forward Flow based lookup yields rule: out id=0xcae4e608, priority=5, domain=nat-reverse, deny=false hits=0, user_data=0xcb0ab4f0, cs_id=0x0, flags=0x0, protocol=0 src ip=0.0.0.0, mask=0.0.0.0, port=0 dst ip=10.30.5.5, mask=255.255.255.255, port=0, dscp=0x0
Result: input-interface: inside input-status: up input-line-status: up output-interface: DMZ output-status: up output-line-status: up Action: drop Drop-reason: (acl-drop) Flow is denied by configured rule
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...