updates to whonix in qubes is handled by a builtin routing to sys-whonix
if a clone of whonix-ws-15-dvm has networking set to a clone of sys-whonix … the “am i up to date?” check seems to still go sys-whonix
i am not knowledgeable enough on these subjects to thoroughly investigate unfortunately
i notice that sys-whonix auto-starts when the disposable tor-browser vm starts even if networking is set to another clone of sys-whonix
is this intended?
Hello, welcome to Whonix forums and thank you for your question!
To prevent unexpected autostart, please follow these instructions:
Sparing users from needing to change this setting requires upstream Qubes feature request way to find out name of gateway from witin VM - qubesdb-read /qubes-gateway-name [archive] or qrexec feature request: send this over qrexec to the NetVM I am connected to / sys-whonix hardcoded / sys-whonix unexpected autostart [archive] to get implemented.
1 Like
thank you! i followed instructions in “multiple workstations” and it was solved