-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Max ~40 firewall rules #4018
Labels
R: duplicate
Resolution: Another issue exists that is very similar to or subsumes this one.
Comments
There is compatibility layer to make templates/standalonevms imported
from 3.2 working. And it fails there. Maybe this compat layer should be
optional, opt-in? Or at least opt-out...
|
You can simply leave a comment on a closed issue indicating that it should be opened, and we'll reopen it. |
Duplicate of #1570 |
This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you. |
andrewdavidwong
added
the
R: duplicate
Resolution: Another issue exists that is very similar to or subsumes this one.
label
Jun 20, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Qubes OS version:
4.0
Affected component(s):
qvm-firewall
Steps to reproduce the behavior:
Create a VM with more than ~40 firewall rules.
I directly edited firewall.xml and restarted the machine and/or qubesd for that.
Expected behavior:
VM starts.
Actual behavior:
VM doesn't start and some error about iptables is shown in journalctl.
If you do the same with ~30 rules, the VM starts.
General Notes:
Why is there a limit at all?
Related issues:
This is issue #1570, which was supposedly fixed, but apparently is not.
I however don't have the rights to reopen it.
The text was updated successfully, but these errors were encountered: