GitHub - Nickguitar/VPNTabs: Force the traffic of a Firefox container tab to pass through VPN or Tor network
github.comForce the traffic of a Firefox container tab to pass through VPN or Tor network - GitHub - Nickguitar/VPNTabs: Force the traffic of a Firefox container tab to pass through VPN or Tor network
You must log in or register to comment.
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn’t great, if contents of the website are behind a paywall maybe copy them into the post
- Don’t promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
- 0 users online
- 57 users / day
- 383 users / week
- 1.5K users / month
- 5.7K users / 6 months
- 1 subscriber
- 2.97K Posts
- 74.6K Comments
- Modlog
I usually have a VPN client running in a container and then attach the browser instance to the network namespace of the container.
More information please?
Mmm do you know Linux containers? Like Docker containers, for example?
You need to understand Linux namespace and Linux containers to understand this trick. It isn’t super advanced to be honest, just a Linux feature that is very useful.
It can be overwhelming if you haven’t worked with containers before: https://youtu.be/fTcit7F5Bcg?si=rQlq0mJyapIpOlx8
Basically you can have multiple “network stacks” in the same machine, and they are isolated. By network stacks I mean things like the netfilter rules and the routing rules.
So, if you deploy a VPN inside a network namespace that isn’t the host’s namespace, the host won’t route the traffic to the VPN by default. Only the processes that are attached to that network namespace will process the network packets with the netfilter and routing rules of that namespace. So, if you only attach the Firefox process to the network namespace of the VPN, only the traffic generated by that process will go through the tunnel.
Here is an alternative Piped link(s):
https://youtu.be/fTcit7F5Bcg?si=rQlq0mJyapIpOlx8
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.