On Sunday 10 January 2010 04:57:31 Kevin Keane wrote: > > -----Original Message----- > > From: Kern Sibbald [mailto:[email protected]] > > Sent: Saturday, January 09, 2010 9:49 AM > > To: Kevin Keane > > Cc: bacula-devel > > Subject: Re: FW: [bacula 0001439]: IPv6 breaks WinBacula with Windows > > Advanced Firewall > > > > On Wednesday 06 January 2010 13:01:37 Kevin Keane wrote: > > > Hi Kern, > > > > > > Thanks for looking at that! I may actually end up volunteering to do > > > > the > > > > > Windows IPv6 myself if I find the time and can set up the development > > > environment. Not a promise, though; paid work has to come first, of > > > > course! > > > > > Given that Microsoft is pushing IPv6 very heavily, I can't imagine > > > > that the > > > > > structures aren't there - but it is quite likely that the IPv6 socket > > > > code > > > > > is very different from the Unix code. > > > > > > Meanwhile, Dan and I discussed this offline and came up with a short- > > > > term > > > > > suggestion: make bacula's IPv6 behavior configurable, instead of > > > > always > > > > > automatically using an AAAA record. That is probably a lot faster and > > > easier to implement than porting the Windows FD to IPv6. The impact > > > > is just > > > > > too dramatic to leave this issue completely unaddressed. > > > > I personally believe that the best way to proceed is for someone who is > > interested to either fund an IPv6 project for Windows or to submit the > > code. > > Agreed. I might actually do that myself. But that's a long-term fix; I was > hoping for a short-term solution. > > > I don't particularly like the idea of a configurable option because we > > already > > have too many, and unless I am missing something, this seems to me to > > be > > somewhat of a special case where there are probably other workarounds. > > Yeah, I see your point about too much configurable. A couple notes: > > - It's actually a very normal case. The only reason it hasn't hit big time > yet is that few people are using IPv6 extensively yet, and so far many > people are turning it off altogether. But that is about to change big time > very soon; I actually expect it to be as disruptive as Y2K was predicted to > be. I am trying to migrate my own network to IPv6 to be ahead of the curve > and be ready when the demand hits in 2011. > > - The workarounds have severe networkwide side effects. You have to either > turn off the Windows firewall or abandon your IPv6 migration or remove the > AAAA record from DNS. All of that affects the network as a whole. The least > intrusive workaround is to create a completely separate DNS name for the > client that has only an A record but no AAAA record. But that is pretty > severe, too. > > In any case, in the end you are the one who has to set the priorities, and > I agree 100% with your strategy for resolving this for good, just not in > the short term.
If all goes as currently planned, during 2010, we will be significantly improving our FD support for Windows. Who knows, maybe fixing the IPv6 problem will be one of the items. Best regards, Kern ------------------------------------------------------------------------------ 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-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
