Search results

  1. S

    [SOLVED] No network after dist-upgrade

    Omg... You're absolutely right. :oops: I doubt the upgrade had anything to do with it then. More likely, I've not rebooted the server since I've recently installed it and so never had the chance to run into trouble. Thank you very much for spotting this @spirit!
  2. S

    [SOLVED] No network after dist-upgrade

    I've just tried your suggestion. There was no change. Not surprising, given the syslog reporting May 26 18:12:49 comet kernel: [ 7.332797] forcedeth 0000:00:08.0 enp0s8: renamed from eth0
  3. S

    [SOLVED] No network after dist-upgrade

    Thank you for your reply. The output of ip a would suggest the interface names are not being changed to their predictive names. Although I would presume this is a result of me being chrooted into the system. root@sysresccd:/# cat /etc/network/interfaces # network interface settings...
  4. S

    [SOLVED] No network after dist-upgrade

    I performed the following dist-upgrade which included a new kernel. After reboot, I was unable to ssh into or ping the server. My first instinct was that there was some sort of incompatibility with the new kernel. I chrooted into the system from systemrescuecd and tried booting the previous...


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!