Is it bad to have had my sys-whonix connected to sys-net rather than sys-firewall?

I had to disable my wireguard vpn and instead routed sys-whonix through the sys-net qube rather than sys-firewall.

Been running a bunch of high risk stuff within disposable whonix workstations and just noticed this error on my part. I understand the sys-firewall has basic firewall config and sys-net holds the wifi logins. I shouldn’t have to wipe my system because of this right? I guess this would only be an issue if the sys-whonix was compromised but it’s not like I’ve ever touched that qube…

No worries, what’s coming out of your sys-whonix towards sys-net is already TOR traffic. The firewall in sys-firewall would be useless in that context anyway (since it works with target addresses and ports and your traffic is already encrypted and routed to a TOR entry node).

1 Like