On 19 Feb 2013, at 22:30, - Dickie Bradford - <[email protected]> wrote:
> I had the same issue with https and constantly having to re-login, the way i > worked around it was to force all https connections out the fastest wan link. > Its not ideal , but it was the only way I found to address it. This is usually the approach I take. An alternative - assuming your network traffic is fairly evenly spread amongst a number of similar clients - might be to alternate WAN links based on source rather than destination. For example, x.y.z.1 goes via WAN1, x.y.z.2 goes via WAN2, x.y.z.3 via WAN1, etc. etc. Having said that, I've found the best approach is often to choose the WAN link based on service (i.e. port). Most people don't mind if their HTTP requests are a bit slower than usual when things are busy, but people get very upset when time-critical traffic is delayed - SSH terminals become virtually unusable, VoIP is all but impossible, etc.. So you may be able to achieve a better user experience by routing HTTP down one connection and "everything else" down the other connection. In extremis, you might even have a separate connection purely for torrents and the like. Kind regards, Chris -- This email is made from 100% recycled electrons _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
