|
User Reviews/Comments:
rate:
avg:
![]() ![]() ![]() ![]() ![]() ![]() ![]()
I have a "limited" dual WAN setup working with BitTorrent. A torrent client should be assigned to one WAN interface exclusively for it to work well. I use source local IP and source port ranges (set in advanced settings of µTorrent) to accomplish this, and have two clients seeding for each IP.
Automatic load balancing where the client can establish connections via both WANs didn't work well enough. Remote peers eventually saw both of my IPs and tried to establish new connections to the one that was currently not connected to them. When my peer received the new connection, the previous one having the same peer-id was terminated, the peer was "kicked" by my client, and the new connection took its time to ramp up to full speed (subject to latency and TCP slow start). The WAN interfaces kept switching around like this every few minutes. I use MikroTik "Per Connection Classifier" to distribute other connections (not bittorrent). The "both addresses" mode is the safest. A pair of hosts local and remote always use the same interface. |