diff --git a/snippets/iptables-setup-docker-swarm.md b/snippets/iptables-setup-docker-swarm.md
index e43d81a5..3ac3c57b 100644
--- a/snippets/iptables-setup-docker-swarm.md
+++ b/snippets/iptables-setup-docker-swarm.md
@@ -1,14 +1,12 @@
-Simplyblock requires a number of TCP and UDP ports to be opened from certain networks. Following is a list of all
-ports (TCP and UDP) required for operation as a storage node.
-
-!!! note
-    The NVMf port range is used twice. It is TCP for NVMe-oF/TCP and UDP for NVMe-oF/RDMA.
+Simplyblock requires a number of TCP and UDP ports to be reachable from the control and the storage network. The
+following table lists every port required for operation as a storage node.
 
 {% include 'network-port-table-sn.md' %}
 
-The following script opens those ports with `iptables`.
+The following script opens those ports with `iptables`. No source address is enforced by it. Where a tighter rule
+set is required, the sources given in the Hosts and the Network column are applied on top.
 
-```bash title="Configuration script for iptables"
+```bash title="Opening the storage node ports with iptables"
 #!/usr/bin/env bash
 
 iptables -A INPUT -p icmp -j ACCEPT
diff --git a/snippets/network-port-table-sn.md b/snippets/network-port-table-sn.md
index e37028a6..ad430e14 100644
--- a/snippets/network-port-table-sn.md
+++ b/snippets/network-port-table-sn.md
@@ -1,7 +1,12 @@
-| Service              | Direction       | Hosts            | Network | Port(s)   | Protocol(s) |
-|----------------------|-----------------|------------------|---------|-----------|-------------|
-| ICMP                 | ingress         | control          | Control | -         | ICMP        |
-| storage-node-api     | ingress         | control          | Control | 5000      | TCP         |
-| NVMf (client-target) | ingress         | client           | Storage | 4420-4499 | TCP         |
-| NVMf (internal)      | ingress, egress | storage          | Storage | 4420-4499 | TCP         |
-| storage-node-RPC     | ingress         | storage, control | Control | 8080-9044 | TCP         |
+| Service              | Direction       | Hosts            | Network | Port(s)   | Protocol(s)             |
+|----------------------|-----------------|------------------|---------|-----------|-------------------------|
+| ICMP                 | ingress         | control          | Control | -         | ICMP                    |
+| storage-node-api     | ingress         | control          | Control | 5000      | TCP                     |
+| NVMf (client-target) | ingress         | client           | Storage | 4420-4499 | TCP, UDP <sup>(1)</sup> |
+| NVMf (internal)      | ingress, egress | storage          | Storage | 4420-4499 | TCP, UDP <sup>(1)</sup> |
+| storage-node-RPC     | ingress         | storage, control | Control | 8080-9044 | TCP                     |
+
+<span style="font-size: 0.8em;">
+<sup>1</sup> The NVMf port range carries both transports. NVMe-oF/TCP uses it over TCP, NVMe-oF/RDMA
+over UDP. Only the protocol of the transport in use has to be opened.
+</span>
diff --git a/snippets/network-port-table.md b/snippets/network-port-table.md
index c7c88a79..8ba0c864 100644
--- a/snippets/network-port-table.md
+++ b/snippets/network-port-table.md
@@ -1,9 +1,14 @@
-| Service              | Direction       | Hosts            | Network | Port(s)                         | Protocol(s) |
-|----------------------|-----------------|------------------|---------|---------------------------------|-------------|
-| ICMP                 | egress          | control          | Control | -                               | ICMP        |
-| storage-node-api     | egress          | storage          | Control | 5000                            | TCP         |
-| NVMf (client-target) | egress          | client           | Storage | 4420-4499                       | TCP         |
-| FoundationDB         | ingress, egress | control          | Control | 4500                            | TCP         |
-| control-plane-API    | ingress         | control          | Control | 80                              | TCP         |
-| storage-node-RPC     | ingress, egress | storage, control | Control | 8080-9044                       | TCP         |
-| Monitoring Stack     | ingress, egress | control          | Control | 12202, 13301, 13302, 9200, 9090 | TCP         |
+| Service              | Direction       | Hosts            | Network | Port(s)                         | Protocol(s)             |
+|----------------------|-----------------|------------------|---------|---------------------------------|-------------------------|
+| ICMP                 | egress          | control          | Control | -                               | ICMP                    |
+| storage-node-api     | egress          | storage          | Control | 5000                            | TCP                     |
+| NVMf (client-target) | egress          | client           | Storage | 4420-4499                       | TCP, UDP <sup>(1)</sup> |
+| FoundationDB         | ingress, egress | control          | Control | 4500                            | TCP                     |
+| control-plane-API    | ingress         | control          | Control | 80                              | TCP                     |
+| storage-node-RPC     | ingress, egress | storage, control | Control | 8080-9044                       | TCP                     |
+| Monitoring Stack     | ingress, egress | control          | Control | 12202, 13301, 13302, 9200, 9090 | TCP                     |
+
+<span style="font-size: 0.8em;">
+<sup>1</sup> The NVMf port range carries both transports. NVMe-oF/TCP uses it over TCP, NVMe-oF/RDMA
+over UDP. Only the protocol of the transport(s) in use has to be opened.
+</span>