proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-05-01 14:30:46 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

fix #4319: use corred port range for corosync v3.x

Browse Source 
corosync v2 used ports 5405 and 5404, but corosync v3 uses ports 5405-5412.

Signed-off-by: Marco Gabriel <mgabriel@inett.de>
This commit is contained in:
Marco Gabriel via pve-devel 2022-05-06 09:52:39 +02:00 committed by Fabian Grünbichler
parent 206107cfcf
commit 337a2d4238
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
pve-firewall.adoc
View File

@ -426,7 +426,7 @@ following traffic is still allowed for all {pve} hosts in the cluster:
* TCP traffic from management hosts to port 3128 for connections to the SPICE * TCP traffic from management hosts to port 3128 for connections to the SPICE
proxy proxy
* TCP traffic from management hosts to port 22 to allow ssh access * TCP traffic from management hosts to port 22 to allow ssh access
* UDP traffic in the cluster network to port 5404 and 5405 for corosync * UDP traffic in the cluster network to ports 5405-5412 for corosync
* UDP multicast traffic in the cluster network * UDP multicast traffic in the cluster network
* ICMP traffic type 3 (Destination Unreachable), 4 (congestion control) or 11 * ICMP traffic type 3 (Destination Unreachable), 4 (congestion control) or 11
(Time Exceeded) (Time Exceeded)
@ -435,7 +435,7 @@ The following traffic is dropped, but not logged even with logging enabled:
* TCP connections with invalid connection state * TCP connections with invalid connection state
* Broadcast, multicast and anycast traffic not related to corosync, i.e., not * Broadcast, multicast and anycast traffic not related to corosync, i.e., not
coming through port 5404 or 5405 coming through ports 5405-5412
* TCP traffic to port 43 * TCP traffic to port 43
* UDP traffic to ports 135 and 445 * UDP traffic to ports 135 and 445
* UDP traffic to the port range 137 to 139 * UDP traffic to the port range 137 to 139
@ -634,7 +634,7 @@ Ports used by {pve}
* sshd (used for cluster actions): 22 (TCP) * sshd (used for cluster actions): 22 (TCP)
* rpcbind: 111 (UDP) * rpcbind: 111 (UDP)
* sendmail: 25 (TCP, outgoing) * sendmail: 25 (TCP, outgoing)
* corosync cluster traffic: 5404, 5405 UDP * corosync cluster traffic: 5405-5412 UDP
* live migration (VM memory and local-disk data): 60000-60050 (TCP) * live migration (VM memory and local-disk data): 60000-60050 (TCP)
ifdef::manvolnum[] ifdef::manvolnum[]

2
pvecm.adoc
View File

@ -58,7 +58,7 @@ Grouping nodes into a cluster has the following advantages:
Requirements Requirements
------------ ------------
* All nodes must be able to connect to each other via UDP ports 5404 and 5405 * All nodes must be able to connect to each other via UDP ports 5405-5412
for corosync to work. for corosync to work.
* Date and time must be synchronized. * Date and time must be synchronized.