There may be a SOCKS proxy server implementation that can route over a specific interface (the tunnel).
@Kyron One rather roundabout way would be to run a VM that forwards all outgoing traffic through the VPN. Then set up a SOCKS server on that machine and point your browser on your primary machine at that SOCKS proxy.
My laptop, Inspiron 1525, is SLOW. It is almost impossible to play Portal 2 and Portal 1 is laggy but still playable. I still managed to beat the game. Half Life 2 episode 2 is possibly even laggier than Portal 2. Minecraft is quite laggy.
My hard drive stores 136GB of memory. Here are my specs:...
Otherwise, you can take a look at the OSI model and TCP/IP, to start with.
(Note that the OSI model is theoretical, and the practical TCP/IP we use doesn't directly map to it.)
That goes for devices too. You know those boxes you get called "routers"? They're usually some physical connectors (layer 1), a switch (layer 2), a wireless access point (layer 2) and a router (layer 3), does NAT (layer 3/4) and often a web-based configuration interface (layer 7) in one box. Jam more features in, sell more.
Enterprise routers tend to be more strict :P
@JourneymanGeek Or a not-terribly-overpriced one? :P
As far as I'm concerned a gaming laptop is just an overpriced toaster.
I have my eyes on the Surface Pro 3 (or 4), though. Very expensive, but nice build, pretty powerful, and very portable.
@Kyron Yea, take a look at the OSI model for a general idea of how each layer is separated.
Basically, when you go up a layer you just expect the lower layers to handle things for you.
If you write a web browser, you (ideally) shouldn't have to worry about how the traffic is routed towards the destination, or how congestion control works, etc..
You just tell the lower-level libraries to open a socket to some ip:port combination and let them figure that out.
Of course, in the real world there's a lot of overlap. But it's nice to get the concepts clear first.
I've ranted a fair bit in here about those things called "routers", because people tend to mix up their capabilities, then they use a router where they really want a switch or access point, etc. (Introducing a router where you want a switch tends to segment the network so you can no longer directly communicate between two machines. Especially since consumer routers always imply NAT.)
runit is an init scheme for Unix-like operating systems that initializes, supervises, and ends processes throughout the operating system. Runit is a "reimplementation" of the "seminal" daemontools process supervision toolkit that runs on the Linux, Mac OS X, *BSD, and Solaris operating systems. Runit features parellelization of the start up of system services, which can speed up the boot time of the operating system.
Runit is an init daemon, so it is the direct or indirect ancestor of all other processes. It is the first process started during booting, and continues running until the system is...
There's also restartd and supervisord. I've used the latter before, and it's pretty easy.