I also had this issue and tracked it down to a user rule that had a description beginning with the string "carp" - it appears that $matches['carp'] is used elsewhere before pfblockNG and contains an array of data related to carp interfaces

Two possible fixes:-

find the rule description that begins with the term "carp" and change it adjust the code to use a variable name other than $matches

Enjoy,
N

@jimp:

For manually installing FreeBSD packages, see here: https://doc.pfsense.org/index.php/Installing_FreeBSD_Packages

But that won't help lightsquid. Don't do that. Follow this: https://doc.pfsense.org/index.php/Lightsquid_Troubleshooting

If I do this, I will lose all the logs stored. The problem is with the graph it does not generate.

Hello,

same issue here please fix :)

Thanks,

Hello,

I found the solution.

It was a driver problem of my TFTP Lan Card with pfsense 2.2

I changed my card and now everything is ok.

Best Regards.
Myke.

Well, I made this work. If you are running into this issue, you can probably fix it this way, but I'm no expert at regex.

Here is the code that is in the syslog-ng package now, found in /usr/local/pkg/syslog-ng.inc:

preg_match("/\bfile\b\(['\"]([^'\"]*)['\"]/", base64_decode($object['objectparameters']), $match);

That is supposed to fix the "encrypting the keyfile" behavior, but it doesn't. This is at line 238 according to the redmine page here https://redmine.pfsense.org/projects/pfsense-packages/repository/revisions/c030cf2781c7bbef197db6f07facef35b6856c8e/diff

In order to get this thing to STOP encrypting the keyfile, I changed line 238 to this:

preg_match("/[^-]\bfile\b\(['\"]([^'\"]*)['\"]/", base64_decode($object['objectparameters']), $match);

Once I change this and re-saved, with no changes, my custom Destination object in syslog-ng (restarting the syslog-ng service does NOT make this change take effect), the /usr/local/etc/logrotate.conf no longer includes the key file, but it DOES still include the syslog-ng log files.

One other thing - while youa re editing the /usr/local/pkg/syslog-ng.inc file, chenage the line

$conf .= "@version:3.6\n";

to

$conf .= "@version:3.5\n";

otherwise the syslog-ng service will not start.

I would also suggest reading this thread:

https://forum.pfsense.org/index.php?topic=90092.msg498849#msg498849

Best to create a "permit inbound" alias for CA and US. Then manually create a firewall rule using this alias and using the IP/ports of your mail server.

Not recommended to put all countries except a few in blacklists as pfSense is a stateful firewall by design.

I'd like to add if a change is made to a group in AD, once Dansguardian updates, the changes are reflected on the 'Users' tab, but the actual file is not changed.  You have to click on the 'Users' tab save button to apply.

Anybody got a quick fix for this?

Go to Diagnostics->Edit File
Browse and Load /usr/local/pkg/bind.inc
Go towards the end of the file and add -4 as shown
Save the file and go to the BIND Server page and click Save to apply the change

function bind_write_rcfile() {         $rc = array();         $BIND_LOCALBASE = "/usr/local";         $rc['file'] = 'named.sh';         $rc['start'] = <<<eod<br>if [ -z "`ps auxw | grep "[n]amed -4 -c /etc/namedb/named.conf"|awk '{print $2}'`" ];then         {$BIND_LOCALBASE}/sbin/named -4 -c /etc/namedb/named.conf -u bind -t /cf/named/ fi EOD;         $rc['stop'] = <<<eod<br>killall -9 named 2>/dev/null sleep 2 EOD;         $rc['restart'] = <<<eod<br>if [ -z "`ps auxw | grep "[n]amed -4 -c /etc/namedb/named.conf"|awk '{print $2}'`" ];then         {$BIND_LOCALBASE}/sbin/named -4 -c /etc/namedb/named.conf -u bind -t /cf/named/         else killall -9 named 2>/dev/null         sleep 3         {$BIND_LOCALBASE}/sbin/named -4 -c /etc/namedb/named.conf -u bind -t /cf/named/         fi</eod<br></eod<br></eod<br>

I'm very sorry I haven't responded, I didn't get alerted to the thread being updated.

I am embarrassed to be reminded of this as I did realise I was being less than observant when I first looked in to it, pfBlocker itself can use multiple lists per alias. To achieve what I described I now do the following - please note I am describing this from memory and I have just started using pfblockerNG instead so please don't…. assume I am correct (!)

In pfBlocker:

Create a new item "Alias_Always_Block"
Add the IP blocklists as required to this - I had missed the fact I could simply click "+" to add multiple lists.
Set as an Alias rather than a permit/deny.

–My "Always Block" contains only a Pe**phile list.

Create a new item "Alias_Mostly_Block"
Add the IP blocklists as required to this.
Set as an Alias rather than a permit/deny.

--My "Mostly Block" contains for example malware and ad lists.

In the pfSense Aliases (Firewall > Aliases> URLs) create an Alias "URLs_pfBlocker_Override" and add the URLs you wish to whitelist.

Now create your firewall rules using aliases in this order, relative to your other rules (I use floating rules).

Block "Alias_Always_Block"

Allow "URLs_pfBlocker_Override"

Block "Alias_Mostly_Block"

Whenever something breaks, add "www.example.com" to the "URLs_pfBlocker_Override" Alias - remember to refresh your rules and wait.

You should now find you never see traffic to Pe**philes, and you may find certain websites get blocked because they are hosted by providers whose entire range has been added to a malware or ad list for some bad apples spoiling the bunch. Manually add them to your override URLs to allow for this.

The above is overly simplified as my actual rules block everything, the URLs override rule only allows HTTP/HTTPS ports, and other allow rules I haven't described get the rest of my legitimate traffic working. I highly recommend reading this thread, I am only half way through it myself but it will explain in detail what I have glossed over here - https://forum.pfsense.org/index.php?topic=78062.0

http://www.asterisk.org/downloads/asterisknow

@marcelloc:

Check the sample you copied. That is between two

Yes thank you..attention to detail such an easy thing to miss.

Thanks its working now.

Are the commands for lightsquid or sarg?

Sorry, I'm an idiot.  I grabbed the wrong section from my pfSense cheat sheet.  Try this for Lightsquid:

ln -s /usr/pbi/lightsquid-amd64/local/www/lightsquid /usr/local/www/lightsquid ln -s /usr/pbi/lightsquid-amd64/local/etc/lightsquid /usr/local/etc/lightsquid pkg install perl5 pkg install p5-gd /usr/bin/perl /usr/pbi/lightsquid-amd64/www/lightsquid/lightparser.pl today

This works for getting Lightsquid working with 2.1.5.  I haven't played much with 2.2 packages for a few weeks now so I have no idea if this works with the latest stuff.