Force 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
Tor Browser has many security changes made to it from vanilla firefox to make sure your privacy is protected. This is an interesting project, but it can't provide that same level of security. A disclaimer about this really should be on the github page.
Lots of people use their vanilla browser when connected to a VPN, this is not just for Tor, neither does it claim to be an alternative to using Tor browser or Mullvad browser.
When randomly combining two things, it's usually more reasonable to assume you'll get the worst parts of both rather than the best. Especially when concerning safety, security, privacy, or other weakest link type endeavours.
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.
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.