Thanks alot, this fixed the issue For anyone else trying to manualy fix this issue and your favourite text editor is Notepad, make sure it is not using "Word Wrap" otherwise you wil have issues when copying the code back into Pfsense :)

I assume you mean it still says 'Booting OS….'? That's what you see if no lcd driver has loaded. If it's actually showing some other Watchguard related information it must still be running the Watchguard OS. After you have loaded the lcdproc-dev package you have to go the Services: LCDproc: page and select the driver, screen size and port. Then add some screens in the second page. Then lcdproc should start. Steve

No body reply so I will answer it myself. Lucky me Jim pick up the issue and fixed it Detailed here https://redmine.pfsense.org/issues/3225 It works. Confirmed! Great job Jim!

It must somehow have made an empty tag or similar entry. If you look in the config.xml you will see it, it may have to be manually edited out.

Yep, I do have a backup. Will do the clean install, thanks.

Thanks for your help….upgraded the firmware to .99H from .99 and that did the trick! Once past that I have a baud rate mismatch I needed to correct...the ALix board was set to 38400 while pfSense was set to 9600...Thanks again to all who responded

Ah nice. I see it has a number of large and expensive looking ICs including this: http://www.idt.com/products/interface-connectivity/pci-express-solutions/pci-express-switches/io-expansion-switches/89hpes12n3a-12-lane-3-port-pcie-io-expansion-switch It's entirely possible that your BIOS is not playing nicely with this. I don't know enough about PCIe to give you any real clues here though. The only time I've seen a similar situation resolved the bridge chip was hiding the interfaces entirely. The fact the pfSense is able to detect and talk to the NICs at all suggests this PCIe switch is working.  :- It's probably not worth the effort to make this work to be honest. Steve

Try plugging an old simple nvidia card into a slot and use that during setup.  I had to plug a old PCI card into mine during initial setup be graphics was a mess with the internal unit.

Use a Live BSD CD…  http://www.livebsd.com/ to read the drive.

@stephenw10: A bit far then! So you did try the specific recommendations here? https://doc.pfsense.org/index.php/Verizon_UML290 Sure did.  That's where I started.  But from the logs it doesn't look like we're getting anywhere near close to even dialing which is what that page is mostly about.

Problem turned out to be the dns forwarder was not listening on localhost so of course it wouldn't work ;) Sorry for the false alarm!

@stephenw10: Something easy to overlook is the 'Disable Negate rules' option in System: Advanced: Firewall and NAT: This is unchecked by default so it normally negates the specified gateway for a policy based route if the destination is a local network. It should apply in the case here. Do you have this checked? Personally I always check this box because when I am deliberately separating local network segments I want to do so by simply not adding firewall rules rather than having to add block rules. Steve It is unchecked (default), wasn't even aware of it, maybe it's not working as intended in 2.1?

Hey techaholic, glad it helped!

Yea i was using pfSense-2.0.3-RELEASE-2G-i386-nanobsd Well i just made a new usb install to fix it. We will see in the future if i get the same problem.

Thats what I normally tell people they should do.  I'm glad thats working for you.  :)

Last night I reinstalled Postfix Forwarder. In Services->Postfix Forwarder I needed to save all tabs, then it works like a charm. I also reinstalled the Mailscanner package, but the service status still not works.

I'd be interested in knowing what you did with IPSEC and what problems you noted or changes fixed them?

I believe 2.1RC2 booted the USB stick, installed and then did a panic during the disk boot (geom raid 1).  I think I'm going to remove the bridge and put the DMZ on a private subnet and do some 1:1 nat.  Hopefully, that will fix the intermittent issues with the WAN interface..  If I had hands on access I'd probably try again with 2.1 and put up a better fight.  I just didn't know the release was coming so quick.

Hi, thanks, for this good news, now i don't have machine to test it.

I feel writing a personal message is a better thanks. Just clicking a button is lazy ;-) I am sorry for the mail notification that's raised by a manual message (by clicking the button maybe too?) ;-)