A more detailed explanation of what bindnetaddr is?

KoenDG

New Member
May 31, 2022
10
0
1
Apologies if this isn't the forum for this.

I'm testing things out with corosync and I'm confused by "bindnetaddr". I've posted a similar question here: https://serverfault.com/questions/1126948/a-more-detailed-explanation-of-what-bindnetaddr-is

Though there's probably not going to be an answer there. So I'm asking here.

The question:


Reading the documentation, I'm seeing:
Code:
bindnetaddr
This specifies the network address the corosync executive should bind to.
For example, if the local interface is 192.168.5.92 with netmask 255.255.255.0, set bindnetaddr to 192.168.5.0. If the local interface is 192.168.5.92 with netmask 255.255.255.192, set bindnetaddr to 192.168.5.64, and so forth.

This may also be an IPV6 address, in which case IPV6 networking will be used. In this case, the full address must be specified and there is no automatic selection of the network interface within a specific subnet as with IPv4.

If IPv6 networking is used, the nodeid field must be specified.


This doesn't really tell me anything.

If my machine has multiple physical network cards, or a bond with multiple vlans, do I have to set them all, or just the ones I'll be assigning ip addresses to?

From testing, it seems like it doesn't matter. Setting it to only 1 network still allows me to assign ip adresses to other ones.

Can someone give more detail on the purpose of this?



What is the purpose of `bindnetaddr`? Is it just ip ranges that are expected to exist on the machine? Or just one ip range?

I find the documentation isn't clear on any of this.
 
@KoenDG I was looking into this today also.

The Cluster I manage has been upgraded over the years from V3.. to the current V8.

The quote you have referenced is from this page;
https://pve.proxmox.com/wiki/Separate_Cluster_Network#bindnetaddr
or
https://linux.die.net/man/5/corosync.conf
However there is a Note at the TOP of the Proxmox page;
Note: Article about old Proxmox VE 4.x and 5.x releases. Starting from Proxmox VE 6.x this is part of the reference documentation see https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pvecm_redundancy

Looking at the current Proxmox documentation the bindnetaddr is removed from the example of adding a redundant link to an existing cluster.
https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pvecm_redundancy

I tried removing parameter from my cluster corosync file my cluster is still healthy.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!