So how exactly are we playing BF3 this year? Are we going to get crushed by whatever decrepit pipe comes into the hotel?

Comcast does a great job and brings pipes bigger than Spicy McHaggis

It's an aggregate total of about 230 down, 22 up

But the goal is to have all BF3 traffic going out one pipe so as to avoid retarded punkbuster bans and other BF3-remote-server-why-can't-I-have-a-local-dedicated-server-bullmularkey.

We'll also be utilizing sticky connections since this is a dual-WAN setup as described here: http://forum.pfsense.org/index.php/topic,44012.0.html to hopefully avoid headaches and frustration.

I haven't experimented with dual WAN's other than in a lab as I dont have have the equipment/connections.  But in theory your 2nd post (the thread's 3rd), was the only way that I could foresee it working 100% without issues 100% of the time. 

I was going to try this at our past local LAN.  A crude test was to tether with my phone on a laptop.  Then enable  Internet Connection Sharing to the wired NIC and hook a pfsense WAN up to it.  This way I'd have one WAN going out to fios, and one WAN using my phone.   I was then going to run wireshark to gather the information on ports and filter BF3 traffic.  Create an alias for all the known BF/PB ports and create a rule to filter them out to fios.  Then create a NOT rule with the same information and send it out the tethered LAN.

Unfortunately, I never got a chance to do it while replacing a failing RAID card, and having issues with our UT3 and CSS servers (thanks fearon).  I still want to try it though.  I can post my findings if you like.

The sticky connections works but in theorycan still fail.  You had more time testing it than I, so I believe that failure rate (if there even was one) has to be so low that its not an issue for you.

But based off this from the Sticky Connection description:

This 'sticky connection' will exist as long as there are states that refer to this connection. Once the states expire, so will the sticky connection.

If you havent already I'd set the "Firewall Optimzation Option" in the advanced settings to either high-latency or conservative.  Which ever option holds connections longer.  Both descriptions elude to holding connections longer than default.  Downside is obviously a larger state table, hope theres enough RAM.

I <3 pfsense.  Its been my savior at work and at home!  It certainly is more than capable of getting this job done.  I'm curious as to what hardware you guys run it on.  I've run it on several different machines from P2 400mhz/256MB RAM up to now a C2D 2.3ghz/2GB RAM.  It scales so well.    I thought I read somewhere that v2.1 will have full multi-core support.  That will be awesome!  As of now that 2nd core is hardly being used :(

Sweet.  I have complete faith there will be no issues

Mind sharing the port list you came up with?  Would save me alot of time when I go to test this.

*edit* double negative fail.