>Thanks for the reply.  Is this considered a bug?  Admittedly not so many
>networks use IPv6 yet so I can imagine it might not be very high priority.
>
>Hard coding the IP is not an ideal solution.  This is a laptop running DHCP
>without a reservation so while the IPv6 address probably won't change, the
>v4 address will.  I can give this laptop a reservation, but we're heading
>in the direction of setting up bacula backups for 20-30 laptops, so I'd
>prefer not to give them all reservations.

Well, I don't know about bug, but the manual suggests an algorithm based
on the routing table.

I don't have any v6 nets available (so I can't test), and the manual suggests
that "or as a symbolic name (only in the ip specification)" so it looks as if 
this
would not work (unless I am only being pedantic about "ip" versus "ipv#"):

FDAddresses  = { 
    ipv6 = {
        addr = host.domain.com;
        port = 9102;
    }

You can try it though as I took a look through the source in trunk and there
doesn't appear to be a distinction at least in the code between any of the
address parameters and the manual only notes the limitation in FDAddresses
not FDAddress. My guess is it that it will be fine.
jlc

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users