This appears to be a bacula-fd bug, as best I can tell. Perhaps somebody can shed some enlightenment as to how I might get around it?
We have a bacula server running v4 and v6, with an A and AAAA record. All functional clients are IPv4 and are working great. I'm trying to add a hosts that backs up via IPv6. (It doesn't have IPv4 reachability to the server) The client still dual-stack however. I can use FDAddresses in the bacula-fd.conf on the client to prevent the client from listening on its IPv4 address. However, when I actually try to run a backup, the client contacts the SD by name and ignores the AAAA record for the SD. Even though the FD is not bound to an IPv4 address, it still attempts to use IPv4 to connect to the SD, since there is an A record present. Since there's no IPv4 reachability, the operation times out and the backup hangs. Suggestions? Ideally, it seems is an FD is configured to only listen on an ipv6 address, it shouldn't attempt to connect to the SD on IPv4. (More to the point, I'd think it would try to connect via whichever address family the server contacted it on to kick off the backup) Thanks, Dylan ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
