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

3.1: qubes-iptables can not be disabled with qvm-service #1864

Closed
qjoo opened this Issue Mar 21, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@qjoo

qjoo commented Mar 21, 2016

Unlike in 3.0/qubes-firewall, 3.1 qubes-iptables does not provide that possibility.

Maybe add the following?

ConditionPathExists=/var/run/qubes-service/qubes-iptables
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 21, 2016

Member

This is different than qubes-firewall. qubes-iptables in R3.1 is equivalent to iptables in R3.0. Disabling it will break pretty much every other network-related Qubes functionality (DNAT for DNS, updates proxy, MASQUERADE for normal traffic etc). This is why no qvm-service for that exists.

If you want to disable it anyway and you know what you're doing, you can create systemd dropin /etc/systemd/system/qubes-iptables.service.d/50_disable.conf.

Member

marmarek commented Mar 21, 2016

This is different than qubes-firewall. qubes-iptables in R3.1 is equivalent to iptables in R3.0. Disabling it will break pretty much every other network-related Qubes functionality (DNAT for DNS, updates proxy, MASQUERADE for normal traffic etc). This is why no qvm-service for that exists.

If you want to disable it anyway and you know what you're doing, you can create systemd dropin /etc/systemd/system/qubes-iptables.service.d/50_disable.conf.

@marmarek marmarek closed this Mar 21, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment