Kevin Keane wrote: > Oh yes, that was me. Ultimately, it's a bug in bacula; it has some > inconsistent default values: by default, the director tries to connect on > IPv6 when the machine has an AAAA record listed. But the FD does not listen > on IPv6 (in Linux, you can turn it on to make it work, in Windows, IPv6 is > not yet implemented in the FD). With the Windows firewall turned on, this > leads to a timeout. With the Windows firewall turned off, bacula finds out > about the failure of the IPv6 connection quickly, and switches to IPv4.
Well, in this case, bug is a subjective term. Everything is working as designed. It may be called stupid or dumb, but everything is working according to spec. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
