Interface eth0 error on raspberry pi 4

  • Hi

    I have done a clean install and Im triying to add eth0 method dhcp and dns 8.8.8.8 in Interfaces and i got this error.

    https://controlc.com/0a0d0d0f

    And when i click i show details.

    Im on raspberry pi 4. In a recent install i didn't get this error.

    Could I get some help?

    Thank you.

  • Try this:


    sudo rm /etc/systemd/network/99-default.link

    sudo netplan apply

    sudo omv-salt deploy run systemd-networkd

    omv 5.5.17-3 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • That did not work for me. In the end I just requested a new ip lease from the console (thank you https://www.computerhope.com/issues/ch001078.htm)


    Sudo dhclient -v


    Then I continued to my router and set that, as the static IP address (checked again, already did that earlier)


    Now I got access to my Pi once more... IP and local hostname.
    I can now successfully change settings in Network. Hostname and local domain... and just to be extra sure. I went to interfaces and added DNS and IPv4 and IPv6 settings as read in the console. Might be overkill, but it finally seems to work.

  • Try this:


    sudo rm /etc/systemd/network/99-default.link

    sudo netplan apply

    sudo omv-salt deploy run systemd-networkd

    Thank you very much ryecoaaron !

    I had the same issue while trying to add the ethernet (eth0) interface (as stated in official documentation https://github.com/OpenMediaVa…ing_OMV5_on_an%20R-PI.pdf) with OMV 5 on my RPi 4B.

    Trying these commands have fixed the issue.

    I guess it is not the "normal" behavior as I cannot see any warning on official documentation and it seems to be working like a charm in this video.

    Thank you anyway

  • I have the same problem on mi Pi 3B+, I've tried the three commands reported but after a system reboot I can't access anymore to OMV via SSH.


    From my router panel I see Pi 3B+, but it's setted as "non active". How can I resolve this issue?


    Thanks!!!

  • I have the same problem on mi Pi 3B+, I've tried the three commands reported but after a system reboot I can't access anymore to OMV via SSH.


    From my router panel I see Pi 3B+, but it's setted as "non active". How can I resolve this issue?


    Thanks!!!

    I can confirm this issue on Pi 3B running Raspbian.


    Following @lassewr's instructions fixed this for me:


  • I can confirm this issue on Pi 3B running Raspbian.


    Thanks for the reply! I tried but seems no work for me... The output from console is:


    It's everything ok? What I have to do after that?


    Thanks!

  • Try this:


    sudo rm /etc/systemd/network/99-default.link

    sudo netplan apply

    sudo omv-salt deploy run systemd-networkd

    Sorry, but that does not work for me.

    First line gives me

    Quote

    rm: das Entfernen von '/etc/systemd/network/99-default.link' ist nicht möglich: Datei oder Verzeichnis nicht gefunden

    Second outcome:

    Quote

    /etc/netplan/20-openmediavault-enp2s0.yaml:5:20: Error in network definition: Invalid MAC address '', must be XX:XX:XX:XX:XX:XX

    macaddress:

    ^

    Any ideas?

  • Did you reboot? Is the network adapter still named enp2s0 in the output of ip a? If it isn't, you need to update the omv network setup. omv-firstaid might help.

    omv 5.5.17-3 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    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!