sys-firewall [sometimes] broken, does not function as ProxyVM in Qubes R3.2 RC1

Patrick · July 13, 2016, 9:19pm

Not a Whonix bug. But it affects Whonix. And could create some confusion. Therefore sharing it here.

sys-firewall broken, does not function as ProxyVM in R3.2 / xendriverdomain systemd service not enabled in Fedora

opened 03:28PM - 01 Jul 16 UTC

closed 11:53PM - 15 Jul 16 UTC

T: bug C: core r3.1-wheezy-cur-test r3.1-dom0-stable r3.1-fc21-stable r3.1-fc22-stable r3.1-fc23-stable r3.1-jessie-stable r3.1-wheezy-stable r3.1-stretch-stable r3.2-stretch-cur-test r3.2-fc23-stable r3.2-fc24-stable r3.2-dom0-stable r3.2-jessie-stable

#### Qubes OS version (e.g., `R3.1`): R3.2 (testing repository) #### Affected T…emplateVMs (e.g., `fedora-23`, if applicable): Probably any. --- ### Expected behavior: An arbitrary proxy VM with NetVM set to sys-firewall should just work. (ping, nslookup, wget, etc.) ### Actual behavior: An arbitrary proxy VM with NetVM set to sys-firewall does not work (ping, nslookup, wget, etc.). ### Steps to reproduce the behavior: Unclear, since it seems to be happening only to me. ### General notes: An arbitrary proxy VM (debian based) does not work behind sys-firewall. It however works behind sys-net. Although this breaks Whonix by default, this bug report has been produced independent from Whonix. (sys-whonix does not work with its NetVM set to sys-firewall but it does work fine when set to sys-net.) I have collected a ton of debug output. - https://www.whonix.org/wiki/Dev/Qubes#Qubes_R3.2_sys-firewall_broken_bug - http://archive.is/K9S0C --- #### Related issues: Perhaps https://github.com/QubesOS/qubes-issues/issues/1067.