cmb, thank you for the reply and I understand what you are saying. The whole reason for this project is to get around bandwidth throttling at my apartment complex. But it looks like I am out of luck. Thanks guys.

That's completely different. That's a question for the OpenVPN board here, not routing. I think you need to push the appropriate routes to your clients. See the OpenVPN page on doc.pfsense.org, I think it has the info you need.
http://doc.pfsense.org/index.php/Setting_up_OpenVPN_with_pfSense

well, you can guess why i chose to take a closer look at pfsense twice, but you'll only gonna need one!

I tried one of those "loadbalancing soho routers" from Allnet - not my best choice yet, not to say ugly things about it…..

Then I tried Netgear (about 250 US$), not cheap, but if it works well, why not - ok, not so well, in fact, massive probs with https-sessions broken (used both wan-ports for single onlinebanking session - not so good then...) and sometimes DNS-Querys just got lost, so no answer to browser, except "server not found".

My next choice would have been a small, tiny Cisco Loadbalancer, not exactly the price of a new car - even a japanese one (by the way, i own a Honda Civic! - so no hard feelings - ok?)- but a nice Homecinema Flatscreen TV would fit much better in the plans of the wife than this "little gray box".
So I have to investigate open source software if anything there could be my salvation. And now it looks like I've found, what I'm looking for (unlike Bono).

So I consider this "Bounty" thing for adjustable round robin Load Balancing. Perhaps, if there are some others, we could join for a bounty and make the developers or advanced users help us on this one? I don't know how much work it would be, but I would not wonder if it could be resolved quite fast (and cheap ;) )

If you want to send all your traffic from 192.168.x.125 to opt1 then setup a firewall rule with interface: LAN, source ip  192.168.x.125 and gateway opt1.

This is known as policy based routing.

The next step is to get all your torrent stuff allowed in. That would require rules on the OPT1 interface.  Take a look at the NAT section of this forum for help on that.

Well i found a work around by inspecting the javascript code.

Select the pool type to Server. Put the value of the interface (e.g. wan or opt1) in the "Server IP Address" text box. Now change the type to Gateway and create the pool. The javascript remembers the name you typed in the Server IP address text (even though it is not visible anymore)

I think I answered this myself, it only made a difference when I set the interface to Public, which is what I figured. And then, I had to set the rule allowing DNS traffic to use "default" rather than anything else.

Thanks, this helped out loads!

@bijualapatt:

Hi

Could you tell me, what changes you have made.  I 'm also in the same problem

Biju

try using this docs, there's a lot of screenshots that will help you here

http://doc.pfsense.org/index.php/MultiWanVersion1.2

Thanks for the help guys. I ended up just running win2k in vmware and routing all its traffic through opt1 for torrents.

put a cheap router between wan2 and the 2end cable modem
then the gateways are differend and then pfsense can route the trafic

Remove the gateway(s) on the T1 rules tab  and try again.

I think you want to add a firewall rule on the lan tab.
Something like:tcp from lan net any port dest=3rd party server IP port any gateway=int a gateway
Oh, and I think you should've posted in the Dual-WAN forum…

Can you give me an example of issues I might run into with the double-nat stuff?

Wow, that was fast, thanks!

that's "normal" with multi WAN like you have. It's not a major issue, as everything will work as you desire, but I consider it a bug. I already have a ticket open on it.
http://cvstrac.pfsense.com/tktview?tn=1320,6

You can work around it by creating a rule permitting traffic to your OPT IP with no gateway selection, and move that rule to the top of your OPT ruleset.