Just can not get IP to work

[CountryEd]

Folks,
Boy oh boy I love ProxMox. I was using version 6 years ago and now installed v9 on a new server.
I just can not understand how to assign a static IP from the IPs I have.
Main is x.x.x.1
Assigned is x.x.x.2 which I want to use for a new Deb13 VM.
I install using ISO and set IP as x.x.x.2 and set gateway.
But the IP just not get out of the VM, so I can not ping nor use repos and such for updates.
What am I missing?
Frustrated to say the least... It is my hobby site for amateur radio
May even have to come up with a few bucks for some one to log in and take a look.
Thank you all.
Ed

 

[longer]

Could you provide:
- network config from pve host:
cat /etc/network/interfaces

- Share vm config:
qm config [VMID]

- Share network config from the vm.

 

[UdoB]

I just can not understand how to assign a static IP from the IPs I have.
Main is x.x.x.1
Assigned is x.x.x.2 which I want to use for a new Deb13 VM.
I install using ISO and set IP as x.x.x.2 and set gateway.
But the IP just not get out of the VM, so I can not ping nor use repos and such for updates.

The usual approach for a small box with a single NIC is this: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_default_configuration_using_a_bridge

If your setup differs then you need to describe the differences in detail - to allow anyone to give a helpful reply.

If your system is physically in a datacenter then they should offer documentation, right?

 

[steve999]

VM can't reach the outside world with a static IP usually comes down to one of a few things, and you can narrow it down fast from inside the guest.

First run the basics inside the VM:

ip a
ip r
ping x.x.x.1

If the gateway ping already fails, it is almost always a layer 2 problem, not the IP config itself. A few things I have hit on my own boxes:

Bridge mismatch. In the VM's Hardware > Network Device, confirm the bridge is actually vmbr0, the one that has your physical NIC as a port. On the host, cat /etc/network/interfaces should show vmbr0 with bridge-ports pointing at your real NIC. If the installer picked a different interface, the VM ends up on an island.

IP already used by the host. If x.x.x.2 is also configured on the PVE host itself (easy to do accidentally when setting a static IP during install), you get an ARP conflict and packets disappear. ip a on the host should not show x.x.x.2 anywhere.

MAC binding upstream. Some routers only route the assigned IP to the MAC they learned first. If your router does static ARP entries or the ISP binds the IP to a MAC, the fresh VM MAC gets dropped. Checking the router's ARP/DHCP table, or temporarily cloning a known-working MAC, settles that question in a minute.

NIC firewall flag. On the VM network device the Firewall checkbox is on by default in PVE 9. If you have touched the firewall at datacenter, node or VM level, switch it off for a test.

Also check the netmask. x.x.x.2 with a wrong prefix will ping nothing. For a typical home LAN it should be /24.

Post the output of those three commands plus qm config <vmid> and the exact cause will be easy to spot.