NIC-Bond isn't shown anymore

  • Hi.

    I have a prblem with my nic's in my server.

    It has an onboard nic from realtec and a 4-port networkadapter from intel.

    onboard nic ist used as admin-port (enp8s0), 4-port adapter is bonded as 802.3ad for data-transfer (bond0).

    In Webgui Network / interfaces the bond0 isn't shown anymore, but it is active.

    bond0 has a static ip which is still reachable in the network, but the hostname (nas) ist now bound to the ip of admin port (was on bond0 before).

    When I try to recreate the bond via webgui (all 4 nics are available for this) it creates bond1 an gives an error on the console "inavlid link....on bond0"

    So I deleted bond1 again and restartet the the server.

    In webgui I can't see any bond, only the admin nic, but the server is still reachable on both IP's.

    "IP link show" shows the following:


    root@NAS:~# ip link show

    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    2: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000

    link/ether bc:5f:f4:97:01:fc brd ff:ff:ff:ff:ff:ff

    3: enp4s0f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000

    link/ether 0a:b5:ae:4c:49:1e brd ff:ff:ff:ff:ff:ff

    4: enp4s0f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000

    link/ether 0a:b5:ae:4c:49:1e brd ff:ff:ff:ff:ff:ff

    5: enp5s0f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000

    link/ether 0a:b5:ae:4c:49:1e brd ff:ff:ff:ff:ff:ff

    6: enp5s0f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000

    link/ether 0a:b5:ae:4c:49:1e brd ff:ff:ff:ff:ff:ff

    7: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000

    link/ether 0a:b5:ae:4c:49:1e brd ff:ff:ff:ff:ff:ff

    8: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default

    link/ether 02:42:72:7a:cb:e0 brd ff:ff:ff:ff:ff:ff

    10: veth91ec054@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP mode DEFAULT group default

    link/ether ae:f8:a7:68:54:25 brd ff:ff:ff:ff:ff:ff link-netnsid 0

    12: veth9769d6c@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP mode DEFAULT group default

    link/ether 0a:dc:a2:a4:8c:5d brd ff:ff:ff:ff:ff:ff link-netnsid 1

    14: veth47902f9@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP mode DEFAULT group default

    link/ether 52:60:f0:b4:c4:b5 brd ff:ff:ff:ff:ff:ff link-netnsid 2

    root@NAS:~#

    As you can see there's still a bond 0

    /etc/hosts has an entry "192.168.10.2 NAS.fritz.box NAS" (IP of the admin port)

    Where ist the bond0 configured and how can I delete it to create it new ? And how can I bind the hostname to the Data-IP again ?

  • I found some files in /etc/systemd/network:


    openmediavault-bond0.netdev openmediavault-enp4s0f0.network openmediavault-enp5s0f0.network openmediavault-enp8s0.network

    openmediavault-bond0.network openmediavault-enp4s0f1.network openmediavault-enp5s0f1.network

    Is this why bond0 is still active ?

    the openmediavault-bond0.network shows the correct networkconfig.


    Can I just delete the files and create a new bond after restarting the server ?

    Or could bond0 be linked somewhere else also?

  • tschensie

    Added the Label OMV 5.x

Participate now!

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