There are numerous forum threads on how to do this on 2.0, including a sticky on the 2.0 board (where this post really belongs).

Gateway Groups are the way to do it now.

Okay, wasn't sure about jumping on latest snapshots right away.

To alleviate any concerns i found some memory errors in memtest when i returned the next day…more than likely the cause of the crash.

Thanks!

That was probably an update from last weekend, it was fixed shortly after it was put up.

Current updates should not have any problems.

If you have powerd on, disable it. If you don't have powerd enabled, try turning it on.

You can also try to enable/disable various BIOS options for power saving.

I've had some PCs that did that before, but it generally got worse with load, not better.

It's been fixed in current snapshots.

Open a todo action in redmine.pfsense.org

no known issues there, follow the traffic with packet capture for things that don't work and see what gets where. Is it coming in on WAN, leaving LAN, getting reply, leaving WAN?

you could try to use floating rules to redirect vpn traffic going out on WAN1 to go out on WAN2

thx.

But i dit it. Looks like everything works.

Maybe someone helps this:

1. use putty to login to the pfsense over ssh.
2. choose the menu Sehll (8)
3. type in "cd /var/db/rrd/
4. type in rm . (rm is like delete in DOS)

Thanks

Uh, why open my mouth to prove I am am an idiot..

well, I had the cables in the wrong holes didn't I!

the giveaway was Port state    = Down Not-in-Bndl

Ho Hum, sorry guys, interesting that it crashed like that though.

amazing what you can achieve after some sleep :P

Again, apologies..

:-X

PS 2 bge interfaces in LACP LAGG trunking vlans works well on 2.0 rc2…

:-\

I think I got it working with conjunction of limiter =D

Thanks, I'll try there :)

@ermal:

How does your sip use the old ip address?

It doesn't. The stale state records are preventing client-to-server communication. Client keeps sending packets to server and get no response until the sates are cleared manually.
The problem is known for quite a long time, in 1.2.3 it was 'fixed' by installing fit123 package (similar to the cron-based solution your suggested earlier).

You might want to update the title of the post and add [FIXED] or [RESOLVED]. Makes it easier on everyone. ;)

Good News, switching to pfsense original themes, I had the menus at the side, so I tried all the different 2.0 Rc2 themes and the only one that didn't have the menus was pfsense_ng.

I can live with that, Thanks for your help everyone!  :)

My apologies for the noise… this issue appears to be resolved after updating to:

2.0-RC2 (i386)
built on Thu May 19 19:44:17 EDT 2011

Thanks!

--Tim

Thanks Steve. Always interesting to see how other people does it. Like to see experiment and see what is possible, but this cause a lot of head scratching and little sleep.  ::)

Home many NICs on the server?

There could be several causes for this…If its just one NIC then check to see if its half duplex or full duplex. Is it 100 or gigabit? Might need a driver update.. ?

ok, thanks for for help