adding ipv6 causing client access to be unreliable?

[Brock Palen]

We were modernizing some and rolling out ipv6
The bareos server always had ipv6 but it was not part of DNS nor allowed through the firewall.

After adding it to DNS and opening up the firewall clients that connect directly over the wan (not over the VPN or local network) all use client initiated connections.

They should show up even trigger backups but if you do:

status client=<client>

A large fraction would fail and drop the connection and come back later.

Telling bareos director to only listen on ipv4 things started working again.

I’m guessing I have created some sort of resolution/routing loop, and were actaully ok with ipv4 just more curious as rolling out ipv6 for our mail and everything else has been a learning experience.


Brock Palen
bro...@mlds-networks.com
www.mlds-networks.com
Websites, Linux, Hosting, Joomla, Consulting

[Bruno Friedmann (bruno-at-bareos)]

Hi, Just for information, I'm  using ipv6 since years (>5) here on my network, and I've started 2 years ago to only use ipv6 for the backup, so bareos here is using 100% of the time ipv6.

So for most of the task it works well, but I don't use the client initiated feature.

I might give it a try next week-end ...