Hi,

On Sat, 11 Jun 2011, Kevin Keane wrote:
 
> The two problems I had:
> 
> - The default setting for bacula was wrong. It would only listen on IPv4
>   but not IPv6 unless you explicitly added a
>   DIRAddresses/FDAddresses/SDAddresses section to the respective config
>   files.

This is still true, so we put in explicit IPv6 = <hostname> entries.

> - The Windows FD could not be configured to listen on IPv6 at all.

I hadn't got to the point of a test on Windows yet, but this does seem to
still be a problem alright.  If you put in an ipv6 fdaddress entry, the
bacula-fd fails to start, complaining about that line.  So I guess
bacula-fd for Windows doesn't support IPv6 yet.

> Both issues caused problems if you specified clients or SDs by DNS name
> rather than IP, and there was an AAAA record in DNS. Bacula would use the
> AAAA record and try to connect over IPv6, but that connection timed out
> and the backup failed. For Linux boxes, the workaround was to explicitly
> add the IPv6 addresses to the configuration files. For the Windows
> machines, I had to create a second DNS name for the same machine that
> only had an A record but not an AAAA record.

On linux, you need to explicitly put in an ipv6 address before each daemon
will listen on IPv6.  On Windows, my experience is that the backup doesn't
fail if a AAAA record exists for the client, there's just a bit of a delay
before things get up and running as the initial IPv6 connection times out.

Gavin


------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users