Proxmox setup

[Jimmy Brown]

Hello everyone,

I'm currently facing some technical issues while trying to install Proxmox on my second machine. Specifically, the IP address isn't being detected when I reserve the IP/MAC address via my Eero Pro 6 router. I am no expert in networking so please be patient, haha.

This second machine will be used for virtualizing TrueNAS, backup, secondary DNS (Pi-Hole) incase my 1st Pi-hole cuts out and other services. Below is the hardware setup:

1. Router: Eero Pro 6
2. CPU: AMD Ryzen 9 5950X
3. Motherboard: MSI B550 Tomahawk (supports 2 Ethernet ports: 1GB and 2.5GB; currently plugged into the 1GB port, with both ports tested)
4. Storage: 256GB M.2 SSD, 3 x 10TB Seagate IronWolf Pro NAS SATA drives

Network Setup:

I live in the UK. My internet setup uses fibre from the exchange, connected via an Optical Network Terminal (ONT) downstairs.

The ONT is connected to an unmanaged switch, and an RJ45 cable runs upstairs (to the attic) where it's plugged into a managed switch.

From the managed switch, the Ethernet cable leads to a spare room. I've tested the network cable and confirmed that there’s internet connectivity.

Proxmox Network Configuration:

1. Static IP: 192.168.5.232(this IP appears to be unused within my network)
2. Gateway: Copied from the Eero App under Settings > Network > Gateway (Eero IP Address)
3. DNS: Set to the gateway IP address

IP/MAC Reservation: Added the MAC address and IP to the reservation list in the Eero app

The Eero network uses subnets 192.168.4, 192.168.5, and 192.168.6 based on the devices connected. I've confirmed that the MAC address from the NIC setup page matches the one on the managed switch, and everything appears correctly configured.

I entered the command ip link and confirmed the enp4s0 is up. When I unplug the ethernet, the status will show DOWN State and when I plug it back in, it shows UP.

The vmbr0 is showing the correct MAC address / NIC it is connected to.

When I enter https://192.168.5.232: 8006 on any browser, I get no response.

Any feedback on what went wrong?

Thanks!

 

[LnxBil]

Can you ping the ip? Can you login on the PVE host from the display+keyboard, if so, check with ip a if the IP is still the same.

 

[Jimmy Brown]

Yes, I can ping the PVE.

 

[Impact]

Can you try what ip you get via this?

ifdown vmbr0
dhclient -v

What ip does the device you use to access it have? With your specific router you might have to alter the mask too.
Pinging the node from itself isn't terribly useful. @LnxBil probably meant if you can ping the node's ip from another device.

 

[Jimmy Brown]

Can you try what ip you get via this?

ifdown vmbr0
dhclient -v

What ip does the device you use to access it have? With your specific router you might have to alter the mask too.
Pinging the node from itself isn't terribly useful. @LnxBil probably meant if you can ping the node's ip from another device.

My bad, misundersood what he meant.

Yea, I tried to ping from 2 machine (windows / MAC) and they can not reach the host of 192.168.5.232.

Looks like the vmbr0 is down?

 

[Impact]

Please don't quote whole messages, especially if it is the newest one.
These are two separate commands. Please run them as such. Just dhclient -v without any other arguments. vmbr0 is supposed to be down for this test, hence the ifdown vmbr0 before. I still don't know the ip of these devices.

 

[Jimmy Brown]

Please don't quote whole messages, especially if it is the newest one.
These are two separate commands. Please run them as such. Just dhclient -v without any other arguments. vmbr0 is supposed to be down for this test, hence the ifdown vmbr0 before. I still don't know the ip of these devices.

My apologies, I thought it was one command.

I have ran the command dhclient -v
I've attached the output.

 

[Impact]

You just did it again
I can't tell if you ran ifdown vmbr0 first. It will likely not work without it. Nothing gave out a DHCP lease which is bad. Your router is supposed to give it one if connected properly. Maybe a problem in-between. Try to connect it directly.

I still don't know the ip of these devices.

 

[gfngfn256]

From your PVE node (physical display/monitor), show output for the following 4 commands:

ip a

cat /etc/network/interfaces

cat /etc/hosts

hostname

 

[alexskysilk]

whats the output of

systemctl status pveproxy

 

[Impact]

There is no point checking any of this if basic networking to the router doesn't work.

 

[Jimmy Brown]

There is no point checking any of this if basic networking to the router doesn't work.

I attached the wrong screenshot.
I typed in if down vmbr0 entered. Followed by dhclient -v entered and was the same response as the screenshot, no DHCP lease / IP.

I am going to attempt to plug the pc directly into the Eero router and see if that helps.
Strange that my small Lenovo machine worked fine in the same scenario. This was connected to the same managed switch (attic) and into an unmanaged 8 port switch in my spare room.
I'll run some further test in the new few days. Thank you very much for your help so far.