I am having a lot of networking issues with starting to use Proxmox. I think it may be a router issue (which I cannot access because the router is controlled by the housing agency) but want to check and see if what I've found makes sense or if I've missed something. All the following is from a fresh installation of Proxmox.
Issue 1: My router is assigning two different sets of IPs. On my windows desktop when I run ipconfig I am seeing a different IP than all of the IPs in the rest of the post. If I use the Windows IP/Gateway as a template for my Proxmox host it will fail to ping until I change it to the IP address Proxmox recommends in the 10.10.10... series. The below image from my VM is why I think there is a DHCP issue. The rest is my troubleshooting.
I have no issues creating my host as long as use the 10.10.10 series IPs using 2. enx00e4... as my connection via ethernet.
Issue 2: The network fails as soon as I start a VM. The VM will fail to initialize cloud-int and will not be assigned an IP. I've used Gemini to run through many different attempts at adjusting the network yaml to overcome the lack of IP address issue.
When I boot the VM after installation the issue persists with systemd failing to start because it is checking the Ethernet in the yaml files, I disable this by adding 'options'
The VM will state the network is unreachable on ping and have NO yaml under /etc/netplan/
I build a yaml for the netplan and set the ens18 to up via ip link set ens18 up. Then I generate/apply netplan and see no changes. I have not been able to get it work trying static IP either.
And then using journalctl we come to the original image of why I think there is a DHCP issue.
Help
Issue 1: My router is assigning two different sets of IPs. On my windows desktop when I run ipconfig I am seeing a different IP than all of the IPs in the rest of the post. If I use the Windows IP/Gateway as a template for my Proxmox host it will fail to ping until I change it to the IP address Proxmox recommends in the 10.10.10... series. The below image from my VM is why I think there is a DHCP issue. The rest is my troubleshooting.
I have no issues creating my host as long as use the 10.10.10 series IPs using 2. enx00e4... as my connection via ethernet.
Issue 2: The network fails as soon as I start a VM. The VM will fail to initialize cloud-int and will not be assigned an IP. I've used Gemini to run through many different attempts at adjusting the network yaml to overcome the lack of IP address issue.
When I boot the VM after installation the issue persists with systemd failing to start because it is checking the Ethernet in the yaml files, I disable this by adding 'options'
The VM will state the network is unreachable on ping and have NO yaml under /etc/netplan/
I build a yaml for the netplan and set the ens18 to up via ip link set ens18 up. Then I generate/apply netplan and see no changes. I have not been able to get it work trying static IP either.
And then using journalctl we come to the original image of why I think there is a DHCP issue.
Help