Sorry!
It was right there in my face! Shame on me...
This will generate name pinning configuration for the interface 'enp1s0' - continue (y/N)?
y
Name for link 'enp1s0' (enx525400d99ca2) will change to 'eth0'
Generating link files
Successfully...
Hi...
I am using pve-network-interface-pinning to pin enp1s0, for instance, to eth0, eth1... and so on.
I have 9 nic each server.
But I need to change the hardware and after that, all nic turns back to previously name, like enp1s0, when I use ip...
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
You do not have any new mail.
Last login: Thu May 28 07:40:18 2026 from 192.168.3.7
root@pbs:~# proxmox-backup-manager version --verbose
proxmox-backup...
e the developer documentation applies to all packages, as does the requirement for the devel repository. some packages might build fine without it by chance. it probably doesn't hurt to reference it in the kernel readme as well (since it is...
This would be 3x enterprise drives, in some sort of performance-oriented configuration, while the existing 3 are left for slow/bulk storage.
Yeah, it's not ideal, but we needed *some* sort of redundancy. Also, I didn't initially plan to use this...
Yes, MX500 is DRAM cached like the Samsung 870 EVO. But OP has BX500.
Compare: https://tweakers.net/pricewatch/compare/1645084;1893356;2078708;1745668/
the client is available as a static binary that should work on most x86_64 linux distros:
https://pbs.proxmox.com/docs/installation.html#install-statically-linked-proxmox-backup-client
Fast enterprise drives are obviously preferred and they usually also have a much higher TBW so they wear out much slower. But they come at a price.
It's a trade-off. Invest in enterprise grade hardware which is fast and lasts longer or spend less...
I'm on 9.2 and I cannot connect to VMs via SPICE when using the domain to connect to PVE. It only works if I get into PVE via IP. I think the issue has to be with NPM, but I haven't found reliable information on how to propery configure PVE 9...
But that’s still much better than simply forwarding traffic directly to the relevant apps on port 3000, etc., which suggests to me that many apps likely use plain HTTP or self-signed certificates. An absolute no-go in 2026, and never a good idea...
If there is no specific reason to keep the CT/LXC behind a Proxmox-internal NATed bridge, I would consider attaching the CT/LXC directly to vmbr0 and giving it an IP address on the same LAN as your Internet router.
Then the port forwarding can...