Fixed thanks.

You might want to try a later snapshot.

The apinger warnings were caused by a typo in the code which accidentally set the latency low watermark to 10 ms, which should have been 10% packet loss.

That's been fixed.

Thanks :)

Thanks, looks like i got it running. Took out all capital letters and spaces in wan, gateway and gateway groups. Also found sticky connections kills all traffic within 30 sec after activation.

As a newbie, you really shouldn't be running 2.0.  It's still a work in progress and not meant for any use beyond testing right now.  There is no way to determine that the problems you may encounter are configuration related versus bugs in the system.

Yep, I know; I should have been clearer.

Will pfSense 2.0 be moved from FreeBSD 7.1 to FreeBSD 7.2 base?  I'd think it would be good to develop 2.0 pfSense on the latest released (7.2) and next development (8.0), rather than 7.1

Thank You, ermal!

I've checked snapshot pfSense-Full-Update-2.0-ALPHA-ALPHA-20090530-0319, the problem is fixed.

Should be fixed in the next snap. Looks like it was just an extra errant space in a commit tonight.

If you can somehow get to the menu and start the PHP shell (Or type /usr/local/sbin/pfSsh.php from a normal shell prompt) and then do:

playback cvssync
exec
Then if it doesn't automatically exit, type:
exit(0);
exec

I have had this on 3 diff PC's and using both 7.1 builds and 8.0 builds of Pfsense 2.0.

Not sure what it is.. but annoying.

Fixed thanks for reporting.

Thanks. Perfect. ;)

You are right, sorry. Glitch of some sort. If login routes does not do much, however if first go to another section and then to routs, work perfect.

Only two developers ISOs I've ever tried:
http://snapshots.pfsense.org/FreeBSD_RELENG_8_0/pfSense_HEAD/livecd_installer/pfSense-Developers-2.0-ALPHA-ALPHA-20090523-0539.iso.gz, and
http://snapshots.pfsense.org/FreeBSD_RELENG_8_0/pfSense_HEAD/livecd_installer/pfSense-Developers-2.0-ALPHA-ALPHA-20090522-1218.iso.gz

So by the timestamps, looks like the commit is in is in the first one but not the second.  No change though, both point to the serial console.

regards, …... Charlie

certainly on v1.2.2 it's simply a matter of adding multiple instances of the same interface to a load balancing group
We have a 1.5Mbps line with 512Kbps backup, which is always on, so the 1.5Mbps line has three entries in the pool and 512 has one- works fine. Failover is in either direction.