On 2007-04-08T02:01:45, Simon Horman <[EMAIL PROTECTED]> wrote:
> [ Reposting as I sent it to linux-ha-devel instead of
> linux-ha-devel the first time around ]
>
> This seems to be a bit of an easy trap to fall into.
> Are there any fixes floating around? I was thinking
> that perhaps a cluster id of some sort would be a good
> idea. But I'm not sure.
It's only used as authorisation when "autojoin" is enabled. That is the
whole point of the autojoin method.
Users should not run distinct clusters on the same network media. (ie,
the same subnets + port when using bcast, nor the same mcast address +
port.)
When autojoin is not enabled, this will cause a bunch of errors. If they
have distinct shared secrets, they'll bail at the authentication step.
If they have _both_ the same key _and_ the same media _plus_ autojoin
enabled, they'll merge into one big cluster.
Sincerely,
Lars
--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
