I need a really solid and concrete way to lock down certain traffic to specific network interfaces.
I'm a little familiar with the "route" command on Windows, and have been trying to use it to route internet through one network interface (wireless) and then any addresses beginning with 10...* through another (wired).
Firstly I try to take away the automatic gateway of the wired connection by using netsh, something like:
interface ip set address "%network_connection_name%" static %IP_Addr% %Sub_Mask%
Where %IP_Addr% is the IP address given to that interface by the DHCP server. %Sub_Mask% is 255.255.255.0
Then I try to add routes like so:
route add 10.0.0.0 mask 255.0.0.0 %IP_Addr% metric 100 IF 16 route add 0.0.0.0 mask 0.0.0.0 %wireless_IP_addr% metric 1 IF 17
Where %wireless_IP_addr% is the IP address automatically given to the wireless network adapter.
This method SEMI works.
For about 30 seconds after I execute all those commands, my browser will happily use the wireless network as intended. But then for some reason I don't know nor understand, it seems to switch to the wired one.
Other programs, like Steam for example, continue using the wireless route, which is good. Then others, like my VPN software, try to use the wired one, which is bad.