James McMurray

I think the issue is that you have installed it for your user, but this will try to run as root, so maybe it isn't on the path in that...

Can you check the content of `/etc/netns/NAMESPACENAME/resolv.conf` when running? I remember having issues with the ProtonVPN DNS when writing the sync code - https://github.com/jamesmcm/vopono/blob/master/src/providers/protonvpn/openvpn.rs#L39

That inet stuff is fine, and it seems alright using the internal DNS server (i.e. that will only be accessible within the tunnel). Just to check if you run bash...

Apparently `block-outside-dns` should only affect Windows clients anyway. It might be blocking on missing credentials? In any case, can you try with Chromium or another browser? In case it's due...

I just tested this with the Japan free OpenVPN server and it worked fine for me with `google-chrome-stable`: 

Yeah, I just used `vopono sync`, chose the free one and logged in. Then ran `google-chrome-stable` with vopono. Maybe try to check if anything is overriding the DNS somehow?

It's strange, I use NetworkManager myself, and have [openresolv](https://wiki.archlinux.org/title/Openresolv) installed but it's not an issue at all. I don't see anything weird on the Wiki page either - https://wiki.archlinux.org/title/Domain_name_resolution

Thanks, I can try to test it by switching to systemd-resolved.

If you're using systemd-resolved, it'd be great if you could try vopono 0.9.0 now thanks to PR #144 from @niki-on-github

Hey, In theory any child process should also spawn in the network namespace. It works for me using nftables, Wireguard and normal rules (killswitch enabled, UDP tunnels - the standard...