I'd recommend setting up a filter to solve this. If you've defined the IN and OUT system variables, setup a filter for IN to OUT. This should eliminate the problem. I'll add this to the NSDB as a potential benign trigger.
We are experiencing the same phenomenom concerning back door responses triggered by legitimate ftp traffic. All those back door responses are triggered on the ACKs coming from the client (in case of active ftp) and the server (in case of passive ftp). This is very time consuming to filter out these legitimate ftp clients/servers, as we don't want to disable these signatures. In case of passive ftp we are looking for a workaround using an ftp server that can be configured to use ports out of the known back door port ranges.
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...