On Mon, 07 Apr 2025 14:49:31 +0200, Fabian Grünbichler wrote: > these checks also trigger for full-mesh setups where the corosync node > IP is intentionally configured on multiple interfaces, they might need > to be adapted for those or at least be configurable/opt-out. > > see https://forum.proxmox.com/threads/164603 > > filed upstream as https://github.com/kronosnet/kronosnet/issues/440 > > [...]
Applied, thanks! [1/2] (temporarily) revert routing checks commit: d012c2d77cd98dec26ed7b507cf1dd03173d6fba [2/2] bump version to 1.30-pve2 commit: 4b99fc1cc75a4ac8fb19611c0e95c68f115c2fb3 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel