No networking in VM or LXC

O

osteth

New Member
May 6, 2025
4
0
1
I am am a proxmox noob (setting up for the very first time) and apologize if I am just missing something absolutely basic.

I installed the latest version of proxmox and used other CIDR range instead of my actual IP address upon installation but swapped the IP in /etc/network/interfaces and got it up and running. I note this because I am not certain if this is the cause of my issue or not. The Issue I am facing is that when I spin up a new VM or LXC they are not getting any networking at all. I tried using the helper scripts to install guacamole and it failed due to no networking and then tried an ubuntu container and it had no networking then tried an ubuntu VM and it failed to boot because it permanently stalled waiting for networking .
does anyone know what I am doing wrong?
 
Welcome to the Proxmox forum, osteth!

Have you reloaded your network after the change (e.g. systemctl restart networking)? Could you share your network configuration in /etc/network/interfaces? How is the networking setup for one of your VMs/containers?
 
This is my proxmox host interfaces:
1746628036875.png
Networking tab:
1746628296026.png

I have restarted networking and the entire machine with no change.

Here is a test containers network config.
1746629259359.png
 
Last edited:
news said:
192.111.148.18/30 did you know, what this mean?

https://www.calculator.net/ip-subne...=30&cip=192.111.148.18&ctype=ipv4&x=Calculate

You have only 2 IPv4 Address.

Code: 
Network Address:    192.111.148.16
Usable Host IP Range:    192.111.148.17 - 192.111.148.18
Broadcast Address:    192.111.148.19

So you can't have a dhcpd in this network, nor get a other IPv4 Address from your Network 192.111.148.16/30.
Click to expand...
Yes, understood. That was a primary reason for deciding to use Proxmox. I was under the assumption that the Proxmox server was hosting an internal DHCP server and internal network, so all of the resources within would be within that internal network. I thought the internal networking was bridging over to 192.111.148.18 and exiting to the internet there.

based on this response, I am guessing that is not the case?
 
osteth said:
used other CIDR range instead of my actual IP address upon installation but swapped the IP in /etc/network/interfaces and got it up and running. I note this because I am not certain if this is the cause of my issue or not.
Click to expand...
This is the issue, revert back the IP in interfaces, because at reboot you will loose remote access to PVE itself.
 
_gabriel said:
This is the issue, revert back the IP in interfaces, because at reboot you will loose remote access to PVE itself.
Click to expand...
my cidr range is 192.111.148.16/30, with 192.111.148.17 as my gateway and 192.111.142.18 as my IP address. I installed with the CIDR range of 192.111.148.16/30 because that seemed like the right way to do it. but could not access the PVE web console until I edited the IP in /etc/network/interfaces.
I don't understand how I can have functional networking and a working console.
 
You must log in or register to reply here.
Top Bottom