Why QubesOS need some control over OpenVPN set ups? while other VPNs can work from the box? what is the sense of it?

Hi, to my understanding, 10.139.1.* are used by Qubes to forward dns requests to the last netvm, and this VM use its own dns configuration (resolv.conf) to resolve the DNS request.
It should work with mirage-fw as well as with sys-firewall (at least on my laptop), I’ve managed to get sys-net using a mirage-dns unikernel to resolve the request and forward back to the original AppVM.
I never used openvpn, but I have the following configuration : sys-net ← mirage-fw ← sys-vpn ← AppVM with both openconnect or openfortivpn as client.
Would you mind to describe what is not working with mirage-fw ?

1 Like