Hi Josh,
Thanks for your quick answer.
----- Mail original -----
>
> On 3/13/2012 11:07 AM, Luc Maisonobe wrote:
> > So before setting up internal names and internal DNS in addition to
> > the
> > external one, I considered using IPV6 only for my backups, since
> > IPV6
> > does run perfectly on my system. Each host can have its own address
> > (or
> > even several ones if I wanted to), firewalls can be tuned, there is
> > only
> > one address space to deal with, there are no translation tables.
> > Everything looked better than DNS and NAT tricks ...
>
> If there are no DNS records for the internal IPv4 addresses, then
> make
> up some names for the clients and add them to the bacula-dir server's
> /etc/hosts file. Then use {FD/SD/Dir}Addresses to have everything
> listen
> only on the internal IPv4 network.
>
> Because you currently have both A and AAAA records setup for the
> client
> hostnames, then when given an Address=hostname line in a Client
> resource
> in bacula-dir.conf, bacula-dir is likely defaulting to the A record.
> If
> you really want to use IPv6, then add an alternate hostname for each
> client to DNS that has ONLY an AAAA record and no A record. Then
> using
> Address=alt-hostname in the Client resource in bacula-dir.conf so
> that a
> DNS lookup sees only the IPv6 address.
So in both cases, IPV4 or IPV6, I should set dedicated names for bacula.
I'll try to do that in a few days when I am back.
I understand that when two addresses are available, a program has to guess
which one to use.
It would however be nice that in this case, a rejected connexion on the first
address tried would not interrupt everything but would simply mean to bacula
it needs to try the other addresses. Is there an issue tracker for bacula
where I could put this request for enhancement, so developers can look at it
and decide if it is worth implementing ?
>
> AFAIK, Bacula does not yet have the equivalent of FDAddresses = {}
> for
> the Client resource in bacula-dir.conf. I agree it is probably
> needed,
> because most people using IPv6 do so in a mixed IPv4/IPv6
> environment.
Yes, up to now, dual-stack environments are the rule.
Thank you very much
Luc
> Also, I don't believe FDSourceAddress is suitable for a mixed
> IPv4/IPv6
> environment, though it is rarely needed.
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft
> developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3,
> MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
