On Fri, 2009-04-03 at 16:42 -0400, Jeff Sturm wrote: > > -----Original Message----- > > From: linux-cluster-bounces@xxxxxxxxxx > > [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Mrugesh Karnik > > Sent: Thursday, April 02, 2009 11:09 PM > > To: linux-cluster@xxxxxxxxxx > > Subject: Re: Network Interface Binding for cman > > > > On Thursday 02 Apr 2009 21:34:12 Jeff Sturm wrote: > > > It binds to a multicast address. That address is bound to one > > > interface normally. > > > > Well, how do I specify which interface to bind that multicast > > address to? > > Generally speaking you would create a route entry, e.g.: > > ip route add multicast 224.0.0.0/4 dev eth1 scope link > > However I believe CMAN does not require this, and will automatically > bind to the same interface as the unicast address associated with the > node names you specify in cluster.conf. > > > I see the `bindnetaddr' directive in openais.conf man page. > > The multicast address (not interface) is automatically determined based > on your cluster name. Probably best to leave it that way unless you > have a specific reason to override it. > > Jeff Multicast and unicast sockets are explicitly bound to the interface that matches the ip address in the configuration. This removes the need for any default routes or problems with multicast binding to one interface while the unicast socket binds to another. regards -steve > > > -- > Linux-cluster mailing list > Linux-cluster@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
