Snort Updating problems !!!
-
Giving it a try now. Will post back soon!
Update:
Seems to be working just fine - Rules updated and Snort running. Thanks jimp!!!pfsense: 2.1.5-RELEASE, AMD64
Running on: MB/CPU: ASUS P8H77-I / Core i3-2120T | MEM: 8GB DDR3 | HDD: WD Blue 120GB 2.5" SATA | WAN/LAN: Fujitsu D2735-2 – Intel® chip 82576NS | WLAN: Realtek® 8111F PCIe | Connection: 1000/1000Mbit (Bredband2.com)
[
/U -
I tried it on all 3 of my pfSense boxes and is working fine. Thanks again Jim!
-Jason
-
Looking good here!
Many thanks…
-
I uninstalled the old package and installed the new one and updated it no problem did a port scan test and all is working (fingers crossed) . ;D
-
Question for those brave people that updated (no going back) :)
Premium rules or basic rules?Hoping people have tested both…
-
I used the subscribed rules and everything is working great over here
-
Basic working fine for me.
-
Thanks for the feedback! I'll give it a whirl…
-
Thanks Jimp.
Snort now updates and works fine. (with Basic rules)
-
The updates are working fine now when I manually click update button, the version info states it is still package v 1.27 when it is actually 1.30.
Also, there is still that issue with rules getting enabled after updates. This is starting to become a pain. I know that this was discussed before and not sure if there is a fix.
I have a lot of rules that need to be disabled in certain categories I have to run, but everytime I get updates, it will enable the rules I disabled. Also it appears that the systems I am running are not getting updates automatically on the set time frame. I have a premium VRT license and currently running 8 PFsense boxes that all have the same issue.
Thanks for any help.
-
@darklogic82:
The updates are working fine now when I manually click update button, the version info states it is still package v 1.27 when it is actually 1.30.
Also, there is still that issue with rules getting enabled after updates. This is starting to become a pain. I know that this was discussed before and not sure if there is a fix.
I have a lot of rules that need to be disabled in certain categories I have to run, but everytime I get updates, it will enable the rules I disabled. Also it appears that the systems I am running are not getting updates automatically on the set time frame. I have a premium VRT license and currently running 8 PFsense boxes that all have the same issue.
Thanks for any help.
Those are separate issues from this thread, really. You might start a new thread for each of those issues separately, unless one already exists. I think there may already be some threads out there for the rules getting disabled.
Hopefully the normal package maintainer returns soon and can work on this a bit. I stepped in to fix the updates mentioned in this thread at the request of a commercial support customer, I'd have to spend quite a bit more time looking at the package to even speculate on fixes for the other issues.
-
Working good on 2.0. Thanks for the fix jimp.
-
It works great. ;D
You da man, JimP
-
I will try this soon, thanks JimP! The man who "wrote the book" wrote the snort fix :-) And probably quite a bit of pfSense itself, though I don't know the full extent of his contributions :-)
-
thanks jimp, fix that you provided makes my daily update jobs very easy, because I have been fetch/extract/install every single day by hand which is, annoying.
now that my concern is how you can conpromise longer i/f names that looks like 2.0 specific issue which won't snort from starting at the booting, or any other attempt. i tricked some diy for i/f naming but none of those were permanent fix, system will assign a new name, everytime reload the box.
any thoughts and ideas appreciated.
cheers,
-
now that my concern is how you can conpromise longer i/f names that looks like 2.0 specific issue which won't snort from starting at the booting, or any other attempt. i tricked some diy for i/f naming but none of those were permanent fix, system will assign a new name, everytime reload the box.
That's a matter for a separate thread.
Since the updates now work for everyone (so far) this particular issue is closed. If it breaks again, it'll be a new issue, and other problems should be in new threads.
Locking the topic. :-)
