>>>>> On Thu, 05 Oct 2006 10:47:00 -0400, Josh Fisher said:
>
> Kern Sibbald wrote:
> > On Thursday 05 October 2006 15:03, James Ray wrote:
> >
> >> Kern Sibbald wrote:
> >>
> >>> On Thursday 05 October 2006 11:02, James Ray wrote:
> >>>
> >>>> All,
> >>>> I am wanting the communications from bacula to come out of the same IP
> >>>> address I have DirAddress set as in the Director {} resource. This is
> >>>> not the default system address.
> >>>>
> >>>> I have just tried to do this with IPTables and source NATing but due to
> >>>> a bug in the Fedora Kernel (or what seems to be) I get a panic ;(
> >>>>
> >>>> Any ideas other than me writing a quick patch to do it?
> >>>>
> >>> Could you explain in detail why you would want to do this?
> >>>
> >>> Could you explain what components you are talking about when you say you
> >>>
> > are
> >
> >>> wanting "communications from bacula"? (Director, Console, File daemon,
> >>> Storage daemon), and to where? (each of the daemons carry on several
> >>> different kinds of network conversations -- Dir=3, Console=1, FD=2,
> >>> SD=2).
> >>> See the daemon interconnection picture in the beginning of the manual for
> >>>
> > the
> >
> >>> details of who talks to whom.
> >>>
> >>> Also, could you explain how it is possible to use a different address
> >>> than
> >>>
> > the
> >
> >>> one which is "assigned" to your computer?
> >>>
> >>>
> >> We have a concept of a system address (the machine itself) and a service
> >> address (one for each service, say .2 == an apache service, .3 == an
> >> bacula service, .4 == a dns service, where as .1 is a _system_ address)
> >> all the interfaces will be on the same machine.
> >>
> >> So any communications coming _from_ the bacula service need to come out
> >> of .3 and any connections to the bacula service need to head onto .3 also.
> >>
> >> What I have seen (only on my breif testing) is that the listen address
> >> is the .3 address (as I set in DirAddress) but the outcoming connections
> >> from the bacula-dir to the bacula-fd across the network originate for
> >> the system default address of .1...
> >>
> >
> > I have no idea how to control which address is used for outgoing
> > communications other than by configuring your network gateway to go through
> > the preferred device, which may not do exactly what you want.
> >
> > In any event, unless I am misunderstanding something, Bacula has no
> > mechanism
> > for controlling outgoing addresses.
> >
> >
> A listening socket doesn't perform 2-way communications, and so can be
> "bound" to multiple interfaces. It is the socket returned from accept()
> that is bound to a particular interface, (the interface which received
> the connection request). So DIRAddress affects which interfaces DIR
> listens for connections on, but has nothing to do with any client
> connections that DIR makes to other daemons. It is possible to bind a
> client socket to a particular interface and/or port previous to the
> connect() call, so in that way bacula COULD control the outgoing
> address, but I don't see why it should want to do it's own routing.
Firewall reasons maybe? E.g. if you want packets to come from a particular IP
address.
__Martin
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
