What build are you using?  and what type of hardware?
RC

We're seeing a similar thing, it either doesn't work, or ports are mixed up.
Meaning we're doing Port forwards with aliases, where more than one port is redirected.
Is this legal ?

thanks in advance

One Pfsense  used for the Multi-WAN, Multi-LAN (wireless, openvpn) can run Load Balance with Normal. Just log on the load balance constraints are still there ….. :)

In choosing the bootup slice the drop down menu reads:
"ad0s1" and "ad0s2."

The confirmation text reads:
"The boot slice has been set to pfsense0" or "The boot slice has been set to pfsense1."

This seems a bit confusing.  The confirmations should read the same as the drop down menu or vise versa.
thanks,
Jim

Depends on the specifics of your environment, and the quality of the Internet connections. 5 seconds is pretty low, may cause unnecessary renegotiation.

I would try reinstalling lightsquid.  It works fine for me in RC2

There likely won't be any 1.2.x releases post-1.2.3. The reason for going ahead with the switch is so you can upgrade to 2.0 without reflashing once that time comes.

@gloomrider:

Oh, and have ssh host keys always been in the conf directory?

Yes.

i got same width 1.2.2
maybe disk usage is 100% or over?

bump.

any news of this yet.

just to clear up. i have 4gb cf version installed.
1.2.3-RC2
built on Mon Jul 13 20:07:43 EDT 2009

when i go to automatic update it shows that 22nd july builds is the lastest snapshot available. when on the http website, the latest snapshot for 4gb cf version only appears to be the 21st july build.

The update took a while to download, longer than normal(it stopped at 25 meg for about 30 second and then started right backup.  Since my box is virtual it had a bunch of werid errors during the reboot.  But after that the reboot was perfect no errors and it's running perfect.

RC

Speaking from experience, you might want to use seagate or samsung drives instead of WD.

@strafelife:

I do have a question, I hope someone could answer.  I am using a VIA C3 cpu, which has native crypto acceleration for AES (padlock) - without running any benchmarks, should I disable glxsb or leave it enabled?  Does it make a difference for the VIA cpu at all either way?

AFAIK, The glxsb hardware is only present in the AMD Geode chipset, so this only applies to PC Engines Alix, Soekris boards, and similar units based on that chipset. The VIA and other chipsets should just fail to load the driver and not cause any problems. You would want to check if the padlock driver is getting loaded for your hardware, but that should be another thread.
@onhel:

I also upgraded to the same snap.  I see the option to disable GLXSB and by default it's unchecked, but when I run dmesg it shows no driver attached even with GLXSB enabled by default.  Was the driver omitted in this snap?

It's a module, not in the kernel. You can verify it's loaded with kldstat.

now i tried an external wlan usb stick(AVM Fritz) instead of my notebook internal wifi card.
with the usb wlan stick i get an DHCP configuration.
so it seems the problem depends on the used wifi adapter in the client.

Bah!! Wish I seen this before I wiped the hard drive with a fresh install.  Ah well

Nice catch tho.

Yes, serial console …