Skip to content

Update iptables-setup-docker-swarm.md #189

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.

Sign up for GitHub

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

Merged
noctarius merged 2 commits into from
Aug 21, 2026
Merged

Update iptables-setup-docker-swarm.md #189

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
81202eb
docs: tighten the storage node firewall snippet
schmidt-scaled Aug 10, 2026
1b1be18
docs: mark the NVMf port range as TCP and UDP in the port tables
schmidt-scaled Aug 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 5 additions & 7 deletions snippets/iptables-setup-docker-swarm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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
Expand Down
19 changes: 12 additions & 7 deletions snippets/network-port-table-sn.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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>
23 changes: 14 additions & 9 deletions snippets/network-port-table.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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>
Loading