Unless your ISP is involved, you’re not going to do link aggregation or BGP.
I’m guessing you’re doing NAT on both of these WAN connections, and not just
routing. In this case I would recommend separating traffic by user, or by
port/protocol.
I had a DSL and T1 arrangement a while ago and found that the best experience
was to let web users hit the DSL, and put ssh and latency sensitive stuff on
the T1. Allowing web connections to dynamically bounce between the two uplink
connections caused problems for web sites that attempted to detect spoofing or
maintain a persistent connection over stateless http.
Multiple WAN is good for traffic separation or failover. But don’t expect
magic aggregate throughput unless your ISP is intimately involved and you’ve
got native addresses.
We have since switched to a single fiber link and it’s much less troublesome.
ED.
> On 2016, May 10, at 2:38 AM, FrancisM <fran...@mytechrepublic.com> wrote:
>
> Dear All,
>
> Im a fan of pfsense and been using it the old days 14years ago using the
> CLI script in freeBSD OS. Now Im using the latest release of this web GUI
> in my home lab network including my home network. I just want to know if I
> can aggregate two WAN Connection to become one huge uplink?
>
> sample lets say i have two times 10Mb and will become 20Mb total bandwidth.
>
> Thanks
> _______________________________________________
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
