Re: [SUSPECTED SPAM] snort3.0 doesn't log the triggering packet of an alert

[João Soares <joaosoares11 () hotmail com>]

I forgot to mention one important thing:

During that test I uncommented most of the rules available (except deleted.rules and others I can't remember), so it 
was a pretty rough stress test to Snort. I don't how how it would've performed with 1000-2000 rules only.

On 11/01/2017 10:14, João Soares wrote:

Hi,

Surprisingly it's libpcap. I will most likely play with pf_ring later this year.

My way of load balancing for now is probably not the best, I'm splitting the traffic using linux bonding and bridging 
into 12 dummy interfaces, and then Snort is listening on all those 12 interfaces. This way I'm essentially forcing 
Snort to use 12 threads.

As for supporting 10Gbps, well I tested this while doing my master's thesis, but I only had 1 thread running at that 
time. **With only 1 thread**, and assuming your traffic is actually a constant 9-10Gbps (I simulated this will 
tcpreplay), Snort will place most of your packets in a queue, so I believe it's not ideal for more than ~2Gbps. 
Nevertheless, I haven't tested it thoroughly with 12 threads, but I'm feeling it will do great, even better if I start 
using pf_ring I suppose. I still have much to learn.

On 11/01/2017 03:05, Maxim wrote:
Hi Joao,
Sorry that I cannot spell your name correctly using that letter with a hat on it^_^. I think they are related. If 
nobody answer it, we have to dive into the source code to figure out why. By the way, you said in your question that 
you started 12 threads to process captured packets. May I know what type of DAQ did you use? pf_ring or DPDK? What's 
the performance? Can it reach 10 gigabytes? Many thanks.




At 2017-01-09 23:24:19, "João Soares" <joaosoares11 () hotmail com><mailto:joaosoares11 () hotmail com> wrote:

Hi, I'm sorry to interrupt this conversation but I believe I had a similar issue, but unfortunately nobody answered. 
Maybe we can solve both of our problems :)

https://sourceforge.net/p/snort/mailman/message/35565599/

Are these issues related? I'm logging .pcaps and alerts separately, not using the unified format.

On 09/01/2017 14:03, Russ wrote:


On 1/9/17 2:53 AM, Maxim wrote:
Hi Albert,
In seciont 1.3.2 of snort3.0 manual,  there is a saying:
   "-A u2 is the same as -A unified2 and will log events and triggering packets in a binary file that you can feed to 
other tools for post processing. Note that Snort 3 does not provide the raw packets for alerts on PDUs; you will get 
the actual buffer that alerted. "

I think it does something to do with this. Am I right?
Correct.  We can try to provide more information.  Please describe the info you need and how you use it.  In general, 
raw packets aren't terribly helpful, but we could log other buffers as well.

Hittlle




At 2017-01-09 11:46:42, "Maxim" <hittlle () 163 com><mailto:hittlle () 163 com> wrote:
Hi Albert,
It is the HTTP request packet that fires the alert, so this packet should be recorded, right? And all packets in the 
same session after this offensive request packet should be logged, right? Many thanks.





At 2017-01-07 06:37:19, "Al Lewis (allewi)" <allewi () cisco com<mailto:allewi () cisco com>> wrote:
You can capture the session traffic with just the tagging.

I don’t think your problem is with the session/tagging functionality. You need to create a rule that alerts THEN starts 
recording.

Snort will not be able to go back and capture packets BEFORE the rule alerted. So if you have a rule that alerts on a 
response packet Snort will not be able to go back and “recapture” the request or packets that happened BEFORE the alert.

See attached. It uses a telnet session to alert on the SYN flag, then logs traffic for the next second.

I ran snort like this

"snort -c etc/snort/maxim.lua -r etc/snort/maxim.pcap -k none -l . “

 which produced the pcap, alert, codec and unified log files.


Hope this helps.

Albert Lewis
ENGINEER.SOFTWARE ENGINEERING
SOURCEfire, Inc. now part of Cisco
Email: allewi () cisco com<mailto:allewi () cisco com>

From: Maxim <hittlle () 163 com<mailto:hittlle () 163 com>>
Date: Thursday, January 5, 2017 at 9:41 PM
To: allewi <allewi () cisco com<mailto:allewi () cisco com>>
Cc: 'snort-users' <snort-users () lists sourceforge net<mailto:snort-users () lists sourceforge net>>
Subject: Re:Re: [SUSPECTED SPAM] [Snort-users] snort3.0 doesn't log the triggering packet of an alert

Hi Albert,
Thanks for your help. Attached please kindly find my snort.lua. My question is not that snort doesn't record any 
packets to unified2 file, but the first packet that triggeres the alert. What I am doing is this: if a packet fire a 
rule, tell snort to record the bidirectional packets (packets belonging to the same session) of that session. So, I 
write the following rule:

             alert tcp any any -> any 80 ( msg:"test-http-req-body"; content:"abc";http_client_body; 
flowbits:isnotset,105;flowbits:set,105;tag:session;sid: 105;rev:1;)

As you can see, I used flowbits and tag:session to accomplish this. And ran snort this way:
            /opt/snort3.0/bin/snort -c /var/log/snort/snort.lua -i eth0 -D -l /var/log/snort/

As you can see from the attached unified2 log file, I can see the alert, and the HTTP response packet. But I cannot 
find the request packet payload information there. Am I missing something here? Thanks.






At 2017-01-05 19:17:23, "Al Lewis (allewi)" <allewi () cisco com<mailto:allewi () cisco com>> wrote:
Hello Maxim,

Please see the section under the snort3 manual for loggers:

https://s3.amazonaws.com/snort-org-site/production/release_files/files/000/004/860/original/snort_manual.html?AWSAccessKeyId=AKIAIXACIED2SPMSC7GA&Expires=1483618124&Signature=4RZ4GTblHk9jmFlDhjHddxo%2BA28%3D#_logger_modules


Its impossible to say what the issue is without a copy of your configuration.

Attached is a basic config that should log any tcp packet.

All I did was run it with this below:

./bin/snort -c etc/snort/maxim.lua -r /home/alewis/Downloads/CURL.pcap -l .


And it produced log files as these (unified log is there):


alewis@box3:/var/tmp/snort++$ ls
alert_full.txt  bin  core  etc  include  lib  log_codecs.txt  share  unified2.log
alewis@box3:/var/tmp/snort++$


Albert Lewis
ENGINEER.SOFTWARE ENGINEERING
SOURCEfire, Inc. now part of Cisco
Email: allewi () cisco com<mailto:allewi () cisco com>

From: Maxim <hittlle () 163 com<mailto:hittlle () 163 com>>
Date: Thursday, January 5, 2017 at 3:19 AM
To: 'snort-users' <snort-users () lists sourceforge net<mailto:snort-users () lists sourceforge net>>
Subject: [SUSPECTED SPAM] [Snort-users] snort3.0 doesn't log the triggering packet of an alert

Hi snort experts,
    I just tried snort 3.0, and found that it doesn't log the triggering packet of an alert if I use unified2 logger. 
Is it a bug or am I missing any required configurations? It's very different from snort 2.9.8.0. Many thanks.














【网易自营|30天无忧退货】MUJI同款日式简约名片盒严选价仅29元，马上入>><http://you.163.com/item/detail?id=1043019&from=web_gg_mail_jiaobiao_7>



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot



_______________________________________________
Snort-users mailing list
Snort-users () lists sourceforge net<mailto:Snort-users () lists sourceforge net>
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://sourceforge.net/mailarchive/forum.php?forum_name=snort-users

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




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot



_______________________________________________
Snort-users mailing list
Snort-users () lists sourceforge net<mailto:Snort-users () lists sourceforge net>
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://sourceforge.net/mailarchive/forum.php?forum_name=snort-users

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









------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi



_______________________________________________
Snort-users mailing list
Snort-users () lists sourceforge net<mailto:Snort-users () lists sourceforge net>
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://sourceforge.net/mailarchive/forum.php?forum_name=snort-users

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

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi

_______________________________________________
Snort-users mailing list
Snort-users () lists sourceforge net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://sourceforge.net/mailarchive/forum.php?forum_name=snort-users

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