Re: [qubes-users] Re: Qubes 4.2: qubes-tunnel not working after upgrade (cannot resolve hostname)

2024-01-07 Thread r.wiesbach via qubes-users
ere? how can I make vpn leak-proof again with Qubes 4.2? On 1/7/24 22:49, r.wiesbach via qubes-users wrote: Hi, The forum post does not use qubes-tunnel and I do not use wireguard (but openVPN) - so I do not see how this post solves my issue?! On 1/6/24 12:06, code9n wrote: Hi,   This is on

Re: [qubes-users] Re: Qubes 4.2: qubes-tunnel not working after upgrade (cannot resolve hostname)

2024-01-07 Thread r.wiesbach via qubes-users
Hi, The forum post does not use qubes-tunnel and I do not use wireguard (but openVPN) - so I do not see how this post solves my issue?! On 1/6/24 12:06, code9n wrote: Hi,   This is on the Forum: https://forum.qubes-os.org/t/wireguard-vpn-setup/19141 cheers, On Saturday 6 January 2024 at

[qubes-users] Qubes 4.2: qubes-tunnel not working after upgrade (cannot resolve hostname)

2024-01-05 Thread r.wiesbach via qubes-users
Hi there, vpnVM and netVM both in-place upgrades from Q4.1 (and worked fine there). Template is fedora 38. NetVM is online, ping of vpn server hostname is fine within netVM. Ping and dig do not work within vpnVM, but afair that is intended (leak prevention of qubes-tunnel) I tried to restart