"if I am not completly wrong your cron job updates the blacklist every 10min" : i know, it was just for test with update blacklist.
First time, when i installed pfsense 2.1 , i choose squid3 et squidguard for squid3 but i had many problemes (impossible reload of squid or squidguard for example). I installed and uninstalled them , reinstalled but i always had problems with them. This the reason i chose v2.02 and upgrade v2.1.

I don't understand why squidGuard_blacklist_update.sh don't work completely with my version 2.02 and work with 2.1 without I do anything more

best regards

Bill thanks for your help.

Yes I've checked the configuration file too. But now I think it's my bad. Sorry. Snort is running on WAN and DMZ interface. All my playing around with the FTP preprocessor setting I have done on the WAN interface, not thinking about that maybe I have to do this also on the DMZ interface. The Block list didn't gave me any infromation from which interface the block was set.

I have now disables on both interfaces the FTP preprocessor and insert the custum setting on the bottom of the first side ON BOTH interfaces. Now I'm waiting for the result and will inform you shortly. Sorry again - my bad.

best regards
Frank

I believe I ended up finding a solution.  I found a third-party bash script called check_carp_if that checks output of ifconfig to see if the VIPs are set as master or backup.  I added it to the /usr/pbi/nrpe-i386/libexec/nagios folder, made a couple of modifications to it to fix some broken paths, and voila, I now have an nrpe check that tells me for each box whether the VIPs are master/slave.

I would have liked for this to be a module that was already built-in to the NRPE package so that I could minimize what needs to be done if I have to restore from backups to a new pfsense box, but c'est la vie.

mmh, sorry. Our firewalls are running weeks/months without reboot since 2.1 is out and some reconfiguring is done…
So I must see when I can help with more debugging... Do you have special logs for such case?

I checked for ospf / zebra entries and found only these ones:

/var/log/routing.log:
Dec  4 12:53:55 fw2 ospfd[16271]: nsm_change_state(192.168.6.2, Loading -> Full): scheduling new router-LSA origination
Dec  4 12:53:56 fw2 ospfd[16271]: DR-Election[1st]: Backup 192.168.6.12
Dec  4 12:53:56 fw2 ospfd[16271]: DR-Election[1st]: DR    192.168.6.2
Dec  8 11:17:15 fw2 zebra[23085]: Zebra 0.99.22.3 starting: vty@2601
Dec  8 11:17:15 fw2 ospfd[23308]: ASBR[Status:1]: Update
Dec  8 11:17:15 fw2 ospfd[23308]: ASBR[Status:2]: Update
Dec  8 11:17:15 fw2 ospfd[23308]: ASBR[Status:2]: Already ASBR
Dec  8 11:17:15 fw2 ospfd[23382]: OSPFd 0.99.22.3 starting: vty@2604
Dec  8 11:17:15 fw2 zebra[23085]: client 17 says hello and bids fair to announce only ospf routes

Firewall was rebootet

/var/log/system.log:
Dec  8 11:05:13 fw2 syslogd: kernel boot file is /boot/kernel/kernel
Dec  8 11:05:13 fw2 syslogd: sendto: Network is unreachable
…
Dec  8 11:05:14 fw2 kernel: ifa_del_loopback_route: deletion failed
Dec  8 11:05:14 fw2 kernel: ifa_add_loopback_route: insertion failed
... many of such del/add failures...
...
Dec  8 11:05:27 fw2 php: rc.start_packages: Restarting/Starting all packages.
Dec  8 11:05:31 fw2 php: rc.start_packages: XML error: SYSTEM or PUBLIC, the URI is missing at line 1 in /usr/local/pkg/iftop.xml
Dec  8 11:05:31 fw2 php: rc.start_packages: XML error: SYSTEM or PUBLIC, the URI is missing at line 1 in /usr/local/pkg/iftop.xml
Dec  8 11:05:33 fw2 php: rc.start_packages: XML error: SYSTEM or PUBLIC, the URI is missing at line 1 in /usr/local/pkg/ipmitool.xml
Dec  8 11:05:33 fw2 php: rc.start_packages: XML error: SYSTEM or PUBLIC, the URI is missing at line 1 in /usr/local/pkg/ipmitool.xml
Dec  8 11:05:37 fw2 php: rc.start_packages: [Squid] - Squid_resync function call pr: bp:1 rpc:no
Dec  8 11:05:38 fw2 check_reload_status: updating dyndns WAN_TDSLGW
Dec  8 11:05:38 fw2 check_reload_status: Restarting ipsec tunnels
Dec  8 11:05:38 fw2 check_reload_status: Restarting OpenVPN tunnels/interfaces
Dec  8 11:05:38 fw2 check_reload_status: Reloading filter
Dec  8 11:05:38 fw2 check_reload_status: updating dyndns IPSec
Dec  8 11:05:38 fw2 check_reload_status: Restarting OpenVPN tunnels/interfaces
…
Dec  8 11:11:40 fw2 php: rc.start_packages: Restarting/Starting all packages.
Dec  8 11:11:44 fw2 php: rc.start_packages: XML error: SYSTEM or PUBLIC, the URI is missing at line 1 in /usr/local/pkg/iftop.xml
Dec  8 11:11:44 fw2 php: rc.start_packages: XML error: SYSTEM or PUBLIC, the URI is missing at line 1 in /usr/local/pkg/iftop.xml
Dec  8 11:11:46 fw2 php: rc.start_packages: XML error: SYSTEM or PUBLIC, the URI is missing at line 1 in /usr/local/pkg/ipmitool.xml
Dec  8 11:11:46 fw2 php: rc.start_packages: XML error: SYSTEM or PUBLIC, the URI is missing at line 1 in /usr/local/pkg/ipmitool.xml
Dec  8 11:11:50 fw2 php: rc.start_packages: [Squid] - Squid_resync function call pr: bp:1 rpc:no
…

Your platform is still "cdrom". If you installed, you didn't eject the CD from the VM or adjust the boot order so that the HDD is first.

@grinderfurax:

is there a tweak to check it ?

It's during install.

Or you can try this by you own risk

1. Boot server with FreeBSD or pfSense livecd
2. enable soft-updates using 'tunefs -n enable /dev/xxxx'
3. run fsck on / partition
4. reboot and check what you get with cmd mount on console/ssh

-> /dev/ad0s1a on / (ufs, local, soft-updates)

@shpokas:

"Problematic" one is fresh install :)

Now I have discovered that symlink to /usr/local/bin/snort is gone  :-[
But that's not all. When I execute /usr/pbi/snort-i386/.sbin/snort, nothing happens. With switches or without, just nothing. Size of the file is the same as on the other machine where snort is working.
Time to reinstall again.
Will be back with update  8)
[/quote]

That really sounds like the PBI package manager is hosed up somehow.  The new 2.1 pfSense uses PBI packages that more or less put each installed package in its own chroot environment.  This way the packages can't interfere with each other's shared libraries and such.  As you have noticed, there should be a working symlink from /usr/local/bin/snort pointing to /usr/pbi/snort-i386/.sbin/snort.  If that symlink won't properly execute the command "snort -V", then that is what is wrong with the update process.  Can also be why Snort won't start properly either.

Bill

@sinikel:

Yeah, I read through all of your other posts.  Would be cool if the devs made a feature to allow us to add that src IP to the firewall rules section..

Again, thanks for all of your help!!!

I might be able to do that from the Snort side by copying some functionality available from the Firewall Log page.  Not sure, as I have not investigated in detail; just thinking off the top of my head.

Of course something like that might have limited usefulness because many times "bad actor host IP addresses" frequently change, so an IP block today may well be worthless tomorrow.  Or worse yet, if it was a dynamically assigned IP and now a "good guy" has it, he will be permanently blocked from your network.  Better in my view to use the automatic 1-hour clearing of Snort-blocked IPs.  You can set this on the Global Settings tab.  Right now, with the random early clearing of the block table, you may not see a true 1-hour interval, though.

