Arch Linux

discord

Member

Registered: 2013-02-06

Posts: 7

Managing multiple network interfaces

On one network I use, some ports are blocked such as 6667. I have gotten around this by running a VM and using my cell phone as the primary network interface on the VM; via usb. However I would like to not have to launch a VM to visit specific sites and ports.

One way I can think of addressing this is to use route. However using routes depends on me setting the network IPs for the routes I wish to use. Then I need to go through the process of finding the IPs for all the hosts that I wish to set a route for, and setting them in a file. If I were trying to use freenode for example, I would then need to get the IP of each freenode IRC server and make a route for it.

I'm wondering if there is another way to deal with this issue. Furthermore, what if I wish some of my other traffic to be routed differently depending on which website I'm visiting? Then I need to add routes for each webserver? It could get really messy if they are using multiple servers. Maybe the VM is the best way to go? Is there a way to launch applications such as irssi and browsers to use a specific network interface and DNS server?

Pse

Member

Registered: 2008-03-15

Posts: 415

Re: Managing multiple network interfaces

If you only want to access Internet through one of those networks, then you could just remove the default gateway from one of them (the internal one). I believe it is also possible to set priorities to the routing table (which would allow you to give higher routing priority to your cell phone network), but I am not sure how to that.

If you are using NetworkManager and Gnome, there is a setting that allows you to disable the default gateway for any network easily.

bulletmark

Member

From: Brisbane, Australia

Registered: 2013-10-22

Posts: 683

Re: Managing multiple network interfaces

You can ssh into your PC at home setting up local port forwards as you do. You can also use dynamic proxy (-D) to automatically forward  web traffic and have no constraints on where you go or what you do with your browser. I forward my home router port 443 (normally https) to my PC port 22 (ssh) so that the port I am connecting outbound from the "secure" (i.e. usually corporate) network is much less likely to get intercepted.