I haven't seen it work yet, but you might start a thread on the 2.0 board asking if anyone else has.

thnx for the kind respond. yes bro i know this also. i have 2 router for my two connection. but problem is when we try to setup multi wan on pfsense 1.2.3 version it worked only 2 days. then when we try to setup multiwan on alpha 2.0. we couldnt manage it. because its seems very different from 1.2.3. so please it would be great help if someone can guide us. or give us a link for help. thank you

Thanks for the answer I was looking (and hoping) for. I will also look at the LAN addressing as advised. I have just downloaded the ISO image and will fire it up under VirtualBox before committing to the real hardware. Thanks again. David Goadby, North Wales, UK

Jimp: I added a rule as you suggested and it worked. Thank you very much.

Thanks GruensFroeschli! I think I'm ready to start playing.

Got it. Many thanks! :)

I was at the datacenter this morning and setup the firewalls with 1 WAN connection each and CARP. Everything works great. If I unplug the WAN from the primary firewall (PF1) it fails over to PF2, same thing is I unplug the LAN. It also falls back to PF1 when the connection comes back up. Sweet! Jon

Just add them as Virtual IPs and configure outbound NAT as desired.

I ordered the pfsense book, uninstalled everything and started fresh. It worked without doing anything special. I must have selected some setting I didn't know. Thanks for your help everyone!

My setup requires opt1 & opt2 to be load-balanced. How can I restart apinger manually?

I could think of a way or two, how to do something like this, but….. Do yourself a favor and reconfigure it to use different subnet. You will have way less problems and save yourself a lot of headaches ;)

It's normal, your existing states are not killed when a WAN goes offline (they are in 2.0).

Wow, it's fixed….it was a rule on the LAN....... I have a rule that specifies the gateway to WAN1 for a few users. That rule was above the DMZ rule pictured above. I moved it directly below and it works now..... So firewall rules override static routes. good to know.

First set them up as Virtual IPs. You should then be able to define the rules and NAT.

Your problem is the touch /tmp/filter_dirty error. There are newer snapshots of the 1_2 branch that have that fixed. http://snapshots.pfsense.org/FreeBSD_RELENG_7_2/i386/pfSense_RELENG_1_2/updates/ Note: I would not recommend those for anyone else to use.