I think we finally tracked this issue down to some folks leaving the Package Install screen a little too quickly.  It can take Snort a long time to start up if lots of rules are enabled and/or the CPU is not super fast.  You will see a message in the install box that says something like "…package successfully installed..." when the install is actually finished.  Just because you see it say that it starting Snort, that does not mean the install is complete yet.  After Snort starts, control is returned to the pfSense package manager code, and that code does the final steps of the install which includes adding the menu links under SERVICES.  So if you exit the installer screen too early, the PHP process terminates and that final step performed by the package manager code never happens.  This leads to the Snort option missing under the SERVICES menu.

Bill

@scottd:

OK, managed to figure out why Blacklist did not load.  I had a "partial" list that Firefox didn't warn me aborted during the download process.  I found that out by trying to open the list, WinZip tried to gunzip it and failed, reported premature EOF.  I downloaded again from:

http://urlblacklist.com/?sec=download

and I had to try a couple times to be sure this time I got a complete file.  Don't know why that times out sometimes, busy I guess.

But, I still have my 2nd problem which is that our VPN won't work while using DansGuardian.  Anybody have any ideas on that?

Do you have a subscription? Is so, let them know… If not, then its their way of of saying you need a subscription  ::)

Yes but if you give the VPN the same internal IP as your own, then routing wont work afaik.

Thats why I wanted you to give your local subnet a different IP range. Then we can exclude the routing range.

Yeah, sure. Point taken, although I'd be mostly filtering myself, anyway, if I wanted to restrict the users…

More interested in doing things like ad filtering, or detecting/blocking various phone-home type things, because open ports can be abused, monitoring whether the ports are actually used by the protocols/apps for which they were opened would be my main concern.
I neither trust ISPs nor closed-source software vendors  further than I can throw them (which given their abstract nature is a distance of zero)...

Read again cache.log.  All you need to fix is there.

Thanks for trying to help me  ;D

Just wasted 3 hours of my life trying to get it to work. Was on the brink of a nervous break down, as reinstalling gives huge pain in the butt when having to export certificates for use in Windows and Android, let alone, once you have these certificates exported, putting them on each gadget and laptop, and customizing these again.

Logging was on but showed nothing at all. Radius test user (wiki) on 127.0.0.1 worked. Rebooted switches, WAP's, pfSense: nothing. Reinstalled FreeRadius: nothing.

Then I discovered the obvious bug:

This was the shared secret:

