Description of problem:
ip addr add 192.168.2.111 peer 192.168.2.200 dev eth0
in corosync conf:
Can't bind ...
Interface [192.168.2.200] is up
^^^ At least linux netaddr -> ip doesn't work
Version-Release number of selected component (if applicable):
point-to-point doesn't work
is netmask set properly?
(In reply to comment #1)
> is netmask set properly?
Steve, problem is point-to-point and I believe you trust me that I'm able to correctly configure network ;). I've already found main problem.
Created attachment 585210 [details]
Patch to use IFA_LOCAL instead of IFA_ADDRESS.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
IP is configured as peer-to-peer (netmask /32). Corosync is started with bindnetaddr to configured IP address.
Corosync is unable to create membership. Corosync sockets are bound to PEERs address instead of local one.
Use correct information about local ip.
Corosync starts and run correctly.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.