Skip to content

Commit 17f988c

Browse files
committed
Merge branch 'pr/1539'
2 parents 2183a9b + 691ccc2 commit 17f988c

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

user/security-in-qubes/firewall.rst

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,7 @@ In order to allow networking from qube A (client) to qube B (server) follow thes
139139
140140
- Now you should be able to reach B from A – test it using e.g. ping issued from A. Note however, that this doesn’t allow you to reach A from B – for this you would need two more rules, with A and B swapped.
141141

142-
- If everything works as expected, then you should write the above nftables rules into firewallVM’s ``qubes-firewall-user-script`` script. This script is run when the netvm starts up. You should also write relevant rules in A and B’s ``rc.local`` script which is run when the qube is launched. Here’s an example how to update the script:
142+
- If everything works as expected, then you should write the above nftables rules into firewallVM’s ``qubes-firewall-user-script`` script (see section :ref:`Where to put firewall rules <user/security-in-qubes/firewall:where to put firewall rules>`). This script is run when the netvm starts up. You should also write relevant rules in A and B’s ``rc.local`` script which is run when the qube is launched. Here’s an example how to update the script:
143143

144144

145145

@@ -418,7 +418,7 @@ In this example, we can see 7 packets in the forward rule, and 3 packets in the
418418
419419
420420
421-
Once you have confirmed that the counters increase, store the commands used in the previous steps in ``/rw/config/qubes-firewall-user-script`` so they get set on sys-net start-up:
421+
Once you have confirmed that the counters increase, store the commands used in the previous steps in ``/rw/config/qubes-firewall-user-script`` so they get set on sys-net start-up (see section :ref:`Where to put firewall rules <user/security-in-qubes/firewall:where to put firewall rules>`):
422422

423423
.. code:: console
424424
@@ -477,7 +477,7 @@ Third step, code the appropriate new filtering firewall rule to allow new connec
477477

478478

479479

480-
Once you have confirmed that the counters increase, store these commands in the script ``/rw/config/qubes-firewall-user-script``
480+
Once you have confirmed that the counters increase, store these commands in the script ``/rw/config/qubes-firewall-user-script`` (see section :ref:`Where to put firewall rules <user/security-in-qubes/firewall:where to put firewall rules>`):
481481

482482
.. code:: console
483483
@@ -537,6 +537,8 @@ Where to put firewall rules
537537

538538
Implicit in the above example :doc:`scripts </user/advanced-topics/config-files>`, but worth calling attention to: for all qubes *except* those supplying networking, nftables commands should be added to the ``/rw/config/rc.local`` script. For service qubes supplying networking (``sys-firewall`` and ``sys-net`` inclusive), nftables commands should be added to ``/rw/config/qubes-firewall-user-script``.
539539

540+
Remember that you have to perform these changes in the corresponding disposable templates if the VMs are disposable VMs; otherwise the changes will get lost on restart of the VMs.
541+
540542
Firewall troubleshooting
541543
------------------------
542544

0 commit comments

Comments
 (0)