Re: Snort 3 not dropping packets in IPS/inline mode

"Steven Baigal \(sbaigal\) via Snort-users" <[email protected]>
Newsgroups gmane.comp.security.ids.snort.general
Message-ID <BL0PR11MB2898A7621FC7E84053334932B35A9@BL0PR11MB2898.namprd11.prod.outlook.com>
I’ll suggest you verify your network setup first: stop the snort and ping between your endpoints, there should not be any traffic passing between your test endpoints.

From: Mikha George <[email protected]>
Date: Thursday, January 20, 2022 at 12:17 PM
To: Steven Baigal (sbaigal) <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: [Snort-users] Snort 3 not dropping packets in IPS/inline mode
Exactly my point, the rules are set correctly and shows the below in fast alert mode.

[cid:ii_kyn8hlog3]

But in reality the verdict is showing pass and also snort3 is not dropping the packet. I did not have this problem while using snort2.9.
Here is my test rule:

drop icmp any any -> $HOME_NET any (msg:"ICMP connection test"; sid:1000001; rev:1;)
drop tcp any any -> $HOME_NET 80 (msg:"TCP connection test"; sid:1000002; rev:1;)

On Thu, Jan 20, 2022 at 10:32 PM Steven Baigal (sbaigal) <[email protected]<mailto:[email protected]>> wrote:
I only see pass verdict from this log. Are these packets expected to be dropped? Check your ips rules and make sure you have correct rules for your setup.

From: Mikha George <[email protected]<mailto:[email protected]>>
Date: Thursday, January 20, 2022 at 11:39 AM
To: Steven Baigal (sbaigal) <[email protected]<mailto:[email protected]>>
Cc: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>
Subject: Re: [Snort-users] Snort 3 not dropping packets in IPS/inline mode
Hi Steven,

Thank you for the response.

Enabling the packet tracer showed the below result.

[cid:17e787a7758f2a753933]

On Thu, Jan 20, 2022 at 9:05 PM Steven Baigal (sbaigal) <[email protected]<mailto:[email protected]>> wrote:
You can enable packet tracer to debug the issue and see if the verdict was applied correctly:

packet_tracer = { enable = true, }

and you can also capture the pcap to see if tcp RST is generated correctly for both directions.
If you are using VLAN, please try the latest code, there was a bug fix related to drop connection for vlan traffic.


From: Snort-users <[email protected]<mailto:[email protected]>> on behalf of Mikha George via Snort-users <[email protected]<mailto:[email protected]>>
Date: Wednesday, January 19, 2022 at 5:43 PM
To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>
Subject: [Snort-users] Snort 3 not dropping packets in IPS/inline mode
Snort 3 is not dropping the packets even after the rule specifies to block packets. It is running in inline mode and shows drop but the packets are being sent however.

Snort is using the DAQ modules for running in inline mode. The command I use to run snort is as below:

./snort --daq-dir /usr/local/lib/daq --daq afpacket --daq-var debug --daq-var fanout_type=hash -i eth0:eth1 -Q -R /usr/local/snort/rules/local.rules -A alert_fast

I have two network interfaces attached as required which are up and running.

Any help is highly appreciated and would mean a lot. PFA screenshot for reference.



Thanks & Regards,

Mikha George
[cid:17e787a7757cb971f161]

[cid:17e787a7758f453195c2]

_______________________________________________
Snort-users mailing list
[email protected]
Go to this URL to change user options or unsubscribe:
https://lists.snort.org/mailman/listinfo/snort-users

	To unsubscribe, send an email to:
	[email protected]

Please visit http://blog.snort.org to stay current on all the latest Snort news!

Please follow these rules: https://snort.org/faq/what-is-the-mailing-list-etiquette
image.png (image/png, 62.7 KB) - not displayed
image[27].png (image/png, 178.5 KB) - not displayed
image[73].png (image/png, 24.7 KB) - not displayed
image[75].png (image/png, 280.4 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.