Snort-dev ready for testing. Post issues here.
-
found a bug with the alert gui, the alert file is being updated but the gui is not displaying it.
EDIT: I copied the stable snort_alerts.php page and corrected the alert file it looking for
snort_alerts.php. Copyright (C) 2003-2004 Manuel Kasper ``` -
Jamesdean,
Thanks for letting me know that the issues are receiving attention. I can be patient now knowing that the right guys are aware of the problem.
-
the new pbi allows the block setting to be checked, but i haven't been able to test it yet
can't stop snort from its package status page, using Services pages to restart…
snort is unable to open rules..... not sure what the problem is, thinking the syntax or something
snort[30707]: FATAL ERROR: Unable to open rules file "/usr/local/etc/snort/snort_39737_em3//usr/local/etc/snort/snort_39737_em3/rules/emerging-attack_response.rules||emerging-ciarmy.rules||emerging-compromised.rules||emerging-current_events.rules||emerging-dos.rules||emerging-drop.rules||emerging-dshield.rules||emerging-exploit.rules||emerging-inappropriate.rules||emerging-malware.rules||emerging-mobile_malware.rules||emerging-rbn-malvertisers.rules||emerging-scada.rules||emerging-scan.rules||emerging-shellcode.rules||emerging-trojan.rules||emerging-virus.rules||emerging-worm.rules": No such file or directory.snort[35944]: FATAL ERROR: Unable to open rules file "/usr/local/etc/snort/snort_39737_em3//usr/local/etc/snort/snort_39737_em3/rules/emerging-attack_response.rules||snort_attack-responses.rules||snort_backdoor.rules": No such file or directory. -
latest fixes fixed the rule issue i was having
other issues… NETLIST isn't picking up IPv6 addresses for LAN or WAN interfaces... When manually added them to a NETLIST, its being ignored... Looks like it works with a WHITELIST but can't put IPv6 subnet in it, its ignored.
Is there a way to turn off IPv6 in snort without rebuilding? It was working prior to 2.9.2.3, worked in 2.9.0.5. Turned the Block feature off for now..
You already noted its a mess, but the block page isn't displaying anything.. Was able to tell via snort2c table
-
If you are having "/libexec/ld-elf.so.1: /usr/local/lib/libdnet.1: unsupported file layout" errors that meanse there is somthing corrupt
with your installation of snort.Error may come from mixing am64 pfsense with 32 bit binaries.
Error may come from mixing snort pbi and snort tbz files.
I suggest you remove everything snort related or do a fresh pfSense OS install.
Robert
-
noticed when i uncheck log alerts to system log, it still logs to the system log
-
Thanks Cino.
I'll get to the "system log" issue when Im done with ipv6 support NETLISTS.
Robert
-
Thanks Cino.
I'll get to the "system log" issue when Im done with ipv6 support NETLISTS.
Robert
Thanks Robert! No rush on this one ;-) As i find them, big or small; I'll report'em
Stephen
PS Jim found an issue with the builder for pbi, where certain options weren't being added during the build process. He has fixed it but now he has to rebuild all the pbi's.. Wondering if it will resolve the NETLIST issue when the next snort pbi is build
-
This is really unimportant, but…
Is there any chance you can make add a /snort/index.php that redirects to the /index.php for pfSense?
Every time I'm in snort and I want to get back to my dashboard, I click the pfSense logo and get a "404 Not Found" error because the browser wants to stay in the /snort/ directory...
I guess I could do it myself, but figured it'd be nice to have in the package! :)
-
I'm running a fresh install of Snort-dev on 2.0.1-RELEASE (amd64) and nothing is showing under the blocked tab. /tmp/snort_blocked.cache seems to have the correct entries so I think it's blocking and just a GUI bug.
-
I'm running a fresh install of Snort-dev on 2.0.1-RELEASE (amd64) and nothing is showing under the blocked tab. /tmp/snort_blocked.cache seems to have the correct entries so I think it's blocking and just a GUI bug.
I reported this last week. its blocking, look at the snort2c table
-
This is really unimportant, but…
Is there any chance you can make add a /snort/index.php that redirects to the /index.php for pfSense?
Every time I'm in snort and I want to get back to my dashboard, I click the pfSense logo and get a "404 Not Found" error because the browser wants to stay in the /snort/ directory...
I guess I could do it myself, but figured it'd be nice to have in the package! :)
Doesn't this only happen when you have the widescreen package installed?
-
This is really unimportant, but…
Is there any chance you can make add a /snort/index.php that redirects to the /index.php for pfSense?
Every time I'm in snort and I want to get back to my dashboard, I click the pfSense logo and get a "404 Not Found" error because the browser wants to stay in the /snort/ directory...
I guess I could do it myself, but figured it'd be nice to have in the package! :)
Doesn't this only happen when you have the widescreen package installed?
I think your right. Works fine on 2.1 right now
-
Doesn't this only happen when you have the widescreen package installed?
Ah okay good to know! Thanks.
-
Snort-dev seems to loose blocked hosts on 2.0.1 amd64.
My blocking time is set to 3 hours. A host gets blocked correctly when a matching rule fires. Sometimes this host gets out of snort2c table even if there where multiple new alerts from the same host meanwhile. So it also seems that the remaining blocking time does not get updated after a new alert.Greets, Judex
-
It seems that snort-dev shuts down on the first alert after an automatic rule update. I observed that at leats twice.
Here's the log:
Jun 29 00:10:07 gatekeeper snort[62591]: FATAL ERROR: s2c_pf_block() => ioctl() DIOCRADDADDRS: Bad file descriptor
Jun 29 00:10:07 gatekeeper kernel: em1: promiscuous mode disabled -
It seems that snort-dev shuts down on the first alert after an automatic rule update. I observed that at leats twice.
Here's the log:
Jun 29 00:10:07 gatekeeper snort[62591]: FATAL ERROR: s2c_pf_block() => ioctl() DIOCRADDADDRS: Bad file descriptor
Jun 29 00:10:07 gatekeeper kernel: em1: promiscuous mode disabledI was testing whitelist changes today and enabled blocking, I'm seeing the same issues.
Is there an issue with the pf patch that was applied?
Jul 4 08:28:56 snort[4839]: FATAL ERROR: s2c_pf_block() => ioctl() DIOCRADDADDRS: Inappropriate ioctl for device Jul 4 08:28:56 snort[4839]: FATAL ERROR: s2c_pf_block() => ioctl() DIOCRADDADDRS: Inappropriate ioctl for device -
attempted snort-dev install on two amd64 boxes. Installation does not finish. It hangs at "loading package information".
Cheers,
Dennis. -
attempted snort-dev install on two amd64 boxes. Installation does not finish. It hangs at "loading package information".
Cheers,
Dennis.+1
-
It seems like php closure code that you used on snort.inc file is compatible only with php5.3(pfsense 2.1)
$snort_calc_iface_subnet_list = function($int) use(&$home_net)Starting package snort-dev…
Parse error: syntax error, unexpected T_FUNCTION in /usr/local/pkg/snort/snort.inc on line 183
