I updated to the next release and that particular little nasty went away all on its own.  Maybe a file was corrupted and was overwritten during updates?  Maybe someone (throwing nasty look over the cubicle wall) was "looking" and slipped?  The world may never know. Thanks for your reply!! Scott

Do something like this: vi /cf/conf/config.xml rm /tmp/config.cache /etc/rc.filter_configure_sync

I seem to have found a possible solution.  It seems that by having two hard drives connected and using teh on board RAID controller was causing the issue.  I simply removed the second hard drive and the command ran fine.  Thanks.

This is not supported. If you want to do something like that you will have to find your own way (livecd with packages). There have been discussion earlier why this is not a good idea (search forum and mailinglist).

OK, so j0emv beat me to it. http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/110407 I wish I knew enough about BSD to just fix the darned thing.  I hate waiting.  That little Seagate microdrive is perfect and I can't use it!

Please use the sanpshot from 23.03 with caution, at the time a feature called "schedules" will be implemented! Use the snapshot from 15.03.

Setup a remote syslog server then tell pfSense to send the logs to the other server. Currently there are no other methods of saving the logs locally but we will be addressing this soon.

I think you can watch to timeline : http://cvstrac.pfsense.com/timeline

There is a known problem with using pppoe interfaces in pools. It's not fixed yet.

@egarnel: The 7206vxr could sit behind the pfsense box and perform traffic-shaping and/or policing before it gets to the pfsense box internal networks –---> 7206 ------- pfsense [nat] –- internet We do something similar we have 3845 routers running as a glbp pair that shape traffic, police protocols, perform ip sla checks and then do policy based routing to send particular traffic out either of the pfsense servers or firewalls or nat routers - based on priority & availability. You can use class-maps & service polices to give certain protocols more or less bandwith, qos, etc...  For example:  We choke down bandwidth hogs to a trickle before they even reach the pfsense servers The 7206 is a bad ass router that can do a lot of stuff as above, as well as vlan support & firewalling. We have one here in our shop, it just cranks right along I have an ATM connection to ISP. So I can't put anything in front of my router because of hardware requirements. But your suggestion seems smart. But I think I will work on Hoba's suggestion.

ok thanks for your quick replies - I'll keep on experimenting :-) Update on problem: If I choose 99 in the menu - but from a ssh session as opposed from the "console" (keyboard/VGA screen) the Ncurses GUI works :-) If invoked from the "console" the system freezes - only possible option is the hw-reset button - it seems that the problem is related to the VGA shared-memory…

This is why we advocate reinstalling.  We didnt handle every update case for betas.

Hello, now it rocks! We have changed the HDD from Seagate Barracuda 7200.9 (80 GB) to Samsung SP4011N (40 GB PATA). We did not change anything in the BIOS from Defaults. I loaded the newest RELENG Build and all runs fine. The Seagate 7200.9 SATA and PATA runs definitely not with the Intel Board E7221 and Pfsense. You need to use another HDD. Greetings Heiko

@Darth_Potato: My local time is 8:54PM now. Also I have and different measures in RRD Graphs - on WAN in 114.64MB, but on LAN out 129.43MB :o Maybe this is linked with time-bugs Different Traffic between interfaces is normal. You have some traffic at WAN for example that will be blocked but that is seen from your WAN interface. Also some broadcasts that are seen at the LAN interface won't be routed out the WAN though they hit your LAN interface. Btw, this ACPI-fast is the setting that works on my IBM eserver x330 server. You probably don't have this counter at your system but maybe others. My server offers 3 timecounters but this is the one that I found out to work ok. Check what counters are available at your system and try all of them.

We covered it in the other thread.  Locking this one.

@sullrich: @Emab: Just upgrade to the leatest snapshot: Now the web interface work correctly Duing the boot, I can read via serial console these last line: ....... Starting OpenNTP time client...done. Starting CRON... done. Syncing packages: XML error: not well-formed (invalid token) at line 1 Executing rc.d items... Starting /usr/local/etc/rc.d/*.sh...done. Bootup complete Unfortunately you probably need to restore a config.xml backup prior to the 03/28/07 image. I restored an old config file and now all run ok! Perfect! Thank you!!

http://forum.pfsense.org/index.php/topic,3955.0.html

Although proprietary, the Cisco ASA is a nice firewall.  Why would you want to load pfSense on it?  That would be like trying to retrofit Vyatta on a Cisco IOS router.  ???  :o (No offense to the pfSense or Vyatta developers….) Robert