friend
succeeded in installing the codec?

Thank!

Do you have a backup you can try to restore from?

System -> Firmware -> Restore Full Backup
or
Diagnostics -> Backup/Restore

Hello again  :)

I've just improved to the procedure for installing Finch on pfSense. Now more resilient to upgrading of the pfSense host system. Before these changes, the Finch boot scripts could be wiped away after pfSense upgrade.

Now, the only manual thing a user needs to do after upgrading pfSense, is restore their "fstab" file from a Backup. But it's very easy and full instructions are given.

All new installation procedure is documented on Finch's website:

http://dreamcat4.github.io/finch/install/

Other improvements:

Better handling of admin user accounts.

The presence of a temporary file "$finch_realpath/var/db/finch/installing…" now allows a simple way to query Finch's installation progress (i.e. "not installed, installing, installed"). (Useful for pfSense pkg makers).

@bmeeks:

@magedtab:

I tried to add snortsam to pfsense .

snortsam 2.7 failed in installation
i need the steps to install snortsam on pfsense

thank you friends

I'm pretty sure snortsam is not supported on pfSense, and the package has not been updated for quite a long time now.  So far as I know, the original creator/maintainer no longer visits the forums here.

Bill

@firefox:

I understand that they both IDS/IPS Daemon
What is the difference between them ?

Nothing really except two different vendors.  Snort is an open-source version of the IDS engine used by Sourcefire.  Suricata is a totally open-source effort partially funded by the U.S. Government and some private companies.  Well, technically Suricata is funded by the Open Information Security Foundation, but they get funding from the U.S. Department of Homeland Security and others.  Here is a link describing Suricata:  https://www.openinfosecfoundation.org/index.php/download-suricata.  Suricata is multi-threaded and should theoretically scale better in very high throughput networks.  However, extensive testing by the Snort guys and some independents shows there really is not much difference in the packet throughput in real-world networks between Snort and Suricata.

In the end it comes down to personal preference.  Currently Suricata captures and logs a little bit more "context" around alerts, but Snort is catching up in this area.

Bill

@wq6n:

pfSense 2.1.3
Snort 2.9.6
Barnyard2 ?
Stunnel 4.43.0

Unified2 feed from Snort remains constant on all sensors

First off, thank you for such a great software security suite of tools.

Pointing several Snort IDS sensors to a remote MYSQL server using a common port (lets call it TCP 3333). Created the Stunnel cert at the remote server using:

openssl req -new -x509 -days 365 -nodes -config stunnel.cnf -out stunnel.pem -keyout stunnel.pem

I did not create the Diffie-Hellman 'openssl gendh 512 >> stunnel.pem' as I did not see anything in the pfSense Barnyard2 configuration that suggested integration. However the other native Stunnel relationships do support the DH key.

All Stunnel connections are in place and operational to the remote MYSQL server. I did have to go into the working pfSense Barnyard2.conf and append [port = 3333] to the MYSQL line. The remote Stunnel takes the incoming port TCP 3333 feeds and port forwards the data streams to the local TCP 3306 MYSQL listener.

Restarting the Snort interface everything comes up and the remote end does see the incoming connection from the pfSense Snort application. My challenge is that Barnyard2 stops working and the connection is closed after a while. The Native feeds from the other remote Snort senors remain functional.

Any ideas on keeping the Barnyard2 application running?

Do you see any Barnyard2 related messages in the system log on the pfSense side?  The latest Barnyard2 binary seems to have a problem with multiple instances concurrently accessing the same SQL DB.  This usually manifests itself with a "duplicate key" error written to the pfSense system log.

The fix, if you have this error, is to choose only one Barnyard2 instance to update the References table.  There is a checkbox to handle this on the BARNYARD tab in Snort.

Bill

thank you rjcrowder for your time.

I find the solution, the sites i got the massage was host in my vpn network and i should check the option "Disable DNS Rebinding Checks" at menu System->Advanced->Admin Access

not really an answer but different developers built the packages. That is why Squid 2 doesn't have the real-time logging feature

Final Update & Closing:

My settings:

LDAP base domain: cn=Users,dc=ads,dc=example,dc=local LDAP username DN attribute: samAccountName LDAP search filter: (&(memberOf=CN=InternetUsers,CN=Users,DC=ads,DC=example,DC=local)(sAMAccountName=%s))

AD structure:
Container: Users > squid, test, administrator
Other Containers (OU):

OU Main
            –- OU1 --- User1
            --- OU2 --- User2

All these users have been added to security group (global) named InternetUsers and this group resides in the "Users" container.

I am able to verify three users - test, squid, and administrator which are in Users container; but I am not able to authenticate User1 and User2 which are placed elsewhere in AD even though they are members of InternetUsers group.

I conclude that the search is limited to one level only. So either I have to find a way to provide multiple Base Domain values, or find a way to make the search query recursive. Both would perhaps require me to directly edit the .inc file. I am not planning to do it and will leave it at that. I would rather create local users in Squid and now focus on learning SquidGuard.

Thanks

this is solved. please close. thanks to all

Never mind, I figured out the problem… it was Snort getting in the way.

I had disabled Snort as part of my routine checks; but forgot to clear the blocks it had put into place. ::)

Once the blocks were cleared and with Snort temporarily disabled Lightsquid installed just fine. :)

Every-time i reboot Pfsense the vhost configuration file is deleted, and must go to vhost service page and save the previous config to recreate the config file.

Pfsense 2.1.3 i386

https://doc.pfsense.org/index.php/Pbi_add:_Invalid_file_for_usercheck

I'm not sure I understand what you are trying to accomplish… For each group in Dansguardian (you can only create 3) you can specify multiple things (and I'm sure I will miss some).
1.) What sites are blocked based on a blacklist (plus allows via a whitelist) for URL's and sites
2.) PIC's based blocking
3.) Block rules based on weighted phrases in the content
4.) Grey list of sites that are allowed as long as they don't violate phrase blocking
5.) URL rewrite rules
6.) Content rewrite rules
7.) Blocking timeframes

You can assign users to groups either by using an authentication mechanism (there are several) or by IP address.

@marcelloc you're a genius!

it worked!
fast response too. :)
thanks much!

Hello joako,

When you goto Snort and edit the Interface where you added the suppression, look at the Settings TAB, and find

"Choose a suppression or filtering file if desired"

The file listed here, should be the suppression list for the interface.

There is a "View List" button, if you click that, does it show you the newly added Suppression's?