Hi
I have 2 sites connected using the wireguard, SITEA the wireguard is on the router, the SITEB the wireguard is directly on PVE. I see the traffic using tcpdump but the two site sees the other down
Here the coresync.conf
What I should check?
An example of tcpdup
If I restart a node on SITEA this what I see on SITEB
I have 2 sites connected using the wireguard, SITEA the wireguard is on the router, the SITEB the wireguard is directly on PVE. I see the traffic using tcpdump but the two site sees the other down
Here the coresync.conf
Code:
logging {
debug: off
to_syslog: yes
}
nodelist {
node {
name: pve-garage
nodeid: 1
quorum_votes: 1
ring0_addr: 192.168.50.35
}
node {
name: pve-hp
nodeid: 3
quorum_votes: 1
ring0_addr: 192.168.50.37
}
node {
name: pve-ss
nodeid: 2
quorum_votes: 1
ring0_addr: 192.168.50.36
}
node {
name: pve04
nodeid: 4
quorum_votes: 1
ring0_addr: 10.10.10.1
}
}
quorum {
provider: corosync_votequorum
}
totem {
cluster_name: Casa
config_version: 5
interface {
linknumber: 0
}
ip_version: ipv4-6
link_mode: passive
secauth: on
version: 2
}
What I should check?
An example of tcpdup
Code:
09:43:04.206266 IP 10.10.10.1.5405 > 192.168.50.37.5405: UDP, length 112
09:43:04.212355 IP 192.168.50.37.5405 > 10.10.10.1.5405: UDP, length 112
09:43:04.255262 IP 192.168.50.37.5405 > 10.10.10.1.5405: UDP, length 112
09:43:04.256299 IP 10.10.10.1.5405 > 192.168.50.37.5405: UDP, length 112
If I restart a node on SITEA this what I see on SITEB
Code:
Oct 08 09:45:32 pve04 corosync[4425]: [QUORUM] Sync members[1]: 4
Oct 08 09:45:32 pve04 corosync[4425]: [TOTEM ] A new membership (4.13e50) was formed. Members
Oct 08 09:45:32 pve04 corosync[4425]: [QUORUM] Members[1]: 4
Oct 08 09:45:32 pve04 corosync[4425]: [MAIN ] Completed service synchronization, ready to provide service.
Oct 08 09:45:41 pve04 corosync[4425]: [KNET ] link: host: 3 link: 0 is down
Oct 08 09:45:41 pve04 corosync[4425]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
Oct 08 09:45:41 pve04 corosync[4425]: [KNET ] host: host: 3 has no active links
Oct 08 09:45:42 pve04 corosync[4425]: [QUORUM] Sync members[1]: 4
Oct 08 09:45:42 pve04 corosync[4425]: [TOTEM ] A new membership (4.13e5c) was formed. Members
Oct 08 09:45:42 pve04 corosync[4425]: [QUORUM] Members[1]: 4
Oct 08 09:45:42 pve04 corosync[4425]: [MAIN ] Completed service synchronization, ready to provide service.
Oct 08 09:45:46 pve04 corosync[4425]: [KNET ] link: Resetting MTU for link 0 because host 3 joined
Oct 08 09:45:46 pve04 corosync[4425]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
Oct 08 09:45:46 pve04 corosync[4425]: [KNET ] pmtud: Global data MTU changed to: 1317
Last edited: