On 5 Oct 2006 at 12:34, James Ray wrote:
> Jonas Björklund wrote:
> > Hello,
> >
> > On Thu, 5 Oct 2006, 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?
> >
> > On the director resource you can use DirAddresses.
> > On the client resource you can use FDAddresses.
> > On the storage resource you can use SDAddresses.
>
> This specifies listening addresses rather than bind addresses for out
> going communications doesn't it? Or have I misunderstood the meaning of
> these options?
I said "the documentation does say listen". I was wrong. From
http://www.bacula.org/rel-manual/Client_Fi_daemon_Configura.html:
FDAddress = <IP-Address> This record is optional, and if it is
specified, it will cause the File daemon server (for Director
connections) to **bind** to the specified IP-Address, which is either
a domain name or an IP address specified as a dotted quadruple. If
this record is not specified, the File daemon will **bind** to any
available address (the default).
The documentation for FDAddresses (note plural) mentions listen.
FDPort also mentions listen.
I think you want to use FDAddress. Here is what I used:
FileDaemon {
Name = ngaio-fd
FDport = 9102
WorkingDirectory = /home/bacula/db
Pid Directory = /var/run
Maximum Concurrent Jobs = 20
FDAddress = 192.168.0.68;
}
FYI:
# ifconfig fxp0
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=8<VLAN_MTU>
inet6 fe80::204:acff:fea3:703d%fxp0 prefixlen 64 scopeid 0x1
inet 192.168.0.67 netmask 0xffffff00 broadcast 192.168.0.255
inet 192.168.0.68 netmask 0xffffffff broadcast 192.168.0.68
ether 00:04:ac:a3:70:3d
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
I then ran this while running a status command:
# tcpdump -i fxp0 host 192.168.0.67 and not host 192.168.0.99
where 192.168.0.99 is the host I'm ssh'ing from...
No comms were captured.
--
Dan Langille : Software Developer looking for work
my resume: http://www.freebsddiary.org/dan_langille.php
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
