You can just disable CARP on the master to force it to fail over. Or shut down the master. Normally I do what dotdash recommended.

Link removed. No plans for any further 1.2.x snapshots.

yes pfsense can

Disabling packet mode during boot block installation solved the issue.

I updated the squid package and shortened the tab names so they should go back to tabs instead of the drop-down list.

They are usually announced in various places, the two main ones are: The pfSense blog (you could use the RSS feed): http://blog.pfsense.org/ Mailing lists (including an announce list): http://www.pfsense.org/index.php?option=com_content&task=view&id=66&Itemid=71

i think it's the motherboard. I have an Asus P5K PRO, i tried with a p4V88+ and it worked perfectly with same cables, hardware, so and software. I don't know why, because i have the same setting both in the bios and so.

@jjj: A couple times, it was if someone was holding down the up or down button and it was just scrolling through the options really fast. Then the beeping might have been due to overflow of the keyboard input buffer. I have a system that intermittently seems to go into keyboard "permanent repeat" mode as if a keyboard key was held down. My impression (over 4 or 5 years) is that it happens far less frequently with USB keyboard than PS/2 keyboard, its most likely to happen at startup (though it occasionally happens when the system has been running for an extended period) and it happens more frequently when the system has been powered off for a long period (more than a couple of weeks).

That's good :-) I guess 1.11 is newer than 1.4a anyhow, and you're right that is all I see on their site now. Perhaps mine needs a BIOS update the next time I swap the CF.

@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.