topic Hi, in Network Security

Blocked or blacklisted by the firewall preprocessor

ssambourg — Tue, 12 Mar 2019 09:09:30 GMT

Hello,

when I issued a packet-tracer from my antispam to Internet on SMTP dest port, I see this results :

Phase: 12
Type: SNORT
Subtype:
Result: DROP
Config:
Additional Information:
Snort Trace:
Packet: TCP, SYN, seq 811220630
AppID: service unknown (0), application unknown (0)
Firewall: starting rule matching, zone 1 -> 1, geo 0 -> 0, vlan 0, sgt 65535, user 9999997, icmpType 0, icmpCode 0
Firewall: block rule, id 268434432, drop
Snort: processed decoder alerts or actions queue, drop
NAP id 2, IPS id 0, Verdict BLACKLIST, Blocked by Firewall
Snort Verdict: (black-list) black list this flow

Result:
input-interface: INSIDE
input-status: up
input-line-status: up
output-interface: OUT
output-status: up
output-line-status: up
Action: drop
Drop-reason: (firewall) Blocked or blacklisted by the firewall preprocessor

I can't find anyware to allow or white list this stream

Hi,

Arild Amundsen — Mon, 26 Jun 2017 07:21:39 GMT

Hi,

I am running into the same problem. Did you find the solution for this?

Re: Blocked or blacklisted by the firewall preprocessor

Ben Chen — Thu, 15 Mar 2018 15:01:52 GMT

Hi,

I'm also encounter same issue , do you resolve this problem ?

And another question is how to tune Snort Verdict blacklisted time?

Regards,

Ben

Re: Blocked or blacklisted by the firewall preprocessor

Marvin Rhoads — Thu, 15 Mar 2018 16:18:38 GMT

In such a case the destination address is in the Firepower blacklist - either the one downloaded automatically as part of the Cisco Security Intelligence (SI) feed or a local custom blacklist.

Re: Blocked or blacklisted by the firewall preprocessor

CiscoAzs — Sat, 21 Apr 2018 23:39:41 GMT

i have the same issue when failover to primary node. i am using FTD running version 6.2.3 -83. secondary node work normally.

Re: Blocked or blacklisted by the firewall preprocessor

Marvin Rhoads — Sun, 22 Apr 2018 12:06:32 GMT

Are the appliances managed locally (ASDM) or remotely(FMC). In either case you must make sure that the policies are applied identically to both nodes.

Re: Blocked or blacklisted by the firewall preprocessor

Aydin Ehtibarov — Mon, 23 Apr 2018 05:26:33 GMT

hello,

i was the same issue but cisco tag help me find the reason

your output contain the blocking line id

Firewall: block rule, id 268434432, drop

in your situation it is 268434432

you must go to firepower applianca cli and connect to FTD

if promt is "ASB-HO-FTD-A# " connect to FTD

ASB-HO-FTD-A# connect ftd

then go to expert mode by typeng next commang

> expert

do the next linux command ( 1ac0cb9a-0cd2-11e8-8c50-8f0e1cebbe73 part is different for each appliance )

cat /var/sf/detection_engines/1ac0cb9a-0cd2-11e8-8c50-8f0e1cebbe73/ngfw.rules

if you have problem with doing privious step then

- type "cat /var/sf/detection_engines/"

- press tab button

- append "ngfw.rules"

after this you will see all ACL and ID of each ACE

find the one from packet tracer output " 268434432 "

probably you must have permit statement for traffic before this point.

Re: Blocked or blacklisted by the firewall preprocessor

G_Singh — Mon, 08 Jul 2019 02:57:24 GMT

Hi Marvin, Im having the same issue between 2 FTDs which are managed by FMC. Both FTDs has identical config and not blacklisted. Below results only showing when running packet-tracer from FTD1 to FTD2, but works fine when run packet-tracer between FTD2 to FTD1.
"Drop-reason: (firewall) Blocked or blacklisted by the firewall preprocessor."

Any suggestions....

Re: Blocked or blacklisted by the firewall preprocessor

