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

It works great on XEN server, I have had it running on vmware and it runs as well.  I prefer the XEN. RC

Thanks Jimp, it works like a charm now! :)

Hey thanks for the reply. I couldnt figure it out, then 2 days ago a new version of software was available, so i updated automatically from the GUI, still version 2.0-RC2 but was 2 days newer than the one i had installed, after it installed and i rebooted, all my NIC's are showing up and working together!!  So problem solved here :) Thanks for all the help that everyone gave, its this support that kept me interested in using pfSense

Since you uninstalled all packages and it did not work verty well, I suggest restarting fresh…  I did it yesterday because everything was screwed up badly, pf wouldnt event load the webconfigurator. Download the ISO file, burn and reinstall.  Then upgrade via either webconfigurator -> firmware upgrade, or SSH.  Just to give you an idea how easy this can be, I reinstalled 1.2.3, upgraded to 2.0RC1 then upgraded to 2.0RC2 and reinstalled all packages (squid, squidguard, snort, country block, ip block, HAVP A/V, Cron, ntop) from my iphone via Wifi! :)

Hi Steve, I had to put it indeed in the config.xml because i lost it after the updates.

Best to get the hash from a different mirror, pick any of them. Whether or not you have to download the file or it just opens in your browser depends on the config of the web server on that particular mirror.