Sean,
Have you had a look at the broadcast: yes option? Apparently not in the
man pages, but here is what my corosync.conf looks like:
# Please read the corosync.conf.5 manual page
compatibility: none
totem {
version: 2
secauth: off
threads: 0
crypto_accept: new
interface {
ringnumber: 0
bindnetaddr: 192.168.100.5
broadcast: yes
mcastport: 5405
}
}
I have only tested on Linux platforms and the feature is somewhat
experimental.
Regards
-steve
On Sun, 2009-07-26 at 21:20 -0700, Sean Chittenden wrote:
> Resolving the broadcast address for FreeBSD. Two possible solutions:
>
> 1) 255.255.255.255 doesn't receive any special handling by FreeBSD
> (and a handful of other OS'es, iirc) in terms of binding an
> interface's broadcast address. Any thoughts on adding a broadcast
> config directive?
>
> 2) Other option is to resolve the correct broadcast in user space.
>
> Are there any patches kicking around that do either of these
> remedies? -sc
>
>
> --
> Sean Chittenden
> [email protected]
>
>
>
> _______________________________________________
> Openais mailing list
> [email protected]
> https://lists.linux-foundation.org/mailman/listinfo/openais
_______________________________________________
Openais mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/openais
