Re: [Bacula-users] bacula IPv6 status (unofficially)
Hi James, On Sat, 11 Jun 2011, James Harper wrote: Not really directly bacula related, but one of the concerns I have with switching to IPv6 for LAN scale traffic is the performance of the various offload features in the network adapters. Did you do any throughput testing? I haven't yet had time to look at performance in detail -- except to say that none of the backups that have run since seem noticeably slower. That being said, it's hard to tell with incremental backups and some of our full backups have other bottlenecks. I'm guessing support for IP Checksum Offload, TSO et al will be driver dependant so it may be quite messy to work out which the details of what cards/kernels/OSes do and don't make full use of these in IPv6. The tool to use for testing this is probably iPerf. I must do some investigation myself. Gavin -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula IPv6 status (unofficially)
Thanks for that information, that's excellent news! Back in the 3.x days, I had tried bacula with IPv6 and had two problems. Do you by any chance know if these two things have been resolved? I can't test it again because I had to remove IPv6 from my test network. The two problems I had: - The default setting for bacula was wrong. It would only listen on IPv4 but not IPv6 unless you explicitly added a DIRAddresses/FDAddresses/SDAddresses section to the respective config files. - The Windows FD could not be configured to listen on IPv6 at all. Both issues caused problems if you specified clients or SDs by DNS name rather than IP, and there was an record in DNS. Bacula would use the record and try to connect over IPv6, but that connection timed out and the backup failed. For Linux boxes, the workaround was to explicitly add the IPv6 addresses to the configuration files. For the Windows machines, I had to create a second DNS name for the same machine that only had an A record but not an record. Kevin Keane -Original Message- From: Craig Van Tassle [mailto:cvantas...@purdue.edu] Sent: Friday, June 10, 2011 8:07 AM To: bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] bacula IPv6 status (unofficially) On Fri, 10 Jun 2011 15:57:38 +0100 Gavin McCullagh gavin.mccull...@gcd.ie wrote: On Fri, 10 Jun 2011, Gavin McCullagh wrote: just a short note to say that I've been testing Bacula's IPv6 support of late and have generally found it to be good. PS: well done to all the developers involved :-) Gavin I have to agree there. I have been using IPv6 on my home systems (work does not have IPv6 yet) and it's actually been faster then IPv4 to the same systems. -- Craig Van Tassle HUBzero.org System Administrator YONG 1006 Desk Phone : (765)496-6413 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula IPv6 status (unofficially)
Hi, On Sat, 11 Jun 2011, Kevin Keane wrote: The two problems I had: - The default setting for bacula was wrong. It would only listen on IPv4 but not IPv6 unless you explicitly added a DIRAddresses/FDAddresses/SDAddresses section to the respective config files. This is still true, so we put in explicit IPv6 = hostname entries. - The Windows FD could not be configured to listen on IPv6 at all. I hadn't got to the point of a test on Windows yet, but this does seem to still be a problem alright. If you put in an ipv6 fdaddress entry, the bacula-fd fails to start, complaining about that line. So I guess bacula-fd for Windows doesn't support IPv6 yet. Both issues caused problems if you specified clients or SDs by DNS name rather than IP, and there was an record in DNS. Bacula would use the record and try to connect over IPv6, but that connection timed out and the backup failed. For Linux boxes, the workaround was to explicitly add the IPv6 addresses to the configuration files. For the Windows machines, I had to create a second DNS name for the same machine that only had an A record but not an record. On linux, you need to explicitly put in an ipv6 address before each daemon will listen on IPv6. On Windows, my experience is that the backup doesn't fail if a record exists for the client, there's just a bit of a delay before things get up and running as the initial IPv6 connection times out. Gavin -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula IPv6 status (unofficially)
Thank you very much! It does seem like a major improvement, then. It used to be that when the IPv6 connection failed, bacula would fail in a pretty bad way, and not fail over to IPv4. Great to hear that it now gracefully degrades! Kevin Keane The NetTech (North County Tech Center, LLC dba The NetTech) http://www.4nettech.com -Original Message- From: Gavin McCullagh [mailto:gavin.mccull...@gcd.ie] Sent: Sunday, June 12, 2011 10:19 AM To: bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] bacula IPv6 status (unofficially) Hi, On Sat, 11 Jun 2011, Kevin Keane wrote: The two problems I had: - The default setting for bacula was wrong. It would only listen on IPv4 but not IPv6 unless you explicitly added a DIRAddresses/FDAddresses/SDAddresses section to the respective config files. This is still true, so we put in explicit IPv6 = hostname entries. - The Windows FD could not be configured to listen on IPv6 at all. I hadn't got to the point of a test on Windows yet, but this does seem to still be a problem alright. If you put in an ipv6 fdaddress entry, the bacula-fd fails to start, complaining about that line. So I guess bacula-fd for Windows doesn't support IPv6 yet. Both issues caused problems if you specified clients or SDs by DNS name rather than IP, and there was an record in DNS. Bacula would use the record and try to connect over IPv6, but that connection timed out and the backup failed. For Linux boxes, the workaround was to explicitly add the IPv6 addresses to the configuration files. For the Windows machines, I had to create a second DNS name for the same machine that only had an A record but not an record. On linux, you need to explicitly put in an ipv6 address before each daemon will listen on IPv6. On Windows, my experience is that the backup doesn't fail if a record exists for the client, there's just a bit of a delay before things get up and running as the initial IPv6 connection times out. Gavin -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] bacula IPv6 status (unofficially)
Hi,
just a short note to say that I've been testing Bacula's IPv6 support of
late and have generally found it to be good.
We have:
- consoles connecting to the director over IPv6
- director talking to SD and FD over IPv6
- FD talking to SD over IPv6
As you might expect, if you configure Bacula to connect to a FQDN and
there's no record, you just get an IPv4 connection. If there is a
record available, and a suitable IPv6 route, Bacula will generally try
to connect over IPv6 first and then if it gets a TCP reset (the far end
isn't listening on IPv6) or a timeout (maybe a firewall blocking the
connection), Bacula retries using IPv4 and life proceeds as normal.
A couple of things worth noting:
== Daemon Address Config ==
Thus far, we've found the best thing to do is to use the multiple address
configs with an explicit IPv4 and IPv6 record, eg (for the FD):
FDAddresses = {
ipv4 = { addr = my.fq.dn; }
ipv6 = { addr = my.fq.dn; }
}
If you just use ip = {}, I've found that it only binds to the IPv4 address,
you need to explicitly have an ipv6 entry. The same applies to the
director and storage daemon. I'm open to better suggestions.
I think Bacula usually listens on 0.0.0.0 (all IPv4 addresses) by default,
but doesn't listen on :: (all IPv6 addresses). I'm not sure if this is by
design, but I guess perhaps it's arguably sensible to only listen on IPv6
where it's explicitly enabled for now. The main point is that it can be
enabled.
With IPv6 addresses, if you use SLAAC (stateless address auto-config), the
host's IP address is based on its MAC address, so it doesn't change. If
the host uses privacy addresses the address may change. On Windows 7, as I
understand it there are two addresses, one is initially created randomly
when you plug into that network but it stays constant on that network (this
is the one you expect to receive connections on and which usually goes in
the DNS). A second address is for outgoing connections and changes at each
reboot (or every 24 hours on Windows Vista apparently).
== TCP wrappers ==
In my experience at least, if you use TCP Wrappers on Linux, you need to
enter the IPv6 address of the Bacula daemons which will be connecting.
Although a FQDN will allow an IPv4 host in, you seem to need the IPv6
address. At a guess, this probably has more to do with tcp wrappers than
Bacula though.
This is one situation where Bacula will fail over IPv6 and not revert to
IPv4 which might still work. This is because it's not a connection
failure, it's an authentication failure, so that makes some sense.
Gavin
--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula IPv6 status (unofficially)
On Fri, 10 Jun 2011, Gavin McCullagh wrote: just a short note to say that I've been testing Bacula's IPv6 support of late and have generally found it to be good. PS: well done to all the developers involved :-) Gavin -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula IPv6 status (unofficially)
On Fri, 10 Jun 2011 15:57:38 +0100 Gavin McCullagh gavin.mccull...@gcd.ie wrote: On Fri, 10 Jun 2011, Gavin McCullagh wrote: just a short note to say that I've been testing Bacula's IPv6 support of late and have generally found it to be good. PS: well done to all the developers involved :-) Gavin I have to agree there. I have been using IPv6 on my home systems (work does not have IPv6 yet) and it's actually been faster then IPv4 to the same systems. -- Craig Van Tassle HUBzero.org System Administrator YONG 1006 Desk Phone : (765)496-6413 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula IPv6 status (unofficially)
Hi, just a short note to say that I've been testing Bacula's IPv6 support of late and have generally found it to be good. Not really directly bacula related, but one of the concerns I have with switching to IPv6 for LAN scale traffic is the performance of the various offload features in the network adapters. Did you do any throughput testing? James -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
