@danswartz:

Just upgraded to 1.2.3 Final.  Smooth as can be (outstanding work devs!)  Only glitch: when I went to top-level page, no widgets.  I reinstalled the xml component of the dashboard and all was well.  Hmmm….

That is normal.

The dashboard package replaces index.php, which is also overwritten during the upgrade process. Thus, you must reinstall the dashboard after any firmware upgrade in order to get the widgets back.

maybe because it was a full install, instead of an "upgrade". i had to ssh into my box and point it to a different mirror for it to update.

I have never had my shell access disabled after doing an update.

shell into the box and upgrade from console and point to the file you want to upgrade to. Happened to me and i pointed it to the ncsa server and about 10 minutes later i had 1.2.3.

Fixed now.

I had entered a Gateway address to the OPT1 IP configuration when I was getting the WAN-OPT1 bridge  working under the prior RC3 version.

Clearing the Gateway address field seems to have fixed the problem.

You must be running 1.2.3 to see that information, as in 1.2.2 (and very early 1.2.3 builds) there was no support for the chipset in the ALIX in the kernel. It worked, but it didn't know enough to print that line and make the LEDs work, etc.

Without that, it's a bit harder to figure out. You'd probably have to follow this:
http://doc.pfsense.org/index.php/Remount_embedded_filesystem_as_read-write

And add the dmidecode package:
pkg_add -r dmidecode
rehash
dmidecode | more

That should show you information about the system's BIOS

I think they've been broken for a while, not sure why they're being built actually, AFAIK none of the developers use them. Use a stock FreeBSD 7.2 install.

There aren't any, just use a stock FreeBSD 7.2.

What exactly is the error?

You'll have to disassemble to get to 1.2.3, but from there you won't in the future. If you buy your ALIX kits from Netgate, they ship pre-installed.
http://www.netgate.com/index.php?cPath=60_84&osCsid=d2cdcca7f4cc3d831f0dba310f12febe

Generally in the past, you could downgrade successfully. We now have tighter checks on upgrade files that check a platform file that doesn't exist in older updates, to make sure you can't apply the wrong update. You can bypass that by editing /usr/local/www/system_firmware.php and removing these two lines:

if (file_is_for_platform($_FILES['ulfile']['tmp_name'], $_FILES['ulfile']['name']) == false && !$_POST['sig_override'])
$input_errors[] = "The uploaded image file is not for this platform ({$g['platform']}).";

make sure you get a config backup before you downgrade and be ready to reinstall in the worst case.

It looks to me (based on the error message) that the version I used had a smaller slice size and it was increased in the later revisions, not the other way around.

In any case, I reflashed with the 1.2.3-RELEASE, restored my config and all is well.

Thanks!

Despite your advice it appears the display driver fails somehow on my sis chipset (junk btw) so I went ahead and installed it on a VM. Using an nLite'd XP Pro install for minimal host overhead I have had great success running pfSense 1.2.3-Release with virtualbox. After bridging the adapters and mirroring the WAN mac it performs great, especially squid and upnp. Hope to get it on some real hardware soon. Thx again.

Make sure you decompress the image first using something like 7-zip so you are only writing the .img file

You may also try using Physgui+Physdiskwrite

If all else fails, try the 2GB image. Your card may be slightly too small to fit the full 4GB image, in testing we found several cards that were undersized, but the current crop of images should have been sized low enough to fit on most.

@scarrico:

Can you explain how one neuters conf_mount_ro()?  Do I just comment out the conf_mount_ro() line in /etc/rc.conf_mount_ro()?

No, that isn't enough. Lots of places call that function directly, not by executing the rc script. You need to find the actual function definition for that, and disable the parts which actually set the filesystem read-only.

( If it sounds like I'm being vague, I am, as I wouldn't want someone to do this unless they knew enough to figure out the rest :) )

October is pretty old, unfortunately.  NanoBSD was a moving target up until a brief bit ago.

In these cases you will have to reflash.

Okay, so I dusted off an old Super Micro Dual Xeon server with 2GB Ram. Installed the LiveCD PFSENSE 1.2.3 Release.

(OMG You guys did AN AMAZING JOB on the interface, ITS SO PRETTY Compared to 1.2.2!!!!!)

Fired it up on the Cisco as one of our unused IP addresses, and basically every problem is resolved now. I'm just going to apply our old config at the end of the day today and see if it breaks anything, and if not, I will put this new box live on the network (Basically just have to move a cable around.)

Good job on the new release. Not sure what happened with our old install, maybe it is corrupt or maybe the hardware serving it is corrupt. It was the oldest computer around, a piece of crap seanix with a 48X CDROM, Lol.

^ Nice.

Not really a tutorial, but it's all XML and pretty well laid out so it should be easy to find the spot where you need to edit the interfaces.

It would look something like:

Replace vr0 with whatever network card you are using for LAN.

As for actually getting to the config, there are some tips here:
http://doc.pfsense.org/index.php/Modifying_Embedded