Bill,

Thanks v much for the detailed reply, which gives much more info. Can
visualise the little boxes and data flow. With snort being an optional package,
I guess the only way it can work is to use some sort of hooks in the packet
filter for snort inputs and outputs. Thinking streams, but maybe wrong.
My confusion was the snort block list report, which sort of suggested that
block info was snort generated only.

Pfsense is a really great piece of work and it would be good to contribute to
the effort at some stage. In particular, getting pfsense running on old Sun
hardware. There's a lot of it about, it's cheap, good and it's not X86, which
gives added security. Have never worked with or programmed FreeBSD and almost
nil experience of interpreted languages, but that could be fixed. Have plenty
of old Sun hardware to contribute if anyone is interested in starting a project
and can provide support on hardware related issues..

I guess the first thing to do is to try a FreeBSD install. Debian runs fine
and installed just about out of the box on a V240 class machine, but no idea
how good or stable is the support for FreeBSD on Sparc…

Chris

@t3rmin:

Great! Many thanks @bmeeks and @ermal!

Yep.  Approved and merged.  The pfSense guys have been really busy the last few weeks, and that's the reason it took a bit longer to approve the Pull Request.  I will be posting a new thread in the Packages sub-forum with the release notes.

UPDATE:  the release notes are in this thread – http://forum.pfsense.org/index.php/topic,68884.0.html

Bill

IIRC, it extract ip from lines without coments. You can try to check applied list on diagnostic-> tables.

Current status is:

antivirus is still not finished

gssapi libs from freebsd are still need to run squid(you can get it from any 8.3 freebsd or from my repo)

There is something with squid compilation on freebsd with IPV6 that does not listen on configured port if pfsense is not configured with ipv6 option enabled

I have not tested this package with squidguard yet but they may work together.

ssl filtering is working fine

If you want, you can donate/contribute with it to speed up the -dev drop from this package.

@turker:

I got this error,  what does it mean?
Thanks.

pfsense 2.1 x64

That would indicate that at the instant the Snort binary's output plugin attempted to call the API function to insert an IP address into the snort2c table in the packet filter engine, the engine process was not there or not where the output plugin expected it to be.  The event immediately preceding the error also gives me a clue.  It says the check_reload_status() function in pfSense is reloading the firewall filter.  That may temporarily stop and restart the processes the Snort binary plugin was trying to contact in order to insert the IP address for blocking.

Bill

@Ramosel:

So do you have both squid and HAVP setup as transparent proxies? 
If so, you should set HAVP as a "parent for squid"

That said, this is not how HAVP blocking will alert you.
If HAVP is working you should get a blue and orange graphic screen showing that HAVP has blocked a file.
You can test this safely with these downloads at EIECAR

http://www.eicar.org/85-0-Download.html

Correct, that is how squid and HAVP are setup - HAVP as "parent for squid" and I do/did get the blue and orange graphic screen stating HAVP blocking.

Thx.

The size of the USB stick doesn't matter as much as the size of the CF image that was loaded upon it. For example, if you load a 1GB CF image on an 8GB stick, it would still only have a 512MB OS slice to work with.

You might be better off going to 2.1 if you need Avahi. The PBI install mechanism is much simpler/safer than what 2.0.x used.

I have to agree. I LOVE vnstat2, and if it wasn't for the hardware I was using, I wouldn't have went to 2.1 because of vnstat2 not working with it. I greatly miss it, and would really like to have it back as a supported package (without all of the manual hacks).

I had this same issue and found a solution.

I first got freshclam to run by creating /var/log/clamav and /var/db/clamav directories and using chown -R clamav clamav to change the ownership.

I noticed that /usr/local/etc/rc.d/clamav-clamd was empty.  I copied the contents from /usr/pbi/dansguardian-amd64/etc/rc.d/clamav-clamd into it.  I then created a new file /usr/local/etc/rc.d/clamav-freshclam and copied the contents of /usr/pbi/dansguardian-amd64/etc/rc.d/clamav-freshclam into it.

After a reboot the clamav service started and I was able to use DG to filter web traffic with clamav enabled.

2.7.9 pkg v.4.3.3

Is this a known problem?

I was a bit hesitant to try other versions as I've tweaked the web interface somewhat as shown HERE.

Thanks,

Steve

Remember that dynamic pages(fb, twitter, yt) won't punch the cache, if u can setup calamaris, squid-cache manager and compare with lightsquid reports.

3GB won't say nothing, squid won't warranty that will use those 3GB at the moment.

If u want to see the cache at full speed, give little memory to squid 128MB, restart, full day running and watch your reports, I cannot nothing about how lightsquid works, I don't used.

@periko:

If u see the web page slow, try enable "resolv dns v4" check box, some times this cause issues.

Is enable?

This solved my issues, thank you very much!

@dale1957:

Hi,

I'm fairly new to PFSense.  We have several routes & gateways setup on our PFSense boxes.  I'm looking for a package that will send me an Email notification when one of the routes/gateways starts loosing packets or goes offline completely.  As I said I'm still learning but I have not been able to find anything built into the program to do this.

Thank in advance for your help.

Dale

Dale,

If you go to System -> Advance -> Notifications.

You can setup your notifications there.
pfsense will start emailing you when it starts encountering loss on the gateways. This is a built in feature of pfsense.

Well now i have tons of IPs listed under blocked so something i did worked

Thanks for the tips!  I will set mine up like that and it should make it easier for me to track down issues.

@LawrenceIII:

hey Bill, that was it!  you were correct about the 0.0.0.0, and also the wrong DNS IP (that was a typo)  :-[
i remember putting in that 0.0.0.0 one day, and forgot all about  it.
Thank you so much for straightening me out, that was driving me crazy for weeks.

Lawrence
[/quote]

You're welcome.  Glad you are up and running.

Bill