Under your Proxy Server>Cache Management>Hard Disk Cache System, try selecting null.

null Does not use any storage. Ideal for Embedded/NanoBSD.

I installed freeRADIUS on i386 and amd64 and I did not have such problems.

Perhaps a "Clear package lock", complete deinstallation of freeradius und clearing the config.xml from freeRADIUS entries and the a new installation of freeRADIUS solves the problem.

You can see VRT changes here http://blog.snort.org/, here http://www.snort.org/snort-rules/#rules or here http://www.snort.org/vrt/advisories.xml/

You can see emergingthreats (open & pro) changes here http://www.emergingthreatspro.com/blog/

I am not sure about automating it to actually put it on your pfsense. Most sure way may be just to run pulledpork and sftp them over and restart. At least with pulledpork with enable and disable you can disable CVEs (i..e just disable all CVEs before a certain year if you wanted), rulesets etc. So once you go through the rules you can easily run it. It does output only 1 file for each (normal snort rules and shared object rule file) which I can see as being both good but i find it annoying and a  little less refined, especially in tuning as you could just cat an individual rule file or open it and see what is enabled/disabled (presence or lack of # to comment it out) and then make the adjustment where needed in pulledpork.

Hopefully maintainer of the package will work on the updating so it remembers your changes either from GUI or provides you access to config file for disable, enable rules.

Go to "Target categories" and enter all sites you want to allow/whitelist.

Than go to "Group ACL" and "Common ACL" and chose "allow" or "whitelist" for this target categorie.

Than "General Settings" and "Save" and "apply".

PS: If an URL is in different categories and one categorie is "block" and another is "allow" than the URL will be blocked. "Block" is stronmger than "allow". To solve this problem chose "whitelist". If an URL is one times "blocked" and another time "whitelisted" than "whitelist" ist stronger.

thanks a lot :D I'll try it out and try to get it going.

Sorry if this has been covered multiple times, I can assure you I did many many searches prior to posting this.

The problem isn't squid, it's HAVP.

from: http://forum.pfsense.org/index.php?topic=34199.0

Use the pfsense edit file tool under diagnostics and open this file:  /usr/local/pkg/havp.inc

search for the following line:

Change to:

save and restart HAVP.

You can specify which interfaces Unbound can use to do outbound queries, so if you select both the WAN interfaces then queries will be balanced across the two interfaces.
However if once interface goes down then you will get delays.

So you can try this what Ermal mentioned in this forum post http://forum.pfsense.org/index.php/topic,31125.msg167503.html and see if that works for you. Would be interested to know as i can then update the doc site.

I dont know why but i found my trouble relate with DNS, My clients can not resolved domain name therefore i change to other DNS.

Works, thanks!

@marcelloc:

The location of this file in pfsense is /var/db/postfix/postscreen_cache.db

Postscreen readme says that it's a temporary white list, not persistent.

I pulled what I posted from the README. So, the temporary white like might be persistent if set and will be cleared if not set? Documentation seems to not be clear on that. It might be temporary as in the age thing will remove entries. I cannot test this ATM … but should be something the maintainers of postscreen could clear up.

I have the same problem. It seems to be working perfectly and without any errors, test virus sites are detected and blocked and all functions appear to work. I set it up in transparent mode and have not tried the other proxy modes. After a number of hours it completely kills my internet connection. Stopping havp and the proxy and clearing states not fix the problem. I have to reboot my pfsense and my router.

Any one has any ideas how to troubleshoot this?

Package list:

pfblocker
snort
havp
vnstat

I tried disabling and removing snort and pfblocker but the problem still occurred.

Youtube Video

Made it more useful and submitted it
http://redmine.pfsense.org/issues/2008

tcpdump format was problematic and doesnt add much but not having to run snort to interpret the dump would be nice. Cant get snort to dump only alert packets in binary (tcpdump) format. It wants to dump the whole world or not at all.

Not sure how to make optional on alert type beyond hard coding a list or adding a checkbox to every rule or category.

No comment for now :)

Why the hell is OpenDNS blocking Snort.org of all places? Does this mean "all their clients" networks are not able to reach the SNORT.org VRT updates?

Same symptom here, Remove and Install instead or Reinstall.

http://forum.pfsense.org/index.php/topic,41533.msg222007.html#new

OK. Thank you! I will wait.

Best regards

Kostas