this post was submitted on 20 Oct 2024
66 points (98.5% liked)
Linux
48317 readers
716 users here now
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.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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 Even if the destination target IP address is the same
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.
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
Apologies for the slow reply :)
These are the things that I don't understand. When you say I need to specify the destinations, does that mean the destination of the traffic, like lemmy.dbzer0.com, or the destination network interface like tun0 or enp2s0?
I'm searching for split tunnel VPN, but the majority of results are either sales sites, or Stack Overflow with no confirmed answers.
I've been having a bit more luck with this page after searching for Jet's answer below:
https://manpages.ubuntu.com/manpages/trusty/man8/ip-netns.8.html
but I'm still confused >.<
Routing takes place on layer 3 (ip) so destinations are ip networks and hosts.
Each packet you create has a destination IP. Your computer looks at your route table to see where it goes by matching the destination ip with each network. It will be sent to the most specific match first and your default gateway last.
If you're default gateway is you're vpn server via your vpn interface then you just need to add more specific route for destinations of interest through a different gateway (you're router) via the physical interface
~~Bro. Get a handle on the difference between "your" and "you're." Even if English is a second language, it's worth knowing.~~
Now everything makes sense.
Canadian with a shitty mobile keyboard, that's all.
Swipe keyboard. It picks random yours, and I'm exhausted from flying all day so I didn't proof read.
Even if that's the case, the whole thing made no sense until you corrected it. Now it does.
I gotta agree on this. It's so weird to read a piece when these 2 are mixed up
I mean is there a material pronunciation difference between the two conjunctions? I don’t think so, but I can still somehow manage to work out what people mean when they say use “your” and “you’re” in the same spoken sentence.
There are differences in pronunciation, at least for my southern British dialect. "Your" is said "yorr". "You're" is said "yeur" and is far closer to the "you are" it comes from. It's just said at speed blending the words.