Upgrade PVE ip limitation problem.

[seeb]

Due to problems, I have to do an upgrade of the old PVE 3.x to the latest one. I didn't do it before because of problems with the number of IPs assigned to a CT. Currently I have 64 public IPV6 addresses and 8 public ipv4 IPs assigned to one CT. When upgrading to a newer version I get a message that I have too many ip addresses and the CT will not start. How to solve the problem with so many ip's that need to be assigned to one host in CT?

Does anyone have an idea how to solve this?

 

[Dunuin]

Proxmox VE 3.x
First Release: 2013-05, Debian Version 7 (Wheezy), Debian EOL: 2016-04, Proxmox VE EOL: 2017-02

So you are running a 10 year old PVE installation that isn't receiving any security patches for over 6 years but is hosting public services with a lot of public IPs? That really sounds bad....

With "upgrade of the old PVE 3.x to the latest one" you mean PVE 7.4 according to this?:
https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0
https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0
https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0

Or just to the lastest Version of the PVE 3.4?

 

[seeb]

The update itself is not the problem. The problem is a restriction that I can't get around. I upgraded to 7.4 and I can't use as many IP addresses as I need. I am encountering more and more problems maintaining this server. I compile newer and newer versions manually but some things require newer kernels and updating even manually is no longer possible. Of course the PVE itself stays in the old version .... In version 7.4 I encountered another problem. Only DNS had an open port, but this is probably the fault of some new version of the firewall and its default settings. Apparently, I already have to make a production update but without moving the IP to the host it will not be possible. CT has Debian 9 with manually compiled packages. Otherwise, it doesn't work. I am ready to move the entire host to a fresh installation 7.4 however this is prevented by the limit of IP addresses I can assign to one CT.

 

[seeb]

After the update, ~20 IPs remained from 65! Proxmox 7.4

 

[Neobin]

After the update, ~20 IPs remained from 65! Proxmox 7.4

I mean, that are after all 12 more than the documentation states :
https://pve.proxmox.com/pve-docs/chapter-pct.html#pct_container_network

I have no clue, but I am wondering, if there is no other/better approach to handle that amount of IPs?

 

[seeb]

I would very much like, for example, a range of 2000:4444:xxx::2-2000:4444:xxx::FA