Use bind0 as primary network adapter instead of eno1

    • OMV 4.x
    • Use bind0 as primary network adapter instead of eno1

      Hello,

      I have a box with a build-in and two PCIe network adapters. I used the build-in to install with DHCP, it appears as eno1.
      Also, I successfully configured the two others to be a trunked bind0 with DHCP, as I have a managed switch which supports
      trunking.

      Both interfaces work well and can be accessed by their different names. But eno1 is still used as default route, it appears
      before the bind in /etc/network/interfaces. I thought this file would be generated by mkconf, so I renamed the 30bind
      into 15bind in order to have it defined before eno1. omv-mkconf exchanges the entries, no change.

      Either, I did not understand the concept of primary interfaces correctly, or I have to do something with "ifup" in order to
      delete the default route and add a new one using dev bind0.

      Or do I overlook an easy way of doing so?

      BR,
      Carsten.

      The post was edited 1 time, last by Carsten12 ().