[SOLVED] No internet connection/ wrong Interfaces

[Zatterli]

Hi there

So i just upgraded my proxmox from version 7 to 8. After the update my Proxmox didnt come online again. After reading some Threads i saw that qith the kernel update the Interfaces change nam. I tried to rename them in /etc/network/interfaces and then restart the aervice. No luck.
After that i also saw that my interfaces are down. I also tried to bring them back up.

Here are the Photos for some information:


Thanks in advance

 

[sw-omit]

You'll have to use the main name instead of the altname, so replace all the "enp0s31f6" with eno1 ( 4 places) as well as fix the typo you made in the gateway (192 instead of 1925)
Then be sure to apply the new settings with ifreload -a
Also, if you're worries about the interface starting with W, ignore that for now, that's the wireless interface (unless you set that one up as your primairy source, then do worry / check your wireless settings)

 

[Zatterli]

So i did what you recommended but still the Interface doesnt get any ip Adress. I also couldnt do ifreload - a so i just rebooted the system.

 

[sw-omit]

That you're getting an access-denied as root is a big red flag that something might be wrong on the system.

Did you follow these instructions for the upgrade?
https://pve.proxmox.com/wiki/Upgrade_from_7_to_8

Also, a quick google also gave me this thread:
https://forum.proxmox.com/threads/updated-packages-restarted-no-internet.136230/

 

[Zatterli]

Hi there

Sorry i response only now. So i looked into the other forum and did the dkpg and that worked. Now i also can do the ifreload - a. But im still not getting any ipadress.

 

[sw-omit]

Not sure how I missed this before, but you're missing a Linux Bridge (and using the linux-bridge values for the device, which is what some of the errors are about).
Try replacing your ENTIRE /etc/network/interfaces with the below (including the source-line at the bottom) and then running the ifreload -a again:

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual

iface wlp3s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.249/24
        gateway 192.168.1.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

source /etc/network/interfaces.d/*

 

[Zatterli]

but do i need the wlp3s0?
i dont have them anymore, as seen in th latest pic

 

[sw-omit]

Ah, yeah, the wlp3s0 line you can drop (this is for your / a wireless card), but yes on the vmbr0

vmbr0 is a Virtual BRidge device, so it gets created through software, so it's not there because you don't have it in your config.
You need such a bridge device to, in turn, connect your VM's to, so yes you need it (and it's common practise to set the network-settings that you use to connect to your Proxmox on that bridge too, that's what the installer does as well)

 

[Zatterli]

So that worked my VM's are back but i cant login to my (no Webinterface). But the ones from the VM's are there. And if i do a ip addr there are many things (dont know what they are).

 

[Zatterli]

I tried it with this thread didnt help.
Thread

And server is not Pingable.

 

[sw-omit]

Tried a full server restart already?
And are you able to ping from your proxmox-server itself to either your router or 8.8.8.8? (pinging to proxmox might be firewall-blocked or something like that)

 

[Zatterli]

i did a reboot and a ping to my rooter aswell to 8.8.8.8 and had a 100% loss

 

[sw-omit]

Can you, from within the host, ping 192.168.1.249 at least (to verify that config is set correctly)?
And what are the results of the commands:

ip r
systemctl status pveproxy

 

[Zatterli]

I couldnt ping from the the host

 

[Markku]

Note the typo in the interfaces configuration: it should be "address", not "adress"

 

[Zatterli]

worked after that. Thanks to all that helped, ur the best

 

[sw-omit]

Note the typo in the interfaces configuration: it should be "address", not "adress"

Good catch there Markku!

And nice that it now works, maybe mark the topic as solved by editing your first post.

That aside, it is still strange that it broke so much, so you might want to think about doing a system re-install sometime in the future to remove any hidden issues (and/or keep an eye on the logs, see if something strange pops up in there).