Can happen to anyone!  :D Steve

Thanks to all for your help.  The solution was found by: -Enable DNS Forwarder in pfsense It works great now.

Thanks! could have find it jp

You could re-apply a firmware update, or grab a clean copy of a file from github, but if a file was corrupted, the storage can't be trusted. I'd suspect the adapter more than anything. Also make sure DMA is off (check the doc wiki)

Same here for NTP for lonnnng time… PPP has recently become very anemic...

spoke too soon, the error is different: /libexec/ld-elf.so.1: Shared object "libz.so.6" not found, required by "libneon.so.27"

What is in the PPP logs on pfSense? (See Status -> System Logs, click on PPP tab) I have just noticed my ppp log is empty. Perhaps your ppp log won't yield any useful information. What is the output of the pfSense shell command ifconfig -a Have you followed suggestions in http://doc.pfsense.org/index.php/Accessing_modem_from_inside_firewall

I took the easy way out.  I bought a refurbished SATA drive and that worked without the mount issue.  Thanks, chpalmer, for answering my post and giving me some options for dealing with the mount issue.

Depending on package, you will get config file erros or missing file erros. I think there is a script on pfsense That makes a full backup. Try to find it searching forum or pfsense file system. EDIT: The scripts for full backup are /etc/rc.create_full_backup and /etc/rc.restore_full_backup Related topic http://forum.pfsense.org/index.php/topic,44637.0.html

I re-loaded the 2gb image after successfully loading and booting from the 512mb image. A bad image load at first.  All is working now, thanks!

Yeah it worked… Just neede fstab edit from ad16a1s1 to ad4a1s1 Or something like that :)

It would be even better if the pfSense devs just built it to format & start at 2048 in the next 2.02 release. No reason not to these days.

Under system Information : ersion 2.0.1-RELEASE (i386) built on Mon Dec 12 18:24:17 EST 2011 FreeBSD 8.1-RELEASE-p6 Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /etc/inc/system.inc:2) in /etc/inc/auth.inc on line 1254 Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/system.inc:2) in /usr/local/www/guiconfig.inc on line 47 Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/system.inc:2) in /usr/local/www/guiconfig.inc on line 48 Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/system.inc:2) in /usr/local/www/guiconfig.inc on line 49 Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/system.inc:2) in /usr/local/www/guiconfig.inc on line 50 Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/system.inc:2) in /usr/local/www/guiconfig.inc on line 51

I'm fairly sure since 2.0 all versions are using an SMP kernel since it now handles a single cpu with no problems. I also thought that it was a restriction of pf to a single process that limited the total potential throughput of pfSense. I realise that's a simplification. Steve

You can go right to 2.0.1, you don't need to go through 1.2.3. I've even upgraded a VM from 1.2 up to 2.0.1 before. The upgrade code takes care of all the needed bits from every old version.

See: http://forum.pfsense.org/index.php?topic=44072.0 It will probably not work without patching some files and recompiling. Steve

Hope 2.1 is better on these standard machines.  As for your comments, I have to agree with others in such places such as this - http://arstechnica.com/civis/viewtopic.php?f=10&t=1137301 - too much "KoolAid" of your product.  You have good product don't ruin it with those type of comments here and there…

The TEAK 3035 box turned up today with a VGA port on the back. There was no mention of that port in the specs! I popped in a 2.5" HDD and a memory upgrade and then installed the full LIVE version and installed it to the HDD without any problems at all. All is looking good so far. Thanks for your efforts Jim, although not required. Gordon

it was set for amd64…. on all 4 firewalls..... still the "upgrade" installed the x86 edition one of the firewalls was even a fresh install, everything set up from scratch..... (not imported any previous setups...)