PC1                                                 PC2                                                     PFSENSE                           PC3 ip 20.50.10.106/16  <–----> ip2 20.50.10.105/16--|--ip1 10.50.0.1/16<----->wan ip 10.50.0.2/16--|--opt1 20.50.0.1/16 <-------> ip 20.50.0.3/16    gw 20.50.10.105                                                 gw 10.50.0.2                       gw 10.50.0.1   |      gw 20.50.0.3                     gw 20.50.0.1                                                                                                                                        |                                                                                                                                        |                                                                                                                             lan ip 192.168.233.2/24                                                                                                                                       |                                                                                                                                       |                                                                                                                                       |                                                                                                                                 PC4                                                                                                                        ip 192.168.233.1/24                                                                                                                           gw 192.168.233.2

Not sure we can do that going forward.  apinger will only accept one target.

After upgrading to 1.2.1-RC3 on Monday, and letting it run a few days, the problem appears to be gone. USER    PID %CPU %MEM  VSZ  RSS  TT  STAT STARTED      TIME COMMAND root    386  0.0  0.2  5696  1960 con- S    Mon12PM  0:05.94 /usr/sbin/tcpdump -s 256 -v -l -n -e -ttt I'm still not sure what may have caused the symptoms I saw in my original post. Something sure made tcpdump chew through a lot of CPU time and memory in less than a week, but as long as it doesn't happen again it was probably a fluke or a side effect of the testing I had done.

System->Packages->wident perhaps?

It's a while since I thought about this one. I've been running 1.2.1-RCx with SLBD (3 failover groups) for weeks now on a quad core xeon rackmount (DL140). I've not seen SLBD grab 100% of a core for a long time now. And stability seems good. One thing I do see is some mis-reporting in the GUI. A line may show "Offline" whereas the logs show that line as up ie. "marking service UP" was the most recent log for that line. I consistently see this on the primary firewall (SMB) but not on the backup firewall (uniprocessor). The backup firewall uses the same synched-over settings and correctly shows all the lines as "online". Nick.

The default is checked.

1.2.1-RC3 built on Mon Dec 15 12:05:39 EST 2008

This area of the forum is to report problems.  Not to educate you on everything you do not know. I kindly request that you stop posting general question to this area of the forum (1.2.1-RC Snapshot Feedback and Problems).  Thank you.

a small workaround was in the dns forwarder area i put 10.0.0.1 -> the hostname of my choice

No, a graph.  Please do not mix issues in the same post.  Thanks.

Sorry, cannot reproduce this one.

I agree - sort of.  It should at least prompt the user that a reboot might be necessary to complete the change.  This has been an issue for some time now, though I'm not sure it affects everyone, though I have experienced it many times.

Actually, there are still some entries that cause blank or malformatted lines in the dashboard log viewer. I copied more of the logic from diag_logs_filter.php into log.inc, and am seeing even better results. Could still probably use more work, but It Works For Me log.inc.txt

rc3 fixed it

rc3 fixed it

Just fixed.  Will appear in 1.2.1-FINAL or a future snapshot.

You can virtualize pfSense pretty well on vmware ESX. There are a number of installations and carp clusters working on ESX. Paravirtualization is something entirely different. If you just want to run it as a vm it'll work fine.