>>>>> On Thu, 27 Dec 2007 22:54:35 -0500, Minkus said:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> Before I filed a bug report I wanted to ask this on the list to see
> if I am missing anything.
>
> When a host has both an A and an AAAA record it seems that Bacula
> prefers the A record. Since most people who run IPv6 are still
> running it in dual-stack environments most hosts will have both
> records. It is common practice for clients to favor AAAA records in
> order to facilitate the eventual switchover. I for one am trying to
> move and test each service one by one and my life becomes more
> difficult when I have to play games with records in order for Bacula
> to connect over IPv6.
>
> Second, when a host has both types of records and the Bacula daemons
> are only listening on IPv6, Bacula does not try to fail over to the
> other address. I tried to force Bacula to use IPv6 by forcing the
> FD to listen on IPv6 but the director will try to use the A record
> and never even attempt to contact the FD over IPv6. Most clients
> attempt the preferred record and then fall back to the non-preferred
> record in the event of error.
>
> Am I doing something wrong here or I am correct in thinking that the
> address resolution behavior should be modified?
It does prefer A. I think the code for this is in bnet_host2ipaddrs, so you
could try swapping the cases where that call resolv_host when family is 0.
> One last item ... Has anybody successfully gotten the Win32 FD to
> use IPv6? I used the precompiled version and it gave me an error
> similar to:
>
> got token 'ipv6' expecting [ip|ipv4]
>
> I received this error when I tried to force it to listen on IPv6 by
> putting the following in the FD config:
>
> FDAddresses {
> ipv6 = { addr = <ADDRESS6>; port=9102; }
> }
>
> I then though that maybe ipv6 was not built into the precompiled
> version, so I compiled it myself and I received the same error. I
> read in the archives a response from Kern stating that IPv6 should
> be supported in Win32 but according to the error that I am getting
> it doesn't even look like ipv6 is valid for win32.
The error means that IPV6 was not detected at compile-time. You'll need to
check the config.log to find out why.
__Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
