On 1.2.2 and older, any upgrade required a complete reflash+restore config. Since you have to do that anyway, there's no reason not to go right to 2.0.1.

@slth: In case you are wondering how on Windows: cmd -> diskpart -> list disk -> select disk #yourflashdrive -> clean by GUI Control Panel->Administrative Tools->Computer Management->Disk Management.. find the USB stick drive listed, usually by the bottom of the list. Click on existing partition, right mouse click and select "delete.." from menu.. then create new partition by right clicking on raw drive volume and selecting "New Simple Volume"..

Unless you happen to be lucky and have the default NICs in your config (presently the defaults are vr-based interfaces for ALIX/Soekris) you do have to assign NICs before you can do anything. There is an open ticket to attempt some sort of "auto assign" but there are some problems with doing that dynamically that are not easy to solve.

FINALLY!! After coming close to loosing it and taking a chain saw to my router I decided it was rtfm time. I don't find the cli on the HH very easy to get to grips with but managed to get all traffic sent to one IP address. As well as this the BT HH wasn't playing fair as the web gui wasn't doing as I told it too with the benefit of loking at the cli so I performed a factory default on it. Now the router is configured the way I was trying to get it configured via the web gui, cept it all works even port forwarding. Lets hope it stays that way

Access the latest area of ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/Latest/ And check the packages names and then pkg_add it.

Almost all dual port copper (RJ45, Cat5, Cat6, etc) Ethernet cards operate as independent interfaces, meaning that the Operating System and any software involved doesn't really notice that they happen to be sharing a slot on the motherboard.  At least as far as you or any software you're concerned about cares.  If you happen upon a card that doesn't operate this way, then it's most likely some oddball card that wouldn't be supported anyway.  If it's in the supported hardware list, it should operate in the way that you want. The main point that some people don't notice when starting out, with optical cards, mostly, is that it takes 2 strands of fiber to facilitate communication on a single port; what may look like 2 sockets is still a single port; one side sends, the other receives.  The other side to optical cards is them not being obvious by appearance as to whether they're an Ethernet card or a FiberChannel HBA.  Look up the model, it'll tell you.  There are dual port Optical cards as well, both as Ethernet and FiberChannel.  In the Ehternet realm, dual port Optical cards should operate as 2 independent interfaces; FiberChannel, not always, but that probably doesn't fully matter for your purposes. Oh, and there's also Quad port Ethernet cards.  Those should also be 4x independent Ethernet interfaces.

No you shouldn't need that. Just edit the fstab so that it gets mounted at boot. The shellcmd package only gives you easy access to the shellcmd option in config file anyway. Steve

@ezyclie: How come you can get 2.0.2-RC1? What is your "Firmware Auto Update URL"? The dashboard flashed me that an update is available, but to download this you need to go in system -> firmware -> updater setings. And there check the "allow auto-update [….]".

If I recall correctly, I had trouble with running pfSense in a VirtualBox VM when VirtualBox provided emulated AMD (pcn?) NICs to pfSense. The problem went away when I changed (in VirtualBox) the NIC emulation to Intel E1000 (82554 chipset?) - pfSense devices em0 and em1. It is not clear what you have bridged with what. (It takes some care to get it right.) I presume the Windows VM is bridged with the pfSense LAN NIC and the pfSense WAN NIC is bridged with a NIC connecting to a modem connecting to the Internet.

Glad to see this saga is solved.  ;D  I marked it as such.

What a extrem solution! RFC 1483 doesn't need authentication ;) I have the connection now working properly. I have configured the Linksys as a single user with my static IP through RFC 1483 Routed. It should be the same configuration for any router. Linksys configuration: Configure the LAN Ip interface with your ISP gateway IP and the mask (both provided by your ISP) Disable NAT. pfSense configuration: Configure your WAN IP interface with your ISP public IP and the mask. Add a gateway with the IP of the Linksys LAN interface. And enjoy, in my case after that, I had to reset the device to establish the connection.

Ok, so I was able to work when I chose the "Member Down" option and then unplugging the ethernet wire.  I just assumed that when I chose "Packet loss & High Latency" option that it would still work with the ethernet unplugged because technically an unplugged ethernet wire is 100% packet loss.  Ah well, it's working now so that's solved. BUT, the only thing that does not work with failover is, dun dun dun, the Server!  It works fine with the Tier 1 internet, but fails with the Tier 2 internet.  I dunno why.  I went to Firewall: Rules and changed the default gateway to the Failover one.  So any other ideas? Update: Ha, solved that.  All I had to do was add another NAT rule (DUHHH!) since it's on the OPT1 interface.  Wow, happy day today.  Just hope everything stays working fingers crossed…for a few seconds cause I need to eat  ;D  :D So this can be marked as solved, yay!

This is probably due to an error in the acpi table in the bios, it is indicating a sensor at an incorrect location hence the bad value. You should first check to see if a newer bios is available. Alternatively it may be possible to disable parts of acpi by adding: debug.acpi.disabled="thermal" ```to /boot/loader.conf.local Though I've never tried this myself. Steve

podilarius, it's a binary update here's the details (this is an install yesterday after switching the update URL to get 2.0.2-RC): 2.0.2-RC1 (i386) built on Wed May 16 17:53:37 EDT 2012 FreeBSD 8.1-RELEASE-p9 Update available. Click Here to view update. and, after running the auto updater this morning: 2.0.2-RC1 (i386) built on Thu May 17 23:24:26 EDT 2012 FreeBSD 8.1-RELEASE-p9 You are on the latest version.

You could follow this thread: http://forum.pfsense.org/index.php/topic,48780.0.html That involves such a device. Steve