Enabled the bootblocks and all is still well, many thank.

On a side note, I have an extremely old PCI WAN card (10 years old) for a cable network and it doesn't come up as a interface.  I have drivers for it but I do not know the location on where to put the driver.  I will start another thread for this.

BSDPerimeter, including the founders of pfSense, offer this as a service.
https://portal.pfsense.org/index.php/reseller-subscription.
You could also tackle this yourself but if you plan on re-selling pfSense it will be much quicker to have them do it.
http://devwiki.pfsense.org/ReBrandingSupport

Steve

Tnx so much!! i think everything works fine!!
tnx again!!

Sure, with embedded it's easy. Just use dd/physdiskwrite/something else to write the embedded image to the CF. I thought Netgate even had 2.0 images for the Hamakua with the right bits set on them to boot correctly. Check their website or e-mail their support, they're a good bunch of guys they can point you in the right direction. (Especially if you let them know you're looking to order more. :-)

http://redmine.pfsense.com
What you're probably interested in is:
http://redmine.pfsense.com/projects/pfsense/activity

@Perry:

Yes

@http://forum.pfsense.org/index.php/topic:

Usually this is happening when you have nano bsd installed and you are trying to follow the boot sequence through the VGA port. In that case, you will have to attach the null modem cable and connect through the serial port. Nano bsd does not load VGA drivers.

To support different sizes of CF cards as you now can upgrade and install some packages on nanobsd.

doc.pfsense.org and forum search is your friend
If your new to networking and pfSense the book will really help you out

thanks

I don't think I have sticky connections.  Correct me if I'm wrong but I would not have that unless I have a multi-wan setup (which I do not).

Thanks for the link.  I've changed my DNS to openDNS for now.

As for the 6 possible causes in the article
1. How would I ensure this? 
2. The LAN subnet mask is 255.255.250.0 (Status -> interfaces) in pfsense and the same on the asus router.  It is 255.255.240 on the WAN if that matters.
3. Where do I set the MTU?  Pinging with 1500 bytes was successful
4. Traceroute does not stop upstream - not applicable
5. Not applicable
6. Did this

I'll post back if I continue to have problems.

I've seen similar issues when there was existing data on the HDD. That isn't normally a problem but can have issues in certain cases.

Have you tried writing zeroes to the whole drive and then attempting the install again?

Was looking for the same thing, I found this to be a perfect guide to this 5 step process (I’m novice in freebsd):
http://www.mail-archive.com/support@pfsense.com/msg06000.html

Granted it's for migrating graphs within the same pfsense version numbers. not sure what happens if you try to do this after an upgrade from 1.2.3 to 2.0.

I had to do this since I didn't upgrade I just moved freebsd to a VM, it was easier to reinstall than to look for ways to virtualize that machine…
Hope this helps some poor soul coming from google :)

@stephenw10:

If you connect the router via it's WAN port then it will still be acting as a router including many of the functions now handled by pfSense, NAT firewall etc. This will work as long as you have different subnets. E.g. pfSense LAN port set to 192.168.1.1 and router LAN ports set to 192.168.2.X. Your router will then receive an IP address for it's WAN port from pfSense.
However this is not ideal as you will have double NAT and that can lead to problems. If you can use your router simply as a switch and wireless access point then that is what you should do. Disable the DHCP server in the router and connect the pfSense LAN interface to one of the router LAN connections. Leave the router WAN socket empty. Depending on how your router is configured this may work perfectly or not!  :P

Awesome!  disabling the DHCP of the router seems to have done the trick.  Even the wireless computer is working with no reconfiguring.

Thanks a ton for all of your help.
-=Mark=-

Hmmm,
I'm out of ideas at this point.  :(
You could try reflashing the card. You could try a different CF card. You could try a different image.

Steve

You should probably start a new topic. since this topic has been dead for a while now.

I do not know the answer to your question, but i would think it would work. since upgrading is the same thing. Just remember that some packages that worked on 1.2.3 do not work on 2.0.

You must have a restrictive ruleset on LAN then. Previously, the "anti-lockout" rule would have allowed that DNS traffic because it allowed anything to hit the pfSense LAN IP, but now that is not the case.

As for the gateway selection, it works fine for me with FF 4.0.1, there may have been something in the browser cache that needed cleared.

Via VT6103 Networking Controller
And Intel Pro GT….

Via for WAN Intel for LAN

Did you change any bios settings? It could be your bios battery has gone flat and it's gone back to the defaults.
Unless you have a very complex setup you need to recover I'd just reflash the CF card if only to rule that out.

Steve

Hacom have a modified image that they distribute for their own hardware but anyone can use it. It has several differences to the main pfSense image, primarily it uses keyboard/vga for it's main console output. The pfSense nanoBSD images use the serial port for the main console.

Use the pfSense images unless you can't use the serial console for some reason.

When you've installed the image the package manager will only display packages that can be installed.

Steve

The PPPoE username/password bug was fixed after RC1. Current snapshots wouldn't have that problem.

Not easily from the nanobsd images.
However Hacom have some pre-modified images for their own hardware which have both VGA and serial output.
You could try one of these: http://www.hacom.net/kb/pfsense-2-rc1

Steve