Snort Won't Start After Upgrade
-
++
Can't wait.. and have already donated :)
snort should be directly integrated in the pfSense image as I can't imagine someone would open any port without using snort.
-
I wish I could donate, but I'm barely keeping my head above water right now…had two disasters to deal with and waiting for number three... Thanks anyway for all your hard work, James!
++
Can't wait.. and have already donated :)
snort should be directly integrated in the pfSense image as I can't imagine someone would open any port without using snort.
-
again any idea of a release date?
without snort it is not a good deal :(
best regards and many thanks for good work
-
-
-
+1
-
+1 from me.
Can't wait to have it up and running again! -
is there any chance to get a statement, or shall we better go back to the routes with pfsense build within working stable snort package ???
-
I am afraid we have to ….
-
is there any chance to get stable snort working again, perhaps by installing over shell ?
i don´t want to wait any longer for the new one because i see no release time !
thanks and best regards
btw: i installed snapshot from June 22th again
-
I attempted to reinstall snort and the reinstall failed. I am using PF 2.0RC3, updated yesterday. Since the reinstall failed, I don't see any of the snort packages listed in "available" or "installed".
If I understand this thread correctly, at the moment, there is no snort package available at all, stable or dev?
-
I attempted to reinstall snort and the reinstall failed. I am using PF 2.0RC3, updated yesterday. Since the reinstall failed, I don't see any of the snort packages listed in "available" or "installed".
If I understand this thread correctly, at the moment, there is no snort package available at all, stable or dev?
same problem to me, what is going on NOW with snort, can anyone please give a statement ?!
it is of course not a good deal to kick all snort packages and nothing happens at all :-(
thx and regards
-
it is of course not a good deal to kick all snort packages and nothing happens at all :-(
+1
-
I think that this not quite fair to the developers.
If they need time then they should have it. Or if you need it so badly why don't you make bounty for it -
Or if you need it so badly why don't you make bounty for it
Can't wait.. and have already donated :)
You mean I should have used the money for a bounty instead?
Or directly for some
.. would have been better ::) -
Now that's not fair, James…getting me all excited thinking that you were gonna say that Snort's ready to start snorting again. I'm sniffing with tears :'(
-
but i think they could leave the stable snort package online until the new one is released - when ever this could be…
i cannot find any reason to kick the stable package and nothing happens :-(
-
just remember that patience is a virtue… ;)
but i think they could leave the stable snort package online until the new one is released - when ever this could be…
i cannot find any reason to kick the stable package and nothing happens :-(
-
++
Can't wait.. and have already donated :)
snort should be directly integrated in the pfSense image as I can't imagine someone would open any port without using snort.
I agree with this sentiment, running 1.23 ( not upgrading ) until this is A-OK seems the best path. Runnin' a RC, things like this are to be expected.
-
Runnin' a RC, things like this are to be expected.
Ok and what do you say about this? http://blog.pfsense.org/?p=589
There are considerably fewer open issues on 2.0 right now than there were on 1.2.3 when it was released, and no major outstanding problems. 2.0 has gotten widespread use in production environments over the last year plus including in our most critical networks, and looks to be ready for release. We expect final release within a month, and consider RC3 the preferred release for all new installs.
I used it in a critical network too..
