Snort update coming soon – please read about an important change!
-
Hello,
sorry for disturbing, but there is no package available for download:
Look here: https://files.pfsense.org/packages/amd64/8/All/
Is there the read-acces to everyone set or not?
-
I thing the file is not uploaded yet.. i cant see it..
-
How ?
So how can u download it ?I just clicked the links in this post… It downloaded. Double-slash or not.
SHA1:
39d45298585c32b79368d3ead1188326aeb6e961 *snort-2.9.6.0-amd64.pbi
-
lol? there is something strange…
-
I thing the file is not uploaded yet.. i cant see it..
The same here. Indeed, it looks like file hasn't been uploaded yet:
-
-
The vast majority of us still cannot see the package uploaded. Maybe a read permission issue? Or a rsync hiccup?
Regards,
Luigi
-
Yeah.. I'm not seeing that file there :)
Maybe it's an issue with some of the mirrors?
-
$ host files.pfsense.org files.pfsense.org has address 208.123.73.81 files.pfsense.org has IPv6 address 2610:1c0:1:25::57
-
Still nothing here, even browsing at the I.P. address you pointed out… :(
$ host files.pfsense.org files.pfsense.org has address 208.123.73.81 files.pfsense.org has IPv6 address 2610:1c0:1:25::57
-
$ host files.pfsense.org files.pfsense.org has address 208.123.73.81 files.pfsense.org has IPv6 address 2610:1c0:1:25::57
definitly not there or we cant see it
-
I just checked for the i386 package that I need. On the IPv6 site it is available but NOT on the IPv4 site (yet I hope).
-
The strange thing is that if I click the links here at the office, the file downloads. If I access from home via my pc or pfsense it cant be found. Tested via ipad from a wifi hotspot and it failed… so not sure why the links work here at the office. If I browse the directory I can see it from here as well. Try that from home or from ipad do not see it at all..
-
The strange thing is that if I click the links here at the office, the file downloads. If I access from home via my pc or pfsense it cant be found.
As said above, it only works over IPv6.
-
The strange thing is that if I click the links here at the office, the file downloads. If I access from home via my pc or pfsense it cant be found.
As said above, it only works over IPv6.
Ahh missed that.. guess thats it then.. guess i need to dload the file here upload to the firewall at other location then install it via command line…
-
Hello,
and what about this message trying to get the packeage via browser?
404 Not Found
files.pfsense.org has address 208.123.73.81
files.pfsense.org has IPv6 address 2610:1c0:1:25::57I guess on your Webserver the content for ipv4 is not set correctly or the rights are different. Is the folder the same on your webserver for ipv4 and ipv6?
:(
-
Well I noticed the new snort package is ready to download. I gave it a shot and noticed 2 things:
1: It wont allow me to have 2 sensors using the same interface anymore. I've had 2 WAN Sensors (1 for blocking and another for testing/alerting new rules)
2: My WAN interface wont start:Apr 8 09:10:30 php: /snort/snort_interfaces.php: The command '/usr/local/bin/snort -R 60770 -D -q -l /var/log/snort/snort_em360770 --pid-path /var/run --nolock-pidfile -G 60770 -c /usr/pbi/snort-i386/etc/snort/snort_60770_em3/snort.conf -i em3' returned exit code '1', the output was '' Apr 8 09:10:30 snort[34127]: FATAL ERROR: /usr/pbi/snort-i386/etc/snort/snort_60770_em3/rules/snort.rules(7703) : pcre compile of "(obj.data|\object.data).+file\x3A\x2F\x2F127\x2E[0-9]" failed at offset 11 : missing opening brace after \o
Before upgrade I did an uninstall then removed every snort reference on the filesystem, "find /* | grep -i snort | xargs rm -rv"
-
The strange thing is that if I click the links here at the office, the file downloads. If I access from home via my pc or pfsense it cant be found.
As said above, it only works over IPv6.
What about the folks without ipv6?
-
IPv4 here and still waiting to see the package here: http://files.pfsense.org/packages/8/All/
Any news??? :( -
@/CS:
Any news??? :(
Any news would need to come from the developers/people with access to the HW. Frankly, pretty much everything that could go wrong did go wrong with all those migrations, even the 2.1.1 release got messed up. Dunno what's up with the guys lately. :(