[prev in list] [next in list] [prev in thread] [next in thread]
List: snort-users
Subject: [Snort-users] Snort crash on a Kunbus Revolution Pi connect +
From: Nestor Eduardo Ramos Perez via Snort-users <snort-users () lists ! snort ! org>
Date: 2020-03-20 16:18:39
Message-ID: CAOdgXGOQR5e6=-v93z-kPgyhe52AYoZXwvekzjagNfg_Hri=Qw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Snort version: 2.9.15.1
Rules enabled: all the rules obtained from the registration set
Snort installation: binaries downloaded from Snort.org
Configuration files: I only modified the snort.conf with my home-net Ip
address and the rules path
Os: Debian 9, linux kernel
Hardware: Kunbus Revolution Pi connect + (based on a Raspberry Pi 3), 1 GB
of RAM
HI everyone,
I have encountered a problem when launching Snort on a Revolution Pi
connect + device (basically a Raspberry Pi 3). When starting Snort with the
following command: "*snort -A console -c snort.conf", *Snort is killed in
the initialisation process by the OS (see screenshot attached
"snort-crash.png"). I even used the *top* command in order to see my CPU
and memory load and when I start Snort, the CPU goes to 99% of utilization
(see screenshot "CPU-utilization").
I am aware that running Snort on a Raspberry Pi architecture is not
recommanded but I only need Snort for a very basic usage. Therefore, I
tried the community rules set and Snort didn't crash. As this is part of my
Master thesis, I need to explain exactly why Snort was killed with the
other rule set.
I look forward hearing from you.
Regards,
Nestor Eduardo Ramos Perez
[Attachment #5 (text/html)]
<div dir="ltr">Snort version: 2.9.15.1<div>Rules enabled: all the rules obtained \
from the registration set</div><div>Snort installation: binaries downloaded from \
Snort.org</div><div>Configuration files: I only modified the snort.conf with my \
home-net Ip address and the rules path</div><div>Os: Debian 9, linux kernel \
</div><div>Hardware: Kunbus Revolution Pi connect + (based on a Raspberry Pi 3), 1 \
GB of RAM </div><div><br></div><div>HI everyone,</div><div><br></div><div>I have \
encountered a problem when launching Snort on a Revolution Pi connect + device \
(basically a Raspberry Pi 3). When starting Snort with the following command: \
"<span style="color:rgb(0,0,0)"><i>snort -A console -c snort.conf", \
</i>Snort is killed in the initialisation process by the OS (see screenshot attached \
"snort-crash.png"). I even used the <i>top</i> command in order to see my \
CPU and memory load and when I start Snort, the CPU goes to 99% of utilization (see \
screenshot "CPU-utilization"). </span></div><div><span \
style="color:rgb(0,0,0)">I am aware that running Snort on a Raspberry Pi architecture \
is not recommanded but I only need Snort for a very basic usage. Therefore, I tried \
the community rules set and Snort didn't crash. As this is part of my Master \
thesis, I need to explain exactly why Snort was killed with the other rule \
set.</span></div><div><span style="color:rgb(0,0,0)"><br></span></div><div><span \
style="color:rgb(0,0,0)">I look forward hearing from you.</span></div><div><span \
style="color:rgb(0,0,0)"><br></span></div><div><span \
style="color:rgb(0,0,0)">Regards,</span></div><div><span \
style="color:rgb(0,0,0)"><br></span></div><div><span style="color:rgb(0,0,0)">Nestor \
Eduardo Ramos Perez</span></div></div>
_______________________________________________
Snort-users mailing list
Snort-users@lists.snort.org
Go to this URL to change user options or unsubscribe:
https://lists.snort.org/mailman/listinfo/snort-users
To unsubscribe, send an email to:
snort-users-leave@lists.snort.org
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
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic