No Network Access After Fresh Install

[ghostntheshell]

Hello,

I've installed a fresh install of Proxmox 7.2 on a box that was previously running 7.1 in the past. The server shows the ethernet interface and bridge as up. However, I cannot access the GUI nor can I SSH into the server.

Attached are the photos of the ip a, network/interfaces, and resolv.conf files. I've done hours of research and multiple installs, always the same issue. The only variables changed since the last time this box ran proxmox are; new GPU 2GB 1030 and new switch.

Thank you!

 

[ghostntheshell]

Sorry for the sideways images. Also, the switch is showing a good link light and I've tested the cable.

 

[bobmc]

Is the new switch dumb or managed? If it's managed, does the switch register the mac-address of the proxmox host?

you probably have at least three devices on the network a) gateway b) proxmox c) your laptop/desktop
are they all connected to the same switch?
can c ping a and b?
can b ping c and a (that would be no - according to your picture)?

if you swap switch ports for b and c, does anything change?

 

[ghostntheshell]

Thank you for your help!

Switch is unmanaged.
Desktop and Proxmox are on the same switch.
Desktop can ping the gateway/router.
Proxmox box cannot ping anything including the gateway. "Destination Host Unreachable"
Swapping ports resulted in the same result.

I've also installed other distros on the box recently as a host OS, all of them work without networking issues.

 

[bobmc]

Desktop and Proxmox are on the same switch.

Is the gateway device (ISP modem?) not directly attached to the switch?

 

[ghostntheshell]

Router is attached to the switch. ISP Modem is attached to the router. Router is handling DHCP and acting as the gateway.

 

[leesteken]

What is the output of ip r? Your router's IP address is 192.168.50.1? Your desktop also has an IP address within 192.168.50.0/24? Does your router block, or only allow, some MAC addresses? Does your router only allow traffic from IP addresses from within the DHCP range? Can you change your desktop IP address to 192.168.50.5 and see if it still works (and make sure not to connect the Proxmox machine)?

 

[bbgeek17]

try a new cable
connect the cable directly between laptop and proxmox, assign IPs manually - does that work?

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[ghostntheshell]

What is the output of ip r? Your router's IP address is 192.168.50.1? Your desktop also has an IP address within 192.168.50.0/24? Does your router block, or only allow, some MAC addresses? Does your router only allow traffic from IP addresses from within the DHCP range? Can you change your desktop IP address to 192.168.50.5 and see if it still works (and make sure not to connect the Proxmox machine)?

ip r
default via 192.168.50.1 dev vmbr0 proto kernel onlink
192.168.50.0/24 dev vmbr0 proto kernel scope link src 192.168.50.5

Router is open for all internal traffic. No blocked addresses. Changed desktop to same IP and confirmed it has net access and can ping the gateway/outside world.

Thanks for helping!

 

[ghostntheshell]

try a new cable
connect the cable directly between laptop and proxmox, assign IPs manually - does that work?

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

It doesn't. Also tried different cable. The NIC definitely works, have verified this today with another linux install.

 

[leesteken]

Since other Linuxes worked and it worked with PVE 7.1, maybe try installing and booting pve-kernel-5.13? Maybe its a driver thing and it works with 5.13 but not with 5,15. Maybe you need to run apt-get update and apt-get dist-upgrade, which you can't at the moment. The 5.15 kernel from the installer enables intel_iommu and later version disable it again (because there are too many issues on older hardware). You could try intel_iommu=off or iommu=pt with kernel 5.15, or try 5.13 and dist-upgrade if that gives you a working network connection.

EDIT: I just realized you can't try kernel 5.13 because you can't install it, because you have no network. Try the intel_iommu=off by pressing e in the boot menu and adding it to the kernel parameters.

 

[ghostntheshell]

Thanks everyone for the help. I connected the eth cable directly to one of the free ports on the router and now it works perfectly. It doesn't like the switch. It's unmanaged with no rules so not sure why it's not connecting. Would love to figure that out to take advantage of the higher throughput (2.5 vs 1).