UPDATE network interface name

    • OMV 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Wow, i thought this should never happen with predictable device names.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • It is on version 4 since installation. (not upgraded from 3 or anything).
      I didn't move the NIC, it's the onboard!

      In my opinion, it's OMV's drawback. It should assign your network settings to 'any' or 'the first' available interface..
      Even so, you could still get locked out if simply your onboard card dies. Then you add a pci, but OMV would probably see and configure the onboard first.

      It's mandatory, in my opinion, for a web interface environment, to allow you to pre-configure a non existing network interface.


      Anyway, the question remains, will I mess up OMV if I edit the file?
      enp2s0 is only mentioned twice. Once for the main network configuration and once for the vpn configuration.

      If yes, my only hope is to add a pci ethernet first, really HOPE that it will get named enp3s0 and select it from OMV web interface,
      then power-off, remove the nic, put the graphics card and boot..
    • MacAriOi wrote:

      I didn't move the NIC, it's the onboard!
      Would be interesting to compare lspci output with video card installed and without. It seems your mainboard enumerates PCIe 'slot's differently then and as such Debian 9 with its predictable device names gets confused. OMV relies on Debian's interface names and since they change with your configuration you're in trouble now.

      Can't help here since I didn't configure network on any of my OMV boxes (I rely on DHCP with dynamic DNS updates and honestly don't care about interface names and IP addresses in small networks).
    • MacAriOi wrote:

      In my opinion, it's OMV's drawback. It should assign your network settings to 'any' or 'the first' available interface..
      Even so, you could still get locked out if simply your onboard card dies. Then you add a pci, but OMV would probably see and configure the onboard first.

      It's mandatory, in my opinion, for a web interface environment, to allow you to pre-configure a non existing network interface.
      OMV behaves as every other Linux would in this case. The predictable network device naming is a standardized mechanism. OMV uses the Debian network interface framework/toolchain, so there is nothing that can be done.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • MacAriOi wrote:

      Anyway, the question remains, will I mess up OMV if I edit the file?
      What file? /etc/openmediavault/config.xml? No, that's not enough. You need to rebuild the affected configuration files. You can give it a try with

      # omv-mkconf networking

      But maybe that's not enough.

      BTW: In OMV5 it would be very easy to rebuild all affected configuration files: # omv-salt stage run all
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • Actually a lot of Mainboards do strange stuff with virtual pcie interfaces for onboard i/o. This is of course very unfortunate and at least only common with consumer hardware. Maybe you could fix it differently, others may correct me if I am wrong, as I am way more familiar with GNU/Linux in general as I am with OMV.
      Edit /etc/udev/rules.d/70-persistent-net.rules and add a symlink from enp2s0 to enp3s0. This way you can access the device using both names. Go to the GUI and change all network settings from enp2s0 to enp3s0, remove the symlink. The question remaining is, how the gui handles the symlink, but my guess is, that it will just recognize a new device.