Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign up4.0rc1 VM Settings window fails to load with error: FirewallModifiedOutsideError: it does not add up #3020
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
As a workaround there is qvm-firewall tool... |
marmarek
added
bug
C: qubes-manager
P: major
labels
Aug 13, 2017
marmarek
added this to the Release 4.0 milestone
Aug 13, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
kitambi
Aug 18, 2017
It appears that the trigger for this is actually the "Allow DNS Queries" checkbox. If you use qvm-firewall to remove the "special target" rule, then you're able to open the manager without this recurring. I was unable to check the "Allow connections to Updates Proxy" in my AppVM. I'm unsure of whether this just doesn't apply to AppVMs or if there's a bug selecting it, but the dialog disappears with rules added when OK is selected (and when qubes-vm-settings is reopened, the checkbox is empty).
kitambi
commented
Aug 18, 2017
|
It appears that the trigger for this is actually the "Allow DNS Queries" checkbox. If you use qvm-firewall to remove the "special target" rule, then you're able to open the manager without this recurring. I was unable to check the "Allow connections to Updates Proxy" in my AppVM. I'm unsure of whether this just doesn't apply to AppVMs or if there's a bug selecting it, but the dialog disappears with rules added when OK is selected (and when qubes-vm-settings is reopened, the checkbox is empty). |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
pugege
Sep 2, 2017
Unable to access VM settings of restored appvms from R3.2 because of this persistent
error. Disabling the DNS box in those appvms before 3.2 backup did not correct the issue. Will this problem be addressed in the upcoming 4.0-rc2? Was unable to qvm-firewall appvm del, the "special target" rule. Kindly advise the specific cli required to accomplish the work around.
Thanks
pugege
commented
Sep 2, 2017
|
Unable to access VM settings of restored appvms from R3.2 because of this persistent |
added a commit
to marmarek/qubes-core-admin
that referenced
this issue
Oct 16, 2017
added a commit
to marmarek/qubes-core-admin
that referenced
this issue
Oct 21, 2017
qubesos-bot
referenced this issue
in QubesOS/updates-status
Oct 21, 2017
Closed
core-admin v4.0.11 (r4.0) #284
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarta
Nov 17, 2017
Fixed in QubesOS/qubes-manager@dd990c0 - now, an error in firewall does not error out the whole settings window; furthermore, reading existing rules and writing rules have been also been improved.
marmarta
commented
Nov 17, 2017
|
Fixed in QubesOS/qubes-manager@dd990c0 - now, an error in firewall does not error out the whole settings window; furthermore, reading existing rules and writing rules have been also been improved. |
seandilda commentedAug 13, 2017
Qubes OS version (e.g.,
R3.2):4.0rc1Affected TemplateVMs (e.g.,
fedora-23, if applicable):fedora-25Expected behavior:
When clicking on 'VM Settings', the vm settings window should appear.
Actual behavior:
A window with the title 'Houson, we have a problem...' appears with the error message:
Expanding the details shows:
The firewall.xml for the VM is:
Steps to reproduce the behavior:
Edit a VM's firewalls in the UI, select 'Deny network access except...', select 'Allow DNS queries', add '10.0.0.0/8' with protocol of 'any'.
Close and try to open the VM settings window again.
General notes:
Related issues: