On 5 Dec 2000, Karl Kleinpaste wrote:
> Jeremy Hansen <jeremy,AT,d3productions,DOT,net> writes:
> > I'm using 1.4.5 and basically I have a two node configuration working
> > nicely, when I try and add a third, the third kicks in and knocks out
> > one of the other nodes.
> I think you need to flesh out the concept "knocks out one of the other
> nodes." I have an active 3-node environment which works very well.
> So we have to ask, What problem is actually in evidence? Does
> ciped-cb die? Do the routes misinteract? Is ciped-cb attempting to
> reuse an interface number? There are a lot of things that might fall
> under "knocks out another."
Searched the mail archive, found the mails referring to running multiple
cipe daemons, created multiple option files, everything is now working
Red Hat's init script is not very friendly to this type of configuration
and reading multiple options files. Hopefully they'll fix that.
> Message sent by the cipe-l,AT,inka,DOT,de mailing list.
> Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
> Other commands available with "help" in body to the same address.
> CIPE info and list archive:
Well you should at least leave me the TV.