Tarek wroteMicrosoft.com :
Metric specifies the interface metric for the IPv4 protocol. When routes are chosen, the overall metric used to determine the preference is the sum of the route metric and the interface metric. Typically, the interface metric gives preference to a particular interface, such as using wired if both wired and wireless are available.
If a preference is not specified, the stack will choose an automatic metric, such as automatically preferring wired over wireless.
Looks like I got lucky here and had the same route metric (20). You can check the sum of both metrics using "print route" in the command prompt. However, it looks like you can modify the route metric . I will write how in the previous post.
Tarek wroteAka you will have a nonsensical network setup...very high number of lost packets and screwed routes = BAD
How did you jump to this conclusion? I tested my setup and downloaded a 5.8GB game on steam (which uses multiple connections when connecting to the server) in around 8.5 hrs on 2 1mbps connections instead of 17 hrs.
Let's assume Windows establishes connection 6 with the server on interface 1 . All packets for connection 6 will go through interface 1. It doesn't work randomly (sometimes through interface 1, sometimes through interface 2). So, there is no reason for packets to be lost or screwed routes. If you are using a single connection with the server (youtube stream or downloading from rapidshare as free user), then you will use 1 interface and remain with that interface until you finish (sream or download).
Prince wroteThe only way i know and tested is by making it on Mikrotik with 2 inputs cards and 1 output cards the method is called PCC (Per Connection Classifier)
Apparently there is another way with no extra hardware :).