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 upqubes_firewall_user_script is not executed at boot #1944
Comments
andrewdavidwong
added
bug
C: core
P: minor
labels
May 4, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
May 4, 2016
Member
This script is called only in ProxyVM (https://www.qubes-os.org/doc/config-files/). Is it the case?
|
This script is called only in ProxyVM (https://www.qubes-os.org/doc/config-files/). Is it the case? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
lorenzog
May 5, 2016
Ah, fair enough. I was expecting it to be executed in AppVMs too; I needed a NFS share to be mounted between a HVM and an AppVM so I needed to open a few ports on the AppVM's own firewall.
I was following this: https://www.qubes-os.org/doc/qubes-firewall/ and I thought I could apply the same reasoning to all VMs. To be hones I just found this https://www.qubes-os.org/doc/config-files/ which does mention proxy VMs, so never mind :)
lorenzog
commented
May 5, 2016
|
Ah, fair enough. I was expecting it to be executed in AppVMs too; I needed a NFS share to be mounted between a HVM and an AppVM so I needed to open a few ports on the AppVM's own firewall. I was following this: https://www.qubes-os.org/doc/qubes-firewall/ and I thought I could apply the same reasoning to all VMs. To be hones I just found this https://www.qubes-os.org/doc/config-files/ which does mention proxy VMs, so never mind :) |
lorenzog commentedMay 3, 2016
Qubes OS version (e.g.,
R3.1):3.1
Affected TemplateVMs (e.g.,
fedora-23, if applicable):fedora-23
debian-8
Expected behavior:
IPTABLES rules in /rw/config/qubes_firewall_user_script should persist across reboots
Actual behavior:
IPTABLES rules are not loaded from /rw/config/qubes_firewall_user_script
Steps to reproduce the behavior:
Place rules in /rw/config/qubes_firewall_user_script, e.g.:
iptables -I INPUT 2 -p icmp -j ACCEPTMake the script executable (
chmod +x ....)Reboot the VM.
Verify the rules are not loaded.
General notes:
A solution consists in adding this line to /rw/config/rc.local so that rc.local executes the firewall script automatically (don't forget to make rc.local executable)
/rw/config/qubes-firewall-user-scriptRelated issues:
Relevant labels: