Veeam WA & IPv6

[Fraeco]

Hi,

I'm trying to get an offsite through the Wan accelerator to work on IPv6
I've added the WA on the local server, this is no problem. When I try to add it on the remote server veeam can't seem to connect to the device.

I entered the DNS name of my V6 to-be WA Proxy (offsite.domain.com), entered credentials of the machine and when the wizard goes to check what needs to be installed I get the error "IP list empty".
I then tried entering the IP instead of the DNS, then I just get the default "The Network Name cannot be found" error.

When I ping offsite.domain.com I get reply from the target on v6 however. Also, when I open the UNC path \\offsite.domain.com\ADMIN$ it opens without any problem.

Am I doing something stupid here, or is Veeam not setup to work with IPv6 yet?

[Dima P.]

Hello Fraeco,
I am 99% sure that IPv6 is not supported.

[foggy]

+1%

[Fraeco]

Sorry for the slowpoke reply

Thanks for getting back to me on this.

Is IPv6 support on the roadmap?

[foggy]

Not in the short list, as far as I know.

[Zeon]

I know IPv6 isn't supported in v7 (which we use). In our area (APNIC area) there is virtually no further public IPv4 really available. We've switched our entire internal network to IPv6 with just our PBX and Veeam not using it currently...

[dellock6]

However the lack of "public" IPv4 is not completely related to switching an internal network to IPv6; it's fine from a consistency viewpoint and to remove any 6-to-4 routing system, but it's not mandatory