From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Yes you can!
As you said, it’s got everything to do with routing and you don’t know how to do that yet.
Now’s a great time to learn!
If you’re on a time crunch, go ahead and use network namespaces under network manager to set up something like what you want as another user suggested.
If you have time to learn about the firewall and routing table rules, put on your wire rim sunglasses, pop a jungle cd in and crack open Linux Firewalls or some such book for nerds.
If you’re on a time crunch, go ahead and use network namespaces under network manager to set up something like what you want as another user suggested.
I'd love to, but I have no idea how >.< :D
I have a vague idea of what they are and what they do, but everything I've found assumes a level of understanding that I don't have yet. I've found this man page from searcing an example posted in another reply, and it's helped, but I'm still confused :)
https://manpages.ubuntu.com/manpages/trusty/man8/ip-netns.8.html
If you’re on a time crunch, go ahead and use network namespaces under network manager to set up something like what you want as another user suggested.
Is there a way to do this without NetworkManager?
I have only used them with network manager, but according to the manual it seems possible to use them free of network manager, and maybe even systemd!
That's amazing, I'm gonna have to dig a little deeper into that
Yes that's called routing.
You don't bind it to a NIC, you specify the destinations you want forwarded to each interface. Your VPN connection is just another interface.
If you're looking for good docs, you may want to Google split tunnel vpn, and also bone up on your networking.
A few static routes should get you what you need
And one doesn't even need two NICs, right.
One NIC is fine
yeah, VLAN interfaces and other kinds of virtual interfaces can also be used. I think you can even have multiple "sub interfaces", that will receive distinct IPs from the local DHCP server
Everything you said is true, but I don't think it's the complete answer the OP would like.
For instance if somebody goes to Google, on the raw network, and on the VPN. They would correctly expect that traffic to take two different routes, and come from different IP addresses
I think the key to this idea is that as long as the VPN only apps are running in docker containers, container networking can be used to restrict their traffic to the vpn.
Apps like qBittorrent support proxy connection options for this scenario without containers.
https://github.com/qbittorrent/qBittorrent/wiki/Explanation-of-Options-in-qBittorrent#proxy-server
goes to Google, on the raw network, and on the VPN.
You can't "go" to a destination on two networks in a single request. It's all packets on a wire, if it comes from two sources, it was two requests.
Unless you mean two different requests. As in while on the VPN everything is tunneled, and while not on the VPN it's not, but this is the opposite of what the OP was asking for. He wants the VPN on for some use cases, and off for others. That's split tunneling.
He'll likely wind up with difficulties around trying to figure out which destinations he doesn't want routed through the VPN, because there's no way to do it by protocol, since routing happens on layer 3, not 4 or 7. He'll likely need to know those address in advance.
Yes, that's what Gluetun is for. You create a Gluetun container and specify which containers should use it as the gateway in the compose file with:
network_mode: "service:gluetun"
Then you can open a shell in the container and run this to see if the container's IP is different from your own:
curl ifconfig.io
Make sure to try stopping the gluetun container and confirm your other containers lose network access.
There are plenty of guides about this if you search for "gluetun arr stack", like this random one I picked: https://www.smarthomebeginner.com/gluetun-docker-guide/
That has some steps outlining the basic gluetun configuration, how to put specific containers behind it, and test it.
Gluetun is for containers. OP is asking about routing.
Apologies for the slow reply :)
To clarify, I'm happy with using either, if my network traffic is split. Ideally I want to switch a lot of my programs to containers at some point, then switch to a better server OS. In the meantime though, I just want to get everything working together.
Qbittorrent has to be behind the VPN, and that's stopping my Minecraft servers from connecting to the outside world. If there's a way to force Qbittorrent to be behind the VPN while leaving a non VPN connection open, I'm happy to use it. I only mentioned Gluetun because I've heard of it, and I know that it's for keeping containers behind a VPN. I thought it might be the answer here :)
I'm pretty sure OP is asking about forcing containers to use the VPN through gluetun.
"If I set up qBittorrent and the Arrs as Docker containers, can I use Gluetun to bind just them to the VPN?"
I think they are just misunderstanding what Gluetun is for.
It also exposes a proxy (and a tun), most things you want behind a vpn can use a proxy.
Network namespaces!
ip netns exec namespace command
One namespace for surfshark, and anything you run in that namespace uses those rules
Network namespaces and policy based routing are black magic, IMO.
I've got a VPN set up on my router and separate VLANs set up for ordinary traffic and VPN traffic. A device doesn't need to support VPNs at all, I just connect it to the VPN VLAN and all its traffic goes over the VPN whether it likes it or not. I've got separate wifi SSIDs for each VLAN.
My desktop is connected to both VLANs with a network namespace set up for the VPN VLAN, so sudo vpn rtorrent runs rtorrent in the namespace that's connected to the VPN VLAN.
My setup is nice, but I wouldn't recommend it to anyone who doesn't want to learn quite a bit about networking.
Code dump for the curious?
I mean, it's bits of configuration all over the place that I've built up over time. It isn't a single script on one machine, and you'd need to change a lot of things if you weren't running Slackware. I can't really copy and paste it all.
Wait WHAT. Thank you.
Yes but why?
What's the VPN for?