Marvin Rhoads — Mon, 08 Jul 2019 09:04:06 GMT

@G_Singh

Are FTD 1 and FTD 2 in an HA pair?

We need some more details to ascertain possible causes of your problem.

Re: Blocked or blacklisted by the firewall preprocessor

G_Singh — Mon, 08 Jul 2019 22:13:02 GMT

Hi Marvin, no FTDs arent clustered or in HA, but will be in future....also as Aydin Ehtibarov mentioned, I ran same expert Linux commands but unable to find the Tracer output on non-working FTD as it should, but able to see on working FTD.

(FW101) non-working
> show access-list | include DMVPN_Traffic_Hub_to_Hub
access-list CSM_FW_ACL_ line 140 remark rule-id 268439606: L7 RULE: DMVPN_Traffic_Hub_to_Hub

show access-list | include 268439606
access-list CSM_FW_ACL_ line 139 remark rule-id 268439606: ACCESS POLICY: FW101 - Mandatory
access-list CSM_FW_ACL_ line 140 remark rule-id 268439606: L7 RULE: DMVPN_Traffic_Hub_to_Hub
access-list CSM_FW_ACL_ line 141 advanced permit tcp ifc Interlink object-group FMC_INLINE_src_rule_268439606 ifc Interlink object-group FMC_INLINE_dst_rule_268439606 object-group ESP_50 rule-id 268439606 (hitcnt=0) 0x65342c53
access-list CSM_FW_ACL_ line 141 advanced permit tcp ifc Interlink x.x.x.0 255.255.255.252 ifc Interlink x.x.x.0 255.255.255.252 eq 50 rule-id 268439606 (hitcnt=0) 0x7a797f98
access-list CSM_FW_ACL_ line 141 advanced permit tcp ifc Interlink x.x.x.0 255.255.255.252 ifc Interlink x.x.x.4 255.255.255.252 eq 50 rule-id 268439606 (hitcnt=0) 0x0a8c2851
access-list CSM_FW_ACL_ line 141 advanced permit tcp ifc Interlink x.x.x.4 255.255.255.252 ifc Interlink x.x.x.0 255.255.255.252 eq 50 rule-id 268439606 (hitcnt=0) 0x5effc1c3
access-list CSM_FW_ACL_ line 141 advanced permit tcp ifc Interlink x.x.x.4 255.255.255.252 ifc Interlink x.x.x.4 255.255.255.252 eq 50 rule-id 268439606 (hitcnt=0) 0x146865f8
access-list CSM_FW_ACL_ line 142 advanced permit udp ifc Interlink object-group FMC_INLINE_src_rule_268439606 ifc Interlink object-group FMC_INLINE_dst_rule_268439606 object-group UDP_4500 rule-id 268439606 (hitcnt=0) 0x8d388f80
access-list CSM_FW_ACL_ line 142 advanced permit udp ifc Interlink x.x.x.0 255.255.255.252 ifc Interlink x.x.x.0 255.255.255.252 eq 4500 rule-id 268439606 (hitcnt=0) 0x79dc3f1d
access-list CSM_FW_ACL_ line 142 advanced permit udp ifc Interlink x.x.x.0 255.255.255.252 ifc Interlink x.x.x.4 255.255.255.252 eq 4500 rule-id 268439606 (hitcnt=0) 0x6ca0619f
access-list CSM_FW_ACL_ line 142 advanced permit udp ifc Interlink x.x.x.4 255.255.255.252 ifc Interlink x.x.x.0 255.255.255.252 eq 4500 rule-id 268439606 (hitcnt=0) 0xaef4147c
access-list CSM_FW_ACL_ line 142 advanced permit udp ifc Interlink x.x.x.4 255.255.255.252 ifc Interlink x.x.x.4 255.255.255.252 eq 4500 rule-id 268439606 (hitcnt=0) 0x0dfa067c
access-list CSM_FW_ACL_ line 143 advanced permit udp ifc Interlink object-group FMC_INLINE_src_rule_268439606 ifc Interlink object-group FMC_INLINE_dst_rule_268439606 object-group UDP_500 rule-id 268439606 (hitcnt=6) 0xdd1f3fe4
access-list CSM_FW_ACL_ line 143 advanced permit udp ifc Interlink x.x.x.0 255.255.255.252 ifc Interlink x.x.x.0 255.255.255.252 eq isakmp rule-id 268439606 (hitcnt=0) 0xfd58fc5b
access-list CSM_FW_ACL_ line 143 advanced permit udp ifc Interlink x.x.x.0 255.255.255.252 ifc Interlink x.x.x.4 255.255.255.252 eq isakmp rule-id 268439606 (hitcnt=0) 0x810563db
access-list CSM_FW_ACL_ line 143 advanced permit udp ifc Interlink x.x.x.4 255.255.255.252 ifc Interlink x.x.x.0 255.255.255.252 eq isakmp rule-id 268439606 (hitcnt=6) 0xf3c91e26
access-list CSM_FW_ACL_ line 143 advanced permit udp ifc Interlink x.x.x.4 255.255.255.252 ifc Interlink x.x.x.4 255.255.255.252 eq isakmp rule-id 268439606 (hitcnt=0) 0xe1fc9781
access-list CSM_FW_ACL_ line 144 advanced permit udp ifc Interlink object-group FMC_INLINE_src_rule_268439606 ifc Interlink object-group FMC_INLINE_dst_rule_268439606 object-group IPSec_over_UDP rule-id 268439606 (hitcnt=0) 0xe1b61e51
access-list CSM_FW_ACL_ line 144 advanced permit udp ifc Interlink x.x.x.0 255.255.255.252 ifc Interlink x.x.x.0 255.255.255.252 eq 10000 rule-id 268439606 (hitcnt=0) 0xfa9d9d5c
access-list CSM_FW_ACL_ line 144 advanced permit udp ifc Interlink x.x.x.0 255.255.255.252 ifc Interlink x.x.x.4 255.255.255.252 eq 10000 rule-id 268439606 (hitcnt=0) 0x4d1f57ad
access-list CSM_FW_ACL_ line 144 advanced permit udp ifc Interlink x.x.x.4 255.255.255.252 ifc Interlink x.x.x.0 255.255.255.252 eq 10000 rule-id 268439606 (hitcnt=0) 0x2247f007
access-list CSM_FW_ACL_ line 144 advanced permit udp ifc Interlink x.x.x.4 255.255.255.252 ifc Interlink x.x.x.4 255.255.255.252 eq 10000 rule-id 268439606 (hitcnt=0) 0xc20f6752

Below commands are from Expert mode in FTD, showing no out put in regards to rule-id 268439606 as it shows on working FTD at the bootm of the page
admin@FW101: cat /var/sf/detection_engines/17b6430e-5f23-11e9-b014-8e6fe6d5323f/ngfw.rules
(should appear some rule-id 268439606)

(FW201) Working
> show access-list | include DMVPN_Traffic_Hub_to_Hub
access-list CSM_FW_ACL_ line 273 remark rule-id 268439607: L7 RULE: DMVPN_Traffic_Hub_to_Hub

> show access-list | include 268439607
access-list CSM_FW_ACL_ line 272 remark rule-id 268439607: ACCESS POLICY: FW201 - Mandatory
access-list CSM_FW_ACL_ line 273 remark rule-id 268439607: L7 RULE: DMVPN_Traffic_Hub_to_Hub
access-list CSM_FW_ACL_ line 274 advanced permit tcp ifc Interlink object-group FMC_INLINE_src_rule_268439607 ifc Interlink object-group FMC_INLINE_dst_rule_268439607 object-group ESP_50 rule-id 268439607 (hitcnt=0) 0x945e36cb
access-list CSM_FW_ACL_ line 274 advanced permit tcp ifc Interlink x.x.x.0 255.255.255.252 ifc Interlink x.x.x.0 255.255.255.252 eq 50 rule-id 268439607 (hitcnt=0) 0x7a797f98
access-list CSM_FW_ACL_ line 274 advanced permit tcp ifc Interlink x.x.x.0 255.255.255.252 ifc Interlink x.x.x.4 255.255.255.252 eq 50 rule-id 268439607 (hitcnt=0) 0x0a8c2851
access-list CSM_FW_ACL_ line 274 advanced permit tcp ifc Interlink x.x.x.4 255.255.255.252 ifc Interlink x.x.x.0 255.255.255.252 eq 50 rule-id 268439607 (hitcnt=0) 0x5effc1c3
access-list CSM_FW_ACL_ line 274 advanced permit tcp ifc Interlink x.x.x.4 255.255.255.252 ifc Interlink x.x.x.4 255.255.255.252 eq 50 rule-id 268439607 (hitcnt=0) 0x146865f8
access-list CSM_FW_ACL_ line 275 advanced permit udp ifc Interlink object-group FMC_INLINE_src_rule_268439607 ifc Interlink object-group FMC_INLINE_dst_rule_268439607 object-group UDP_4500 rule-id 268439607 (hitcnt=0) 0xccac03cf
access-list CSM_FW_ACL_ line 275 advanced permit udp ifc Interlink x.x.x.0 255.255.255.252 ifc Interlink x.x.x.0 255.255.255.252 eq 4500 rule-id 268439607 (hitcnt=0) 0x79dc3f1d
access-list CSM_FW_ACL_ line 275 advanced permit udp ifc Interlink x.x.x.0 255.255.255.252 ifc Interlink x.x.x.4 255.255.255.252 eq 4500 rule-id 268439607 (hitcnt=0) 0x6ca0619f
access-list CSM_FW_ACL_ line 275 advanced permit udp ifc Interlink x.x.x.4 255.255.255.252 ifc Interlink x.x.x.0 255.255.255.252 eq 4500 rule-id 268439607 (hitcnt=0) 0xaef4147c
access-list CSM_FW_ACL_ line 275 advanced permit udp ifc Interlink x.x.x.4 255.255.255.252 ifc Interlink x.x.x.4 255.255.255.252 eq 4500 rule-id 268439607 (hitcnt=0) 0x0dfa067c
access-list CSM_FW_ACL_ line 276 advanced permit udp ifc Interlink object-group FMC_INLINE_src_rule_268439607 ifc Interlink object-group FMC_INLINE_dst_rule_268439607 object-group UDP_500 rule-id 268439607 (hitcnt=1) 0x202df959
access-list CSM_FW_ACL_ line 276 advanced permit udp ifc Interlink x.x.x.0 255.255.255.252 ifc Interlink x.x.x.0 255.255.255.252 eq isakmp rule-id 268439607 (hitcnt=0) 0xfd58fc5b
access-list CSM_FW_ACL_ line 276 advanced permit udp ifc Interlink x.x.x.0 255.255.255.252 ifc Interlink x.x.x.4 255.255.255.252 eq isakmp rule-id 268439607 (hitcnt=1) 0x810563db
access-list CSM_FW_ACL_ line 276 advanced permit udp ifc Interlink x.x.x.4 255.255.255.252 ifc Interlink x.x.x.0 255.255.255.252 eq isakmp rule-id 268439607 (hitcnt=0) 0xf3c91e26
access-list CSM_FW_ACL_ line 276 advanced permit udp ifc Interlink x.x.x.4 255.255.255.252 ifc Interlink x.x.x.4 255.255.255.252 eq isakmp rule-id 268439607 (hitcnt=0) 0xe1fc9781
access-list CSM_FW_ACL_ line 277 advanced permit udp ifc Interlink object-group FMC_INLINE_src_rule_268439607 ifc Interlink object-group FMC_INLINE_dst_rule_268439607 object-group IPSec_over_UDP rule-id 268439607 (hitcnt=0) 0x37d6d61a
access-list CSM_FW_ACL_ line 277 advanced permit udp ifc Interlink x.x.x.0 255.255.255.252 ifc Interlink x.x.x.0 255.255.255.252 eq 10000 rule-id 268439607 (hitcnt=0) 0xfa9d9d5c
access-list CSM_FW_ACL_ line 277 advanced permit udp ifc Interlink x.x.x.0 255.255.255.252 ifc Interlink x.x.x.4 255.255.255.252 eq 10000 rule-id 268439607 (hitcnt=0) 0x4d1f57ad
access-list CSM_FW_ACL_ line 277 advanced permit udp ifc Interlink x.x.x.4 255.255.255.252 ifc Interlink x.x.x.0 255.255.255.252 eq 10000 rule-id 268439607 (hitcnt=0) 0x2247f007
access-list CSM_FW_ACL_ line 277 advanced permit udp ifc Interlink x.x.x.4 255.255.255.252 ifc Interlink x.x.x.4 255.255.255.252 eq 10000 rule-id 268439607 (hitcnt=0) 0xc20f6752

