Skip to content
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

Closed
3hhh opened this issue Jun 19, 2018 · 4 comments
Closed

Max ~40 firewall rules #4018

3hhh opened this issue Jun 19, 2018 · 4 comments
Labels
R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one.

Comments

@3hhh
Copy link

3hhh commented Jun 19, 2018

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.

@marmarek
Copy link
Member

marmarek commented Jun 19, 2018 via email

@andrewdavidwong
Copy link
Member

I however don't have the rights to reopen it.

You can simply leave a comment on a closed issue indicating that it should be opened, and we'll reopen it.

@andrewdavidwong
Copy link
Member

Duplicate of #1570

@andrewdavidwong andrewdavidwong marked this as a duplicate of #1570 Jun 20, 2018
@andrewdavidwong
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one.
Projects
None yet
Development

No branches or pull requests

3 participants