@Quben Iptables was replaced by nftable in 4.2, your problem may come from it.
After transitioning from version 4.1 to version 4.2 with documentation, which additional commands will i have to execute ?
Will the configured vpn-qube stop working on the new version and I have to configure it again?
i’m not an advanced user or can someone explain this step by step if i don’t change these ntfables then the internet won’t work, won’t it be safe?
will whonix 17 be ready to use and all you have to do is change the template and netqube in whonix 16 machines?
Have been using Qubes for about 5 years without any major issues. But since the 4.1 version up to the current testing Qubes-R4.2.0-rc5-x86_64.iso I can’t make the openvpn work in ether the sys-vm, nor any separate VM both with Network manager and without. I tried using both fedora-38 and debian-12, still no result. Seems either dns or firewall problem.
GitHub - tasket/Qubes-vpn-support: VPN configuration in Qubes OS stopped working in both the 4.1.2 and 4.2.0-rc5
I only managed to make the deb…
tasket:master ← 1cho1ce:replace-iptables-with-nftables
opened 07:01PM - 25 May 23 UTC
Qubes dropped iptables support and replaced it with nftables:
https://github.co… m/QubesOS/qubes-core-agent-linux/commit/28b95535c7cbd15543c804e822c0e4c997f5966e
This pull request replaces iptables with nftables.
Removed `allow established input` rules from `proxy-firewall-restrict` since they are already present in nft tables ip/ip6 qubes.
TODO: Need to think of a better way to check in `--check-firewall` in `qubes-vpn-setup` script if the forward drop rules are present (or `proxy-firewall-restrict` script finished successfully).
I hope it will help you