^4540lkkgkf_8(`!$,.;/"

Replaced that with:

1234

And everything worked again…

The weird thing is: that first shared secret was exactly the same as the one it was before I reinstalled pfSense; I meticulously made sure not to make any errors there.

Thanks again for your kind help  ;D

@SunStroke:

In that tutorial HAVP was set as transparent. If you have squid installed you would prefer to set HAVP as "Parent for Squid".

"Transparent" is used for HAVP in standalone mode. I use that mode for HAVP without Squid.

Ok yes that fixed it! Is that setting ok with squiguard running as well?

Thanks very much for the help - much appreciated!

Your config makes sense - I agree, a bit odd about the server, but glad it works for you. I think my issue is related to links missing in v2.2 … :(.

Thanks again.

Changed to no repliant DNS server and speed has improved.

Thx for the advise!

@ghkrauss:

I have Snort running on Pfsense 2.2RC. I would like guidance on which alerts I can safely add to the suppression list. It is unclear what the meaning of "Unknown" vs. :not suspicious". I am trying to configure the Snort system for the longer term. The Pfsense platform is an Xeon E-3 with 16 GB and a 10K rpm hard drive.

There is a thread here with "Master Suppress List" in the title.  Do a search and it should pop up.  It is several pages worth of posts from experienced users here.

Edit:  found the link for you:  https://forum.pfsense.org/index.php?topic=56267.0

Bill

Hi jbiss_ca,

So you don't see session and byte counters on the frontend increase at all? That would mean the connection never arrived at haproxy.

Do you have 1:1 natting or a portforward configured on pfSense for the wan-ip? Any floating rules / traffic shaping / other packages ?

Is there a lot of traffic or high cpu usage on pfSense ? It could be worth trying to make a tcpdump of the traffic to see if a incoming connection is answered. tcpdump can be started on a ssh/console with a command like this where you put the correct ip, and the interface name for em0:

tcpdump -i em0 "host 1.2.3.4 && port 80"

The TCP handshake go's like this normally: Request connection[ S] , Accept connection[ S.] , Traffic[ .] , that would be the first 3 packets..

As for logging to '/var/run/log' that sadly doesn't do much.. It would provide more information if you log it to a actual syslog server. Also enable the 'Detailed logging', every connection handled by haproxy should show up in those logs.

The roundrobbin selection shouldnt affect anything if only 1 server is available..

Hope some of it helps..

https://forum.pfsense.org/index.php?topic=6.msg472384#msg472384

I got it running quite simple but not able to make a package for it yet.  I never made one and don't have any setup to do it.

I hope someone does make a package for it.  It is quite simple to get running just copy files and run the php index file.  To get more just edit the config file some and maybe install a module or two for more functions

@gdelong:

Did anyone ever figure out a solution to this?

Not I, nope :(

-Jamie M.

I guess the package is not fully transferred to 2.2 yet.

@wiz561:

@bmeeks:

If you have Snort on multiple interfaces, the Service Watchdog package cannot distinguish each individual interface as the separate Snort service instance it is, so it will not accurately watch all the instances.

Thanks for posting this as I came here to ask the same question.  I'm getting tired of snort not running for some unknown reason every now and then.  I do run snort on multiple interfaces (wan and internal lan).  Do you have any suggestions on how I can accomplish this, with two interfaces?  I'm mostly concerned with the WAN interface, can I tell the watchdog service to just concentrate on that instance?

Unfortunately the Service Watchdog package cannot distinguish between the Snort interfaces.  It will simply "pgrep" for "snort", and if it finds a running instance it will be happy.  That instance may not be the one that is stopped.  For example, if WAN stops but LAN is running, then the "pgrep snort" command will find the single running instance and be "happy" when it really should be "not happy".

I tried for several weeks earlier this year to find a way around that, but there are some internal limitations with the current pfSense architecture with regards to how packages are sensed and auto-started by the system.  Those limitations cause the issues with something like the Service Watchdog package.

I have considered something similar to Service Watchdog but customized into the Snort package itself.  I have not given that much priority.  I can revisit that idea in a future update.

Bill

Did you find an answer to this or a workaround?

Hi Bill! Many thanx for the extended service, after the tird uninstall-reinstall it finally works! :-D

Had a nice fondue and some decent white wine in the meantime and that apparently helped…

Cheers and nice party everybody

chemlud

I'm hoping marcelloc will notice this thread.

Not that I think it's a really a bug.  There are so many config options in postfix that I'm not surprised he would have had to make some tough choices about how to manage certain things through the GUI.

I suspect any save through the GUI or reinstall of the package would wipe out the change.

i3s belong in the "no-no"* category, so no testing for them.

the flawed "if it aint broken don't fix it/production"**
** machines that are not in use in The Company, but installed by The Company for clients***
*** if those machines were ours, they would be long broken by now  ;D

If we can't get a build working on those p4s, then a hardware upgrade is due. I know what it takes to support old/rarely used hardware/software, so I'm not adding to that if I can help it. Besides, I already got 5 years out of a €100 box (including the 2x dual pci-x intels), what else could I ask for? Oh yea, a pair of them in CARP ;D

If only supermicro stopped pushing out motherboards (guess what motherboards those p4s are running on)… This http://www.supermicro.com.tw/products/motherboard/Atom/X10/A1SRM-LN7F-2758.cfm makes me want to shout "shut up and take my money already!"

Since I always work using "the worst case scenario", I'll start planning for the upgrade soon.