Network interface always down after reboot..

  • Recent issue that popped up after making some changes... When pc starts (or reboots) network adapter is instantly working from bios (lights flashing). As soon as Debian starts, light go out, no network at all. After googling and poking around a bit, I realized the only way to get the network working is to manually enable it from the command line at the pc using these commands:

    Code
    sudo ip address add 192.168.1.4/24 dev enp3s0
    sudo ip link set enp6s0 up
    sudo ip route add default via 192.168.1.254

    After these commands, the network is working normally until the machine reboots. It then starts all over again..


    My system has been working fine for a couple of weeks now. This started recently after I tried installing the plugin called "openmediavault-wol 7.0.2" . I was trying to enable WOL but when I installed this plugin I was getting an error every time I tried to run it (sorry, I don't remember the error. It was a "software error" that popped up in a red banner on the screen in OMV). SO, I uninstalled the plugin and now it is gone. But it must have broken something because I am left with this problem.


    Does anyone have any ideas how to revert back to the working state I had before or what may have gotten scrambled here?


    Thanks!

  • After posting this question I managed to figure out how to fix it but I'm still al little confused. My Netplan.yaml file was showing my network adapter as enp5s0. When it should have been enp6s0. Once I edited that file the network worked fine even after a reboot.


    Now what I don't understand is, when using the command line interface, my network adapter is labeled as enp6s0. When I view the network interface from within the OMV GUI (on another pc) it is showing it as enp5so.. I'm not sure why this is or if it matters but it seems odd seeing how changing that from "5" to "6" in the command line interface fixed my issue. OMV GUI is still showing it as "5".

    • Official Post

    My Netplan.yaml file was showing my network adapter as enp5s0. When it should have been enp6s0

    That is systemd predictable naming causing that. I am guessing you added or removed a pci card? Unfortunately when you do that, OMV doesn't know and you will have to manually fix the networking.

    omv 8.0-10 synchrony | 64 bit | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0 | compose 8.0.1 | cterm 8.0 | borgbackup 8.0.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0 | writecache 8.0.0-13


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • That is systemd predictable naming causing that. I am guessing you added or removed a pci card? Unfortunately when you do that, OMV doesn't know and you will have to manually fix the networking.

    No, ther were no hardware changes at all. The only changes made were me trying to install the WOL plugin and then deleting it.

    • Official Post

    No, ther were no hardware changes at all. The only changes made were me trying to install the WOL plugin and then deleting it.

    Maybe a systemd update then. Hard to say but it was still systemd that changed the name. The WOL plugin installation and deletion could not have affected this in any way.

    omv 8.0-10 synchrony | 64 bit | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0 | compose 8.0.1 | cterm 8.0 | borgbackup 8.0.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0 | writecache 8.0.0-13


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!