Bill

Sorry for the late reply. I've found the bug.
It's fixed on 0.2.1

I'll include it on squi3-dev. Thanks for the feedback.

Post here your config modification.

This way I can try to include on package gui.

Unless there are 5 zeros after a number, no government will bother with it. If tomorrow (or next week, since it's a weekend) pfsense starts selling for a 6 digit number, every single government on the entire planet will write laws requiring its use.
Then there will be the "Security Experts" that studied "Information Systems Security" and took a couple of "Security in an Inter-connected World" seminars. Those insert a not-so-flattering comment here will come along, sign a contract for "Systems Support and Maintenance" and will take 3 years to install a patch. During those years every (as the saying here goes) dog will piss on the systems. Disclaimer: This paragraph has been an actual fact. A well known middle-East ISP, whose name shall not be mentioned, in order to protect the guilty, took 3 years to patch a damned system. In the meantime, every single username and password of every single customer was leaked on the internet. Anyone with a computer that knew how to download an exploit (ie most "hackers") was granted free access to it. Last time I checked, the list is still there.
You can now understand why I sound so angry on these forums (usually) because I have to deal with the "Security Experts" that studied "Information Systems Security" and took a couple of "Security in an Inter-connected World" seminars, daily.
For example last week I called a guy, which I'm sure has 20 years experience in IT. I can actually vouch,without ever talking to him before, that he is the best there is in this country. "Hi, this is ….. you talked with ..... to get a domain transfered. Have you prepared the domain for the transfer?" The 20-years-of-experience guy's response was "I don't need to prepare anything, you just initiate the transfer and I get an email to accept it." My response "no, actually the transfer will fail, unless the domain status is ACTIVE or OK. You can check it with a whois on the domain. Right now it says...clickety-click Registrar-lock. Can you please remove the transfer lock and get back to me?"
A week later, and I'm still waiting for the "Expert" to remove a domain's transfer lock. A process which takes exactly 17 seconds to complete. sigh
Nobody bothers with security or learning something new each day to be honest. Most "Experts" are happy to know how to turn on a system and get on fb and that's it. That actually makes them the very best there is in multiple countries, the geek-elite.
I could go on all day, but it's getting off-topic. My apologies to the OP for going off-topic.

@jdeloach:

Does Snort Block Hosts work?

In Snort Interfaces, Alert settings, I have "Block offenders" checked.  Since I'm still learning my way around PfSense and it's packages, is there some other place that I need to enable something so Snort will block offenders or at least list them under the Block tab?

I have several entries in Alerts but Blocked is always empty.

Couple of things to check.  First, examine the IP addresses of the entries on the Alerts tab and see if they are part of any whitelist.  Snort automatically whitelists any locally-attached IP networks and the WAN interface IP and far-end gateway.  Second, it could be that the hosts are blocked but the "clearing the block table" issue discussed here frequently is removing them before you see them.  This refers to an issue that cropped up in the 2.1 release of pfSense where any thing that causes a reload of the firewall filter clears the Snort block table.  However, as has also been written about here on the Forum many times; clearing the block list is not a huge deal because the offending host will be "re-blocked" when more traffic is observed by Snort.

Bill

@simby:

Hi!

when will you release new v. Snort? :)

It is currently under review by the Core Team developers.  They have been quite busy lately with the firewall code itself I understand, so some of the package reviews have suffered as a result and they are behind.  If you want a preview of what's coming, here is the GitHub link to the Pull Request:  https://github.com/pfsense/pfsense-packages/pull/552.  This updates the Snort binary to 2.9.5.5 and adds a number of additional configuration features for the preprocessors including multi-engine targets.

Bill

As far as I know unser system - advanced there is the possibility to change these locations, isn't it? I am not sure at all.

Thanks phil

Can someone move this post please??

Sorry,

On Squid logging its enable and log rotate, 30d configured.

i'll keep the log rotate on squid empty, and daily reports disabled since my disk is almost full…

Thanks for the help!!!