On 2011-03-15, Josh Fisher <jfisher AT pvct DOT com> wrote:
> On 3/15/2011 4:42 AM, Gavin McCullagh wrote:
>>> Try using something like:
>>>       FDAddresses {
>>>          ip = {
>>>             addr = hostname
>>>          }
>>>       }
>>>
>>> The ip keyword of FDAddresses allows selection of IPv4 and IPv6 addresses.

Unfortunately, it does not seem to work (at least around here). 

Looking by the documentation it might be bug, or it might be that documentation 
is wrong and "ip" is actually an alias for "ipv4" only, and NOT ipv4+ipv6 
superset..

So, specifying ip { addr = my.fqdn.name } binds only to IPv4 address (while
"host my.fqdn.name" return both A and AAAA records)

To make it listen to both IPv4 and IPv6 specified by FQDN hostname, I must
instead do:

  FDAddresses  = {
    ipv4 = { addr = my.fqdn.name }
    ipv6 = { addr = my.fqdn.name }
  }

Then it works (binds to both IPv4 and IPv6 specific addresses corresponding
to my.fqdn.name). It would indeed by nicer if documentation worked as
advertised and I could do just:

  FDAddresses  = {
    ip = { addr = my.fqdn.name }
  }

but, it does not seem to work... I do not know if that is a bug in the code,
or in the documentation to be found at
http://www.bacula.org/5.0.x-manuals/en/main/main/Client_File_daemon_Configur.html
                                                                                

Also, documentation is surely wrong on another points, as it for example gives:

    ipv6 = {
        addr = 1.2.3.4;
        port = 1205;
    }

and 1.2.3.4 is not a valid IPv6 address (it is an IPv4 address)

Also of note for documentation (if it is going to be fixed), one should use
for example 192.0.2.0/24 for documentation IP addresses (and not 1.2.3.4 -
see RFC 5737), and for IPv6 documentation prefix is 2001:db8::/32 (see RFC 3849)

(I would glady provide a patch for documentation if I knew if above specified
HTML file is the source against which the patch should be provided, or is
it automatically generated from something else.)


>> I'd been using FDAddresses alright, but would prefer to just have bacula-fd
>> bind to the available addresses.  Is that not a good idea?  I guess the
>> above hostname-based directive isn't too bad.
>
> Indeed, not specifying either FDAddress or FDAddresses should listen on 
> all available addresses. In the Linux client, it does. For the 3.x 

Well, on my Debianu GNU/Linux, bacula-fd 5.0.2, it does not.

In absence of specified ipv6 addr in FDAddresses, it will listen only on
0.0.0.0 (all IPv4 addresses).

I must use:

  FDAddresses  = {
     ipv6 = { addr = :: }
  }

in order to make it listen to all IPv4 and IPv6 addresses (which is also
probably what OP wanted to do, and what probably should be bacula default
(which it currently isn't) if no FDAddress/FDAddresses are specified.

This should probably be explicitely documented (if it is intended and not a
deficiency of the code, of course)


-- 
Opinions above are GNU-copylefted.


------------------------------------------------------------------------------
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users