Snort 2.9.2.3 pkg v. 2.5.0 Issues
-
@spi:
Hej ermal
Thanks for all your valuable knowledge and help here on snort.
Since libmysqlclient.so.18 file is missing after a reboot and not libmysqlclient.so.16
may I ask why it would not be more appropriate to apply```
pkg_add -v http://files.pfsense.org/packages/amd64/8/All/mysql-client-5.5.29.tbzthis will give version 18 and not 16 as version 5.1.53 would do…or does it not matter ?
Hi,
pkg_add -v -f -F http://files.pfsense.org/packages/8/All/mysql-client-5.5.29.tbz
worked on my machine. I had to use the "force" command because it complained about already having the package installed.
-
It should monitor and notify me about a specific program being used - The only way it will work in by monitoring my LAN interface, with HOME_NET containing my LAN network. Appreciate if you can clear that for me.
If I understood you right, you would be monitoring a network (LAN) that you have completely whitelisted -> nothing is getting filtered and no warnings will trigger.
-
If I understood you right, you would be monitoring a network (LAN) that you have completely whitelisted -> nothing is getting filtered and no warnings will trigger.
This is what happening when HOME_NET does not contains my LAN. When I set it manually (via snort.inc modification) I get the warnings and everything works as it should.
Am I doing something wrong and there is another way to get this information, or does the HOME_NET should include my local network?
-
Corrected teh HOME_NET generation.
Also the libmysql issues should be fixed. -
Ermal,
I checked again today and I am not seeing anything in the sys log about the auto update running or not running. If I run manual update i see the entries. Also I have removed blocked hosts after 6 hours and snort hasnt been doing that. I just changed it to three and restarted the service to see if something was glitched. Will monitor to see if that is working properly. Not sure if its isolated to just my setup or not. Just wanted to mention it to see if anyone else has had the issue. -
I get these errors when trying to change the ports of "Home NET"
-
First of all….
I get these false positives even if I have created them in the Suppress lists!!
-
Suppress list is here….
Tell me why Snort doesnt respect it.......... :-\
-
You need to have an alias cannot put ports there.
I wild guess about the suppression is a missing revision?
-
Ermal,
I checked again today and I am not seeing anything in the sys log about the auto update running or not running. If I run manual update i see the entries. Also I have removed blocked hosts after 6 hours and snort hasnt been doing that. I just changed it to three and restarted the service to see if something was glitched. Will monitor to see if that is working properly. Not sure if its isolated to just my setup or not. Just wanted to mention it to see if anyone else has had the issue.Can you check /etc/crontab if it has the entries for snort?
I pushed a fix which should help here.
Just resave yor settings on Global tab. -
@ermal:
Ermal,
I checked again today and I am not seeing anything in the sys log about the auto update running or not running. If I run manual update i see the entries. Also I have removed blocked hosts after 6 hours and snort hasnt been doing that. I just changed it to three and restarted the service to see if something was glitched. Will monitor to see if that is working properly. Not sure if its isolated to just my setup or not. Just wanted to mention it to see if anyone else has had the issue.Can you check /etc/crontab if it has the entries for snort?
I pushed a fix which should help here.
Just resave yor settings on Global tab.Here is what cron is showing. Looks like no time settings are entered. Looks like the remove host is doing the same thing as its blank too.. May explain why they arent being removed like they should.
-
I am not seeing the update on the dashboard… Guess it takes a while to recognize.. Will check back on it.. What version number is it up to now?
-
@ermal:
You need to have an alias cannot put ports there.
I wild guess about the suppression is a missing revision?
Why an alias when the specific ports are needed??
By the way, running on 2.5.4 so unless package has been updated, then I am on the latest revision.
-
No the version has not been bumped since some small fixes will come still.
When those are finished ti will be bumped. -
Thx Ermal!
-
Hi,
I have the issue with the lib mysql.18 which I was able to correct with pkg_add -v -f -F http://files.pfsense.org/packages/8/All/mysql-client-5.5.29.tbz
But when I reboot my VM, I have to do the command again, because snort won't start with my interfaces.
It is very weird because before rebooting everything was working perfectly fine, alerts were there, all interfaces were enabled…Anyone has an idea ?
Thanks in advance
-
It seems very weird because if I create a folder, after rebooting it is still there, but a modifications like the package is not working.
I suppose pfsense or Freebsd is blocking my modifications, is it possible to force the modification or disable the thing which is unabling me to saves changes ?
Thanks in advance
-
Are we seeing the end of this when Ermal/Bmeeks committed the last changes or do we have to wait until the package is bumped to 2.5.5??? So far running fine here, but havent upgraded to the last snaps from Ermal. Running the changed files from Bmeeks.
-
I have the latest downloaded and installed and everything seems to be working just fine here.
-
Are we seeing the end of this when Ermal/Bmeeks committed the last changes or do we have to wait until the package is bumped to 2.5.5??? So far running fine here, but havent upgraded to the last snaps from Ermal. Running the changed files from Bmeeks.
The "big pieces" for this update cycle are done, I think. My main focus was getting auto-flowbit resolution working and integrating the VRT Policy rules selection. Along with those main goals were some incidental fixes like the stream5 preprocessor memcap setting and some items related to http_inspect. At Ermal's request, the last change was some code to automatically scan for and disable any rules in the selected rule sets that depended on disabled preprocessors. This is necessary because certain preprocessor-dependent rule options (such as the ssl_state and ssl_version options associated with the SSL preprocessor) will cause Snort to error out and not start if the associated preprocessor is not enabled.
In my view, the next "big piece" is to update to the latest 2.4.x Snort binary. I am not ready to jump out there and start that project on my own, though. Still not experienced enough with the pfSense/BSD platform and its package building tools.
Bill