If Streaming’s Got Your Internet Screaming
Say you’ve got two internet connections, and you want to use one for League and the other to stream to Twitch. This could mean that you’re tethered to your phone, or you have ADSL and Cable.
You can do this pretty easily with static routes. You want to specify one particular destination should use the alternate connection using the ‘route’ command on Windows.
route add [destination] mask [networksize] [whichrouter] -p
(where -p means it will stay after its rebooted. failing to add -p will cause the route to be removed after a reboot. not adding -p is a good way of testing easily because if you fuck up you can just reboot and its back to normal)
If you have two connections on your home LAN, make one router 192.168.0.1 and the other 192.168.0.2. Turn the DHCP server off on the second one. If you’re streaming from an iPhone tethering, the [whichrouter] will be 172.20.10.1, not sure for android. To find out things like this, look at your computer’s routing table by typing “route print”. It’ll give you output looking like this:
The line with Destination of 0.0.0.0 Netmask 0.0.0.0 is your current default gateway – this is where ALL traffic will be sent, unless an override rule (called a static route) is put in. What we want to do is specify a default gateway for all traffic, then put in an override for LoL, or Twitch, or whatever.
To specify League of Legends (OCE ONLY, please look up server details for your region if you want to use it elsewhere) to a particular connection:
route add 18.104.22.168 mask 255.255.252.0 192.168.0.2 -p
route add 22.214.171.124 mask 255.255.254.0 192.168.0.2 -p
To specify Twitch Ingest to a particular connection (again this is OCE only, these are Twitch Sydney ingest. Please look up IPs for your appropriate destination):
route add 126.96.36.199 mask 255.255.255.255 192.168.0.1 -p
route add 188.8.131.52 mask 255.255.255.255 192.168.0.1 -p
route add 184.108.40.206 mask 255.255.255.255 192.168.0.1 -p
To remove one of these:
route delete [destination]
Please remember the Gateway IP is important as these are relative to YOUR home connection. It might be 10.0.0.1, it might be 172.20.10.1, who knows. Please use caution when attempting to do this!
These IPs are correct as of May 9th, 2016. You can look up these addresses for yourself for whatever program you want to use, being aware they may change in the future.