proxmox-mirrors/mirror_corosync
1
0
Fork 0
mirror of https://git.proxmox.com/git/mirror_corosync synced 2025-08-06 17:35:28 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

This patch updates the wording for the bindnetaddr option

Browse Source 
in corosync.conf to explicitly state that you need to use
the network address, as opposed to "should always end in
zero", which is only correct for class C networks.

Regards,

Tim


-- 
Tim Serong <tserong@novell.com>


git-svn-id: http://svn.fedorahosted.org/svn/corosync/trunk@2856 fd59a12c-fef9-0310-b244-a6a79926bd2f
This commit is contained in:
Steven Dake 2010-05-19 05:26:13 +00:00
parent 0e9f0bfeb4
commit 9ad14156c6
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
man/corosync.conf.5
View File

@ -88,9 +88,11 @@ ring. The ringnumber must start at 0.
.TP
bindnetaddr
This specifies the address which the corosync executive should bind.
This address should always end in zero. If the totem traffic should
be routed over 192.168.5.92, set bindnetaddr to 192.168.5.0.
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