QubesOS 4.3.1 is facing connectivity issues. VPN as Linux Router/Gateway requires a lot of Improving Potencial

NymVPN Report a bug
1

QubesOS 4.3.1 is facing connectivity issues. VPN as Linux Router/Gateway requires a lot of Improving Potencial.

Standalone with Nym VPN > connects over mixnet > routes to (via Provides Network setting) Whonix Gateway 18 > and this one routes to an Workstation VM / Standalone VM via Provides Network setting.

The Connectivity appears certain times functional , sometimes its timesouts , its generally considered slow (10sec-15sec page/loading time).

The Gateway had times when it run flawlessly.

Same concept with -

Standalone with Nym VPN > connects over dvpn > routes to (via Provides Network setting) Whonix Gateway 18 > and this one routes to an Workstation VM / Standalone VM via Provides Network setting.

This connection stops to work and doesnt receive the Net from Nym VM arriving to the Whonix Gateway VM. It has to do with the Routing rules , where mixnet functions over HTTP Tunneling , while dvpn creates its own tunnel infrastructure within the vm , not routing & attaching to a potencial whonix gateway.

I consider potencially that due to dvpn´s infrastructure , it might not be functional with the dvpn , so when thats the case , the mixnet infrastructure over whonix gateway 18 , workstation & qubes 4.3.1 should be massively improved and start to work flawlessly , otherwise Qubes os as a system with the whonix gateway can´t operate efficiently over nym vpn , in comparison to mac / windows

1 Like
2

Hi,

I had very similar issues. I determined that it is because NymVPN runs its own DNS server or something similar that does not allow outside connection (your client qubes) to query DNS. It could also be that the nftables rules generated by NymVPN do not allow that setup. I did try to circumvent them and it still did not work, therefore I am pretty certain that it’s not just the nftables rules.

You can check if it is DNS by using curl 1.1.1.1 and curl example.com. If curl 1.1.1.1 works but curl example.com doesn’t, DNS is most likely the issue.

I wanted to report this as well, but I didn’t find the time to do so. Also for me no single DNS request was ever successful. Not using DNS however always worked.

If the qube directly uses NymVPN however (it is installed inside the qube itself), then it did work.

1 Like