Fix the your Vista RouteSentry routing problem
Just want to make a note as to why it appears to not be splitting local and international bandwidth sometimes.
The first thing I should mention is that to see if the routing tables have been set up correctly, type
in a cmd window. If the output scrolls for a few screens, then your routes are set up properly. If its just a few entries long, then something is wrong.
The other problem that a lot of VISTA users will have, is that you are not able to use RASPPPoE
My diagnosis is as follows.
1. You are using your router in half-bridge mode (duh)
2. You are connecting to your local account through the router.
3. You are connecting to your international account through the normal dial-up method.
4. You are running some form of p2p app, probably a bittorrent one.
5. The torrent client only knows about your dial-ip (international) account IP address, and is reporting THAT address to the tracker.
6. You are not a beautiful and unique snow-flake.
7. The tracker is reporting your international IP address to all the peers.
8. The peers are connecting to you via the reported international IP address.
9. All requests made to your client via that IP will be serviced through your dial-up account, and therefore, your international account. However your requests to local peers will still be routed through your router-connected account (local).
The Solution (Choose 1)
1. Swap your connections. ie. Router connects to international, Dial-up to local. (Will probably wreak havok on any international p2p downloads)
2. Check your torrent client settings, in uTorrent, there is an option to specify exactly which IP address should be reported to the tracker.
In uTorrent
Options->Preferences->BitTorrent. "IP/Hostname to report to tracker".
Get the IP from the routers admin page or however you like. If you are using a local torrent site (For Linux distros and OSS of course), your local IP address should be reported on your user page. The only problem you might have is that the IP WILL eventually change when your line reconnects, so you need to keep a close eye on it.
Pro-Tip: If you know of a local DynamicDNS service, and can configure your router to automatically update your IP whenever the connection resets, then simply enter your DDNS host name into the "IP/Hostname to report to tracker" field.
Lastly.
1. I didnt really need all those numbers, but its too late now, so bite me

2. Need moar info? Ask.