FROM EXPERT MODE of FTD (CLI)
admin@FW201:~$ cat /var/sf/detection_engines/0b43cfec-a673-11e8-a02e-385aad3b79f3/ngfw.rules
268439607 allow 8 x.x.x.0 29 any 8 x.x.x.0 29 10000 any 17
268439607 allow 8 x.x.x.0 29 any 8 x.x.x.0 29 4500 any 17
268439607 allow 8 x.x.x.0 29 any 8 x.x.x.0 29 500 any 17
268439607 allow 8 x.x.x.0 29 any 8 x.x.x.0 29 50 any 6

Re: Blocked or blacklisted by the firewall preprocessor

Marvin Rhoads — Tue, 09 Jul 2019 03:38:03 GMT

If there aren't in an HA pair or cluster, how can they have the same configurations? Can you backup a step and tell us how you have them setup? Is this a lab?

Re: Blocked or blacklisted by the firewall preprocessor

G_Singh — Tue, 09 Jul 2019 03:59:21 GMT

Marvin,

I have 2x (2130) FTDs managed by FMC and all in production. Initially, we only needed 1 FTD and over the time things grew and added new FTD. Previously deployed FTD running version 6.2.3.12 and recently added FTD running version 6.2.1. Im unable to upgrade 6.2.1 to 6.2.3.12 therefore can not cluster/HA (TAC case logged).

Actually, I wasn't able to set up DMVPN/IPSec tunnels between our 2 HUBs which are behind each FTD. Tried running packet-tracer and seen this SNORT drop, now Im here and seeking advice on "Blocked or blacklisted by the firewall preprocessor". Mind you to establish tunnels between both HUBs traffic traverses thru both FTD

Question arises, should I wait to upgrade FTD 6.2.1 to 6.2.3.12 and then cluster/HA or should look for reason for DROP?

Thanks

Re: Blocked or blacklisted by the firewall preprocessor

Marvin Rhoads — Tue, 09 Jul 2019 05:10:00 GMT

To pass DMVPN/IPsec tunnels through the Firepower devices, you should allow the traffic in a prefilter rule - not an access control policy rule. You will need to allow:

UDP/500,

UDP/4500 and

ESP/AH (IP proto 50/51) depending on configuration.

...to your hub address. The action should be "Fastpath".

Re: Blocked or blacklisted by the firewall preprocessor

G_Singh — Wed, 10 Jul 2019 01:33:22 GMT

Thanks Marvin, added the prefilter and packet-tracer seems happy now!
As your last post, jsut making sure that when using DMVPN/IPSec tunnels then should ONLY use Prefilter not ACP rule?

Re: Blocked or blacklisted by the firewall preprocessor

Marvin Rhoads — Wed, 10 Jul 2019 02:48:51 GMT

You're welcome.

Yes, that's correct - only prefilter it with Fastpath action. Since the traffic is IPsec encapsulated and coming from known endpoints, none of the NGIPS processes (Snort, SI, Malware detection etc.) can add any value so prefilter will just Fastpath the DMVPN traffic to the post-processing stages (ALG, egress interface selection etc.).

FTD Order of Operations