Workaround when using the Whonix testers repository…
Systemd leftovers from Whonix 11’s fault. To unbreak after updating from testers repository… Run the following commands in your TemplateVMs.
Then shutdown and restart sys-whonix and whonix.
Working on a fix.
[hr]
More technical information:
In Whonix 11 -> Whonix 12 updated images, due to the left overs… qubes-firewall.service conflicts with qubes-whonix-firewall.service. Neither one gets load. No worries. Even without firewall being load, no leaks are possible. (IP forwarding is disabled, traffic isn’t just forwarded to clearnet by anything.)
cat /lib/systemd/system/qubes-firewall.service.d/40_qubes-whonix.conf
[Unit]
ConditionPathExists=!/usr/lib/qubes-whonix
sudo service qubes-whonix-firewall status
● qubes-whonix-firewall.service - Qubes Whonix firewall updater
Loaded: loaded (/lib/systemd/system/qubes-whonix-firewall.service; enabled)
Drop-In: /lib/systemd/system/qubes-firewall.service.d
└─40_qubes-whonix.conf
Active: inactive (dead)
start condition failed at Thu 2015-11-05 13:21:40 UTC; 15min ago
ConditionPathExists=!/usr/lib/qubes-whonix was not met
sudo service qubes-firewall status
● qubes-whonix-firewall.service - Qubes Whonix firewall updater
Loaded: loaded (/lib/systemd/system/qubes-whonix-firewall.service; enabled)
Drop-In: /lib/systemd/system/qubes-firewall.service.d
└─40_qubes-whonix.conf
Active: inactive (dead)
start condition failed at Thu 2015-11-05 13:21:40 UTC; 17min ago
ConditionPathExists=!/usr/lib/qubes-whonix was not met