Pada
Executive Member
There are many people out there looking for a solution on how to run uTorrent in the background, using only local cap, whilst allowing other applications to use international (and/or local) cap.
Using RouteSentry or any other form of traffic splitting works well in most cases, although as soon as the peer/tracker's IP address falls out of the local IP range set used by the application/script to split the traffic, uTorrent will consume international bandwidth.
I would appreciate it if I can get testers for Solution #4, where you don't split traffic in the normal fashion, instead only routing uTorrent's traffic through the local account. You could of course use normal traffic splitting AND that method to force uTorrent to use only local bandwidth. I have done a quick test and it seemed to be working nicely.
Here are my solutions:
Solution #1: (safest solution)
Solution #2: (safe solution - should be as safe as with Solution #1)
Solution 3: (fairly safe - if uTorrent & traffic splitting is correctly utilized)
Solution #4: (safer than solution #3 / same safety level as Solution #2)
This solution is my attempt on routing all the uTorrent traffic through the local account. I hope to stop all international bandwidth being used by uTorrent, which can happen in the case of Solution #3 where your IP filter & list of local routes isn't including the local peer/tracker.
I'm using uTorrent, my Traffic Splitter app & FreeProxy.
FreeProxy setup:
Disclaimer/Warning:
Since I haven't fully tested this method yet...
I can't say for sure that this will PREVENT the international connection from being used at all OR that only uTorrent will be using the local only connection where as all the other applications will be using the international traffic
If someone could test this thoroughly, I would appreciate it
If you've tried out my solution 4, give a rough description on your configuration that you used to test it. eg. router in bridging mode; dialing both connections from the PC running uTorrent; using no IP filter; left "Use default gateway on remote network" checked; used Traffic Splitter to make the international connection the default connection & selected the local connection for the local interface
Using RouteSentry or any other form of traffic splitting works well in most cases, although as soon as the peer/tracker's IP address falls out of the local IP range set used by the application/script to split the traffic, uTorrent will consume international bandwidth.
I would appreciate it if I can get testers for Solution #4, where you don't split traffic in the normal fashion, instead only routing uTorrent's traffic through the local account. You could of course use normal traffic splitting AND that method to force uTorrent to use only local bandwidth. I have done a quick test and it seemed to be working nicely.
Here are my solutions:
Solution #1: (safest solution)
Run uTorrent on a separate PC that is connected to ONLY a local account. If you run out of cap, uTorrent would stop downloading & uploading
Solution #2: (safe solution - should be as safe as with Solution #1)
Setup a Socks5 (or HTTP) proxy on a separate PC on the LAN that is ONLY connected to a local account.
Then setup uTorrent to use that Socks5 proxy for all the traffic (incl. peer-to-peer).
If you have managed to configure uTorrent to route all the traffic through the proxy server, then it would be as safe as Solution #1.
Then setup uTorrent to use that Socks5 proxy for all the traffic (incl. peer-to-peer).
If you have managed to configure uTorrent to route all the traffic through the proxy server, then it would be as safe as Solution #1.
Solution 3: (fairly safe - if uTorrent & traffic splitting is correctly utilized)
Using the router in half-bridge mode (aka bridging mode with PPPoE passthrough enabled), where you let the router dial the local only connection.
The safety of this solution depends on how good your IPFilter for uTorrent is and the specific torrent tracker that you're using AND on the list of local routes that you're using for splitting traffic.
Next step would be to run uTorrent in combination with RouteSentry or another method of traffic splitting, where you dial your international connection from the PC (and select it as your international interface in RS) and select your Ethernet (LAN/WiFi) adapter as the local interface in RS.
The cool thing about this solution is that when your local cap is depleted, the routes to the local sites would still be in tact, denying access to all local sites. This would cause uTorrent to stop downloading & uploading too.
The safety of this solution depends on how good your IPFilter for uTorrent is and the specific torrent tracker that you're using AND on the list of local routes that you're using for splitting traffic.
Next step would be to run uTorrent in combination with RouteSentry or another method of traffic splitting, where you dial your international connection from the PC (and select it as your international interface in RS) and select your Ethernet (LAN/WiFi) adapter as the local interface in RS.
The cool thing about this solution is that when your local cap is depleted, the routes to the local sites would still be in tact, denying access to all local sites. This would cause uTorrent to stop downloading & uploading too.
Solution #4: (safer than solution #3 / same safety level as Solution #2)
This solution is my attempt on routing all the uTorrent traffic through the local account. I hope to stop all international bandwidth being used by uTorrent, which can happen in the case of Solution #3 where your IP filter & list of local routes isn't including the local peer/tracker.
I'm using uTorrent, my Traffic Splitter app & FreeProxy.
FreeProxy setup:
- Socks 5 server
- Local binding: Ethernet Adapter (IP 10.0.0.4)
- Remote binding: WAN (PPP/SLIP) interface (IP local only PPPoE connection)
- Allow incoming connections: checked
- Incoming connections: (same as Remote binding)
- Connection:
- Socks5 proxy: 10.0.0.4:1080
- Resolve hostnames through proxy: checked
- Use proxy server for peer-to-peer connections: checked
- BitTorrent:
- Enable DHT Network: unchecked
- Enable DHT for new torrents: unchecked
- Enable Local Peer Discovery: unchecked
- Enable Peer Exchange: unchecked
- Advanced: I'm also using an IP filter for extra measure.
If someone can verify that it blocks all international traffic without using an IP filter, I would appreciate it very much!
- Set the international connection to be the default connection, using the command-line app: "route.exe add 0.0.0.0 mask 128.0.0.0 <international connection's (gateway) IP>" AND "route.exe add 128.0.0.0 mask 128.0.0.0 <international connection's (gateway) IP>"
You could use my Traffic Splitter application for this instead, by selecting the international connection as the International interface. - Set the local only connection to route all destinations too, using by configuring the local only connection to be the default gateway. To do this, simply ensure that the "Use default gateway on remote network" option is checked. If you're using RouteSentry, leave that option unchecked.
You could use my Traffic Splitter application for this, by adding 0.0.0.0,0.0.0.0 to the Auxiliary routes and then selecting the local only connection for the Auxilary (and/or Local) interface(s), but I would advice you to rather check that default gateway option on the local connection's TCP/IP v4 properties and then not selecting the local only connection in my application OR only selecting it for the local interface
Disclaimer/Warning:
Since I haven't fully tested this method yet...
I can't say for sure that this will PREVENT the international connection from being used at all OR that only uTorrent will be using the local only connection where as all the other applications will be using the international traffic
If someone could test this thoroughly, I would appreciate it
If you've tried out my solution 4, give a rough description on your configuration that you used to test it. eg. router in bridging mode; dialing both connections from the PC running uTorrent; using no IP filter; left "Use default gateway on remote network" checked; used Traffic Splitter to make the international connection the default connection & selected the local connection for the local interface
Last edited: