Hello, This bug was posted on Qubes forums. Worked fine so far in Qubes-Whonix 3, 4.1, 4.2. Suddenly stopped working after last Whonix update. Any ideas?
1 Like
No changes were made to networking. Unlikely caused by update.
Whonix-Workstation anon-whonix is functional? Try that first.
Then try with a Debian HVM. Functional?
Documentation:
Otherwise you can run the checklist:
1 Like
Test results:
Anon-Whonix → sys-whonix (working)
Debian12 → sys-whonix (working)
Windows → sys-whonix (not working)
Windows → sys-vpn → sys-whonix (working, this is funny)
It is a Qubes/Xen bug then. They also released updates last week to the Whonix templates. But it is a bug for sure.
No other changes were made to Windows and Whonix-Gateway templates other than applying last updates (both Whonix and Qubes updates).
2 Likes
No idea.
Search Qubes issue tracker and report a bug if it’s not already filed. Will require a good report describing everything you’ve already tested.
1 Like
i have also had a recent unexplained network problem with getting an hvm vm to connect using sys-whonix and am not sure if it’s user error, qubes error, or sys-whonix bug
1 Like
1 Like
For months i have been using windows hvm with sys-whoonix no problem. Today i learned that the whole time the whonix respo has not been enabled soo whonix templates not updating properly. Now i just updated both gateway and workstationwith whonix and kicksecure repo (stable) turned on and all of a sudden windows HVM networking is not working. It was working last night just fine.
I have restored my old whonix gateway template and switched back to that and it works fine. This template does not receive any whonix/kicksecure updates.
Anybody have any fixes that do not require you to use a whonix gateway template that receives no updates from whonix/kicksecure?
1 Like