I have just enabled DNS snooping on our ASA5585-X in preparation for enabling Botnet filter.
Since we have a fair amount of DNS over TCP and to ensure that I don't leave an easy way around the new protection, I looked at enabling snooping on TCP port 53 as well. Unexpectedly, this resulted in all TCP/53 traffic being dropped. Removing 'botnet_snoop_class_tcp' from 'policy-map botnet_snoop_policy' immediately restores traffic. Is this a known limitation, a bug or a misconfiguration?
class-map botnet_snoop_class_udp match port udp eq 53
class-map botnet_snoop_class_tcp match port tcp eq 53 ! policy-map botnet_snoop_policy class botnet_snoop_class_udp inspect dns dynamic-filter-snoop
class botnet_snoop_class_tcp inspect dns dynamic-filter-snoop
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...