VPNHotspot VS namespaced-openvpn

I managed to obtain the 2 parts by using a New-york VPN (NordVPN) on an old rooted android phone with VPNHotspot and setting it up as a repeater.

Either root (with all the hassle that entails with apps that don't like running on a rooted phone) then use apps like https://github.com/Mygod/VPNHotspot or change the custom ROM to one that supports that feature, such as LineageOS (I think S21 is supported, you'll have to research it yourself)

Root + VPN Hotspot. Read through that page well before rooting just for that, though. It's not always super straightforward.

Set up a VPN'ed hotspot from Android and connect to it from the Quest. You will need to have a rooted Android phone. Use VPNHotspot.

Only if the phone is rooted: https://github.com/Mygod/VPNHotspot

Yeah, you'd need to root your Android (do not recommend it) and use it with https://github.com/mygod/vpnhotspot

Thanx, any idea of any apps that don’t require root that is able to hide hotspot usage? This is the only one that I know of but requires root https://github.com/Mygod/VPNHotspot/releases

When you get a root check out this app https://github.com/Mygod/VPNHotspot and let us know how it's performing. I'm about doing same thing with my old 6T.

I currently use an app that makes my tethering data look like on-device data (VPN Hotspot).

If I understand correctly, VPN Hotspot may be what you need.

Network namespaces are a really nice feature for me. I use them for a few things. They are a simple and foolproof way of running programs in VPNs without having the whole system use the VPN, and you can have multiple of them, and even chain/nest them (foolproof as long as you remember to run it in the network namespace, such as a wrapper script or systemd service). WireGuard remembers the namespace it was created in and uses it for connecting to the VPN endpoint, so if you create it in your init namespace, then move it to a different namespace, programs in that different namespace can use the WireGuard interface which connects to the VPN endpoint using the original connection. Programs have no direct access to the internet if the VPN interface disappears. (https://www.wireguard.com/netns/#ordinary-containerization). There is also https://github.com/slingamn/namespaced-openvpn for OpenVPN.

namespaced-openvpn can do this.

Even found namespaced-openvpn, a ready-made solution for this problem.

It would depend of your device but on linux you can use namespaced-openvpn (https://github.com/slingamn/namespaced-openvpn). It would let you connect to vpn1 and running vpn2 over vpn1 for example.

There are ready-made solutions like namespaced-openvpn for OpenVPN. See #27 when using with libtorrent-rasterbar. For WireGuard, you can read up on https://www.wireguard.com/netns but it might be a bit confusing. I've easily made my own script which implements this so that it creates a network namespace, creates a WG interface, moves the WG interface into the new network namespace, then configures the WG interface (which is now in the new network namespace).

If you don't feel like using docker, this is an awesome script to seamlessly launch OpenVPN and spawn a new network namespace with only the tun interface in it. Handy af.