On Saturday 30 October 2010 07:03:38 Blake Dunlap wrote: > On Fri, Oct 29, 2010 at 20:47, Dan Langille <d...@langille.org> wrote: > > On 10/29/2010 4:19 PM, Dylan Vanderhoof wrote: > > > On 10/23/10 11:30 AM, "Dan Langille"<d...@langille.org> wrote: > > > > > > On 10/22/2010 11:13 PM, Dylan Vanderhoof wrote: > > >> 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) > > > > > Have you asked this question on the users mailing list? > > > > > > What version of Bacula are you using? > > > > > >> Sorry it took so long for me to get back on this. > > >> > > >> I'm on 5.0.3, ipv6 support is compiled in, and the client is correctly > > > > resolving (on an OS level) the AAAA and A record for the SD. > > > > If your host has both A and AAAA records, then it's expected to be > > providing services on both addresses. Actually, Bacula takes IPv6 in > > preference. > > > > Solution: if you are providing IPv6 only services, create a new hostname > > with only an AAAA record. Simple. Easy. No code required. > > > > -- > > Dan Langille - http://langille.org/ > > Would it be possible to have Bacula, and try the other stack after a > failure if there are both types of records present? It seems to be emerging > as the standard practice among most client programs I've seen
Yes, someone must just submit a patch, then test it after we have integrated it. > > I think this would be a far better solution than trying to restrict > connectivity via config when you have corner cases due to the nature of the > dual stack transition, when split horizon DNS has not been employed. > > -Blake ------------------------------------------------------------------------------ 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
