[PVE] Worker configuration does not prompt for static IPv6 address

[DrumSlayer]

Hello,

Following case #07672609, where I discussed some details about IPv6 issues with PVE and VBR, I'm here to submit something I think you forgot to implement in the rush :

When configuring Proxmox VE Worker, the Network section does only prompt for a v4, and there is no prompt for any v6 address, nor dual-stack setup.


This seems very unprofessional in 2025 to forget about IPv6, to be honest . We deprecated v4 in our infrastructure a few years ago, and run full v6 as of now.
We run VBR well on v6 networks with VMware using built-in v6 network settings and DNS resolution, and Worker are using linux, which support IPv6 for like more than two decades now

Is it planned ? Or will we have to totally abandon using Veeam in our infrastructure ? (Since we stopped using VMware in profit of PVE)

Thank you,

[PTide]

Hi,

We plan to do that later - there were other things with higher priorities than this one.

Btw, why bother with static IPv6 instead of a normal DHCP reservation?

Thanks!

[DrumSlayer]

Hello!

Nice to hear that.

We do use SLAAC on some cases, but definitely not DHCPv6.
It's weird to have the choice for v4 but nor for v6 to be honest

[rovshan.pashayev]

Hi Pierre,

Your request is noted.

[dcl-technique]

Hello,

We are currently testing VBR with our Proxmox infrastructure but we're running into several issues due to hardcoded 'legacy IPv4' limitations in the GUI as well as on the data plan.

Our insfrastructure is consists of a physical remote Veeam BR 12.3.2.4165 server, reachable over IPv6 (GUA) alongside an internal test Proxmox host, with a dual stack IPv4/IPv6 network setup, with an IPv6 GUA address. On the firewall side, the required ports are open to allow communication between each IPv6 address. However, we've run into several issues / limitations, notably :

1. Inability to add the Proxmox host using the IPv6 address
Veeam can reach the server, the SSH key is obtained

But it fails due to an 'invalid port specified' :

Assiging an DNS AAAA record to the Proxmox host and then adding it works

2. Veeam can deploy the agent but the latter cannot communicate because it's hardcoded to use legacy IPv4
DHCP is enabled on the Worker config on the Veeam GUI but the VM does not obtain a SLAAC address
Documented here but never resolved : post546848.html?hilit=ipv6#p546848

IPv6 on the worker's network config appears to have been intentionally disabled, proxmox reports no IPv6 address on the VM :


So in essence, the data plan communication between the agent and host over IPv6 does not work.
There is no article mentioning such limitations other than the generic advertised IPv6 support here : https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13
"Veeam Backup & Replication supports IPv6 communication for all backup infrastructure components" but this is clearly not the case

Is this fixed in VBR 13 or do you plan to implement it ?

Thanks

[Mildur]

Hello dcl-technique,

I’ve merged your post with the existing topic.
There was no change between v12 and v13 regarding your comment and the discussion in this topic.
We’ll discuss this request internally, and if there are indeed limitations with IPv6, we’ll update our Help Center accordingly.

Best,
Fabian