Snort problem
-
@1clicc:
It couble be because i just install snort last night. When do you think this will be fix?
Last I heard they were waiting to hear back from the person who submitted the updated package. If it can't be made to work, I imagine it will get rolled back to the last working version. You can watch the package commit logs to see if anything has changed:
https://rcs.pfsense.org/projects/pfsense-packages
-
Hope this can be resolve very soon. Please do keep us updated when there's a fix. Thanks you.
-
Hey guys, may i have the previous working version because i think this going to be awhile before it will be fix. Anyone know where i can download the previous version? and how would i manually install it? Thanks and much appreciation.
-
Hello Guys
attached please find the snort.inc that now fix the problem, and snort is running again.
the thing is I have disabled the new "dcerpc2" & "dcerpc2_server" and got back to the old "dcerpc" that does exist.go to Edit file under pfsense menu and load: /usr/local/pkg/snort.inc and replace the content of this file with the one that is attached.
thats it, snort will be working perfectly now.good luck. :)
-
Hello Guys
attached please find the snort.inc that now fix the problem, and snort is running again.
the thing is I have disabled the new "dcerpc2" & "dcerpc2_server" and got back to the old "dcerpc" that does exist.go to Edit file under pfsense menu and load: /usr/local/pkg/snort.inc and replace the content of this file with the one that is attached.
thats it, snort will be working perfectly now.good luck. :)
Actually i got this error now:
May 23 10:18:54 snort[2335]: FATAL ERROR: /usr/local/etc/snort/snort.conf(214) => FTP Commands are no longer than 4 characters: '#MACB'.
May 23 10:18:54 snort[2335]: FATAL ERROR: /usr/local/etc/snort/snort.conf(214) => FTP Commands are no longer than 4 characters: '#MACB'.
May 23 10:19:11 SnortStartup[2408]: Ram free BEFORE starting Snort: 88M – Ram free AFTER starting Snort: 88M -- Mode ac-sparsebands -- Snort memory usage:Any recommendation? because snort is not start also.
-
Its mean that you didn't save the file correctly cause the change wasn't implemented.
after implementing the file you need to save. and then save again in the snort setting page.also I have checked and the netbios rules should not be checked till the dcerpc2 and dcerpc2_server, will be compiled correctly into the snort package
-
this is fixed in the package now
-
What is fixed?
i do not see any package update?
can you please be more specific what is fixed? and how? did you add the preprocessor "dcerpc2" and the preprocessor "dcerpc2_server" ?
or just modify the snort.inc to disable the use of them? -
@cmb:
this is fixed in the package now
OK, Confirm that it is now working after i uninstall and reinstall from the package. Thanks guys you guys are highly appreciated.
-
Well it is not really fixed…. netbios rules still get snort to fail.
-
Well it is not really fixed…. netbios rules still get snort to fail.
Use the netbios.rules from the so_rules folder.
-
I've tried all of the suggestions contained within this thread and it's still not functioning properly. My PfSense box has been up and running for over 30 hours and not a single Snort alert in all that time. I just don't understand what the problem is. Can anyone advise?
Thanks…
-
I've tried all of the suggestions contained within this thread and it's still not functioning properly. My PfSense box has been up and running for over 30 hours and not a single Snort alert in all that time. I just don't understand what the problem is. Can anyone advise?
Thanks…
Do you have any snort rules in the Categories section of snort? If you are using pfsense 1.2.2 version i believe that it's haveing problem updating the rules so you might have to manually download the latest rules from snort.org and do a SSH and also manually install the rules. If you have the latest rules already install than you might have to start the service.
-
@1clicc:
I've tried all of the suggestions contained within this thread and it's still not functioning properly. My PfSense box has been up and running for over 30 hours and not a single Snort alert in all that time. I just don't understand what the problem is. Can anyone advise?
Thanks…
Do you have any snort rules in the Categories section of snort? If you are using pfsense 1.2.2 version i believe that it's haveing problem updating the rules so you might have to manually download the latest rules from snort.org and do a SSH and also manually install the rules. If you have the latest rules already install than you might have to start the service.
Ironically, Snort worked perfectly on 1.2.2. The problems started as soon as I "upgraded" to 1.2.3 RC-1. After monkeying with it for far too long, I finally "downgraded" back to 1.2.2–a version known to work on my machine. Unfortunately, Snort doesn't run on 1.2.2 now either. But I appreciate the suggestion. I'll try it again.
-
Ironically, Snort worked perfectly on 1.2.2. The problems started as soon as I "upgraded" to 1.2.3 RC-1. After monkeying with it for far too long, I finally "downgraded" back to 1.2.2–a version known to work on my machine. Unfortunately, Snort doesn't run on 1.2.2 now either. But I appreciate the suggestion. I'll try it again.
I would tell you to try reinstalling snort; there was a problem recently and doing a reinstall corrected my brief issues, so do that first. Then try re-doing your pfSense box. I can't say how many times I've redone mine over problems I didn't understand. Which has got me in hot water with the Mrs. I have changed my setup at least 10 times. I now have two pfSense boxes running snort - the netbios rules + using ac-bnfa and have squid running on the second box behind the first WAN connected pfSense box. If at first you don't succeed, try again.
-
Hi.
Sorry I have been gone. I just started a new job and have been really busy.
Snort 2.8.4.1 right now does not work because the mysql client port is out of date.
Mysql client needs to be at mysql 5.1, dependencies libdnet-1.11_3.tbz and pcre.7.9 must be installed.
Moreover, It seems that the snort port and the mysql client port were built on different machines.
Sourcefire is using the new RPC2 netbios rules so snort needs to be at snort 2.8.4.1.My snort.inc is good so theres no need to comment out the RPC2 options.
I emailed the core team on how to fix the package hopefully this will be resolved today.
I'll be hear all day so, please ask and I will respond to any messages.thanx
-
Well it is not really fixed…. netbios rules still get snort to fail.
Same problem here.
-
Well it is not really fixed…. netbios rules still get snort to fail.
Same problem here.
reinstall the snort. should work now.
-
seems to work now, no errors in log.
thanks for the update..
John
-
i've just reinstalled twice the snort package, but i can't start-up the snort service, here are the log:
May 26 18:35:47 xxxxx snort[23564]: Initializing daemon mode
May 26 18:35:47 xxxxx snort[23564]: Initializing daemon mode
May 26 18:35:47 xxxxx snort[23567]: PID path stat checked out ok, PID path set to /var/run/
May 26 18:35:47 xxxxx snort[23567]: PID path stat checked out ok, PID path set to /var/run/
May 26 18:35:47 xxxxx snort[23567]: FATAL ERROR: Failed to Lock PID File "/var/run//snort_em1.pid" for PID "23567"
May 26 18:35:47 xxxxx snort[23567]: FATAL ERROR: Failed to Lock PID File "/var/run//snort_em1.pid" for PID "23567"
May 26 18:35:48 xxxxx snort[23564]: Child exited unexpectedly
May 26 18:35:48 xxxxx snort[23564]: Child exited unexpectedly
May 26 18:35:48 xxxxx snort[23564]: Daemon parent exiting
May 26 18:35:48 xxxxx snort[23564]: Daemon parent exiting
May 26 18:35:56 xxxxx snort2c[23647]: snort2c running in daemon mode pid: 23647
May 26 18:35:56 xxxxx snort2c[23647]: snort2c running in daemon mode pid: 23647
May 26 18:36:13 xxxxx SnortStartup[23667]: Ram free BEFORE starting Snort: 59M – Ram free AFTER starting Snort: 59M -- Mode ac-bnfa -- Snort memory usage:i've tried to stop the snort service, remove the file /var/run/snort_em1.pid.lck and start the snort service again, and even reboot my pfsense, but got the same log as above.
any trick?
