Arno Lehmann wrote: > Hello, > > On 2/7/2007 9:26 PM, Martin Simmons wrote: > >>>>>>> On Wed, 07 Feb 2007 13:14:19 +0100, Arno Lehmann said: >>>>>>> >>> Hello, >>> >>> On 2/4/2007 10:34 PM, Florian Heigl wrote: >>> >>> >>>> Hi, >>>> >>>> I'm currently working on clustering bacula (howto follows as all >>>> quirks are removed) >>>> >>> That sounds interesting... >>> >>> >>> >>>> My requirement is running a bacula fd on each of the cluster nodes, >>>> and one for the cluster package. If someone thinks, this makes no >>>> sense, I'd be also glad to hear why. >>>> >>>> For the meantime I'm mostly concerned with making bacula listen to a >>>> specific ip. >>>> > .. > >>>> I haven't found out where I could influence that, how do I achieve this? >>>> >>> There's a feature request regarding that... you can influence it with >>> the editor of your choice and the build tools :-) >>> >> I think listening on a particular IP address is already implemented by the >> DirAddress directive (and similarly for the other daemons). The feature >> request is for outgoing connections to originate on a particular IP. >> > > Erm. Yes. Indeed. Good point. > > I obviously got that mixed up. Sorry if I created any unnessessary > confusion. >
It is the source address used by a client socket connection that is the problem for clusters, or at least for HA clusters. IP takeover works by creating an alias of the physical ethernet interface and assigning the "cluster" IP address to that alias interface. However, when a client socket is created without being bound to a particular IP, then the source IP address used will be automatically assigned according to the routing table. This will usually result in the source address being the IP assigned to the physical interface rather than the "cluster" IP that is assigned to the alias interface. This is not necessarily always a problem, but in some cases it is. For example, it is a problem when there is a firewall on the other end that only allows connections from the cluster IP. Another potential problem area is when the source IP doesn't match the X.509 certificate in a TLS connection. --- Josh Fisher > Arno > > >> __Martin >> >> ------------------------------------------------------------------------- >> Using Tomcat but need to do more? Need to support web services, security? >> Get stuff done quickly with pre-integrated technology to make your job >> easier. >> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >> _______________________________________________ >> Bacula-users mailing list >> Bacula-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bacula-users >> > > ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
