[RESOLVED] Network config on 0.5 Sardukaar

I have this affliction also. The duplicate entries, the bonding_masters does not exist, etc..
Manual bonding via the cli produces the same results. Ifenslave 2.6 is installed.

Hopefully I will explain this in a way that makes sense. I did all of this while doing dinner/bath/bedtime for my 5 and 6 year old miniature humans. Then I got excited that it worked and backed up the working files which over wrote the original backups thereby limiting my ability to accurately document it.
My bad.
If you have any questions about anything that might be unclear, confusing or just plain contradictory please let me know and I will do what I can to clarify.

I have 4 NIC's eth0-3
I was dorking around with bonding again and as soon as I would hit Apply my OMV box would drop offline.
So I would walk over to it and run OMV-Firstaid get it back online and in the web interface I would have eth0 - dhcp (the IP I was connecting to) and Bond0 - static but not responding to pings. bond0 slaves were set to eth1-3

I then went back to the terminal and stopped networking and edited /etc/network/interfaces
I removed the eth0 entry and added eth0 to bond0
Started networking and was informed that it failed to start because it could not read interfaces.
I opened interfaces in nano again and noted that eth0 was back and bond0 had the double entries again.
I could remove the doubles in bond0 and start networking, but with the same results as before.... eth0 worked, bond0 didn't.

I then checked out /etc/openmediavault/config.xml and had this

<iface>
          <uuid>acccb502-442d-11e3-944f-6c626de9cdda</uuid>
          <devicename>eth0</devicename>
          <method>dhcp</method>
          <wol>0</wol>
          <address></address>
          <netmask></netmask>
          <gateway></gateway>
          <mtu></mtu>
        </iface>
        <bondiface>
          <uuid>7fd7e5ba-3bc8-4846-bbf6-3a4ecf33f198</uuid>
          <method>static</method>
          <address>10.0.1.121</address>
          <netmask>255.255.255.0</netmask>
          <gateway>10.0.1.1</gateway>
          <method6>manual</method6>
          <address6></address6>
          <netmask6>64</netmask6>
          <gateway6></gateway6>
          <mtu></mtu>
          <wol>0</wol>
          <options></options>
          <comment></comment>
          <bondprimary>eth1</bondprimary>
          <bondmode>0</bondmode>
          <bondmiimon>100</bondmiimon>
          <bonddowndelay>200</bonddowndelay>
          <bondupdelay>200</bondupdelay>
          <slaves>eth1,eth2,eth3</slaves>
          <devicename>bond0</devicename>
        </bondiface>

So I removed the iface entry for eth0, added eth0 to the bondiface made it look like this

<bondiface>
          <uuid>7fd7e5ba-3bc8-4846-bbf6-3a4ecf33f198</uuid>
          <method>static</method>
          <address>10.0.1.121</address>
          <netmask>255.255.255.0</netmask>
          <gateway>10.0.1.1</gateway>
          <method6>manual</method6>
          <address6></address6>
          <netmask6>64</netmask6>
          <gateway6></gateway6>
          <mtu></mtu>
          <wol>0</wol>
          <options></options>
          <comment></comment>
          <bondprimary>eth0</bondprimary>
          <bondmode>0</bondmode>
          <bondmiimon>100</bondmiimon>
          <bonddowndelay>200</bonddowndelay>
          <bondupdelay>200</bondupdelay>
          <slaves>eth0,eth1,eth2,eth3</slaves>
          <devicename>bond0</devicename>
        </bondiface>

Then I went back to /etc/network and edited interfaces to look like this:

# The loopback network interface
auto lo
iface lo inet loopback
iface lo inet6 loopback


# bond... NIC Bond
auto bond0
iface bond0 inet static
    address 10.0.1.121
    gateway 10.0.1.1
    netmask 255.255.255.0
    dns-nameservers 10.0.1.1
    bond-slaves eth0 eth1 eth2 eth3
    bond-primary eth0
    bond-mode 0
    bond-miimon 100
    bond-downdelay 200
    bond-updelay 200


iface bond0 inet6 manual
    pre-down ip -6 addr flush dev bond0

Then I rebooted and everything came back up correctly.
I know next to nothing about Linux and even less about OMV but it would appear that the config.xml and interfaces weren't getting updated correctly and conflicting. I did the same thing on both of my OMV boxes and it worked both times. (Obviously I was having the same issue on both to begin with.)

Remember, if you're drinking, don't drive and if you're driving, don't drink.
in addition to backing up your files before editing them.

kevon513 - Brilliant walk through. I am pretty sure this will help others that experience issues with bonding.
I'm planning on implementing bonding as well, always nice to scout the area before starting moving into this so I know what to expect.

Sent pm for Volker to take a look at this. Hopefully this will get fixed for you guys....

Hi all,

I have some trouble with the bonding on OMV 0.5.
The difference with kevon513 for me is a fixed IP address.

I check the file : /etc/openmediavault/config.xml
->The configuration seem to be good.

I check the file : /etc/network/interfaces
-> The configuration is strange i have the line

bond-primary eth0
    bond-mode 0
    bond-miimon 100
    bond-downdelay 200
    bond-updelay 200

are repeated.
The network apear but i have an error on login. (I try omg-firstaid and same error on login).

Do you have an idea ?

I try to use only one NIC with a fixed IP, but in this case i can't login on web GUI. If i do a "omg-firstaid" and change to DHCP. I reboot and after the web GUI work.

I'm don't know what is the problem. It's a new installation.

does your config.xml show an entry for "iface" and "bondiface"?
Mine was and the NIC in the iface section was supposed to be included in the bondiface section. For me, removing the iface and adding the NIC to the bondiface section seemed to do the trick.
I don't know if I can be anymore help than that unfortunately, I'm not well versed in Linux, I think I just got lucky when I figured it out.

I check the config.xml and i have only the "boniface" I compare with the on on your post and it's nearly the same :

<bondiface>
          <uuid>6023ef9d-d251-402b-91cf-5a12330db57c</uuid>
          <method>static</method>
          <address>192.168.0.2</address>
          <netmask>255.255.255.0</netmask>
          <gateway>192.168.0.254</gateway>
          <method6>manual</method6>
          <address6></address6>
          <netmask6>64</netmask6>
          <gateway6></gateway6>
          <mtu></mtu>
          <wol>0</wol>
          <options></options>
          <comment></comment>
          <bondprimary>eth0</bondprimary>
          <bondmode>6</bondmode>
          <bondmiimon>100</bondmiimon>
          <bonddowndelay>200</bonddowndelay>
          <bondupdelay>200</bondupdelay>
          <slaves>eth0,eth1</slaves>
          <devicename>bond0</devicename>
        </bondiface>

The only other thing I did was to manually rewrite the interfaces.
Make a backup copy of /etc/network/interfaces
then replace the contents with this (assuming that your DNS server is also 192.168.0.254, if it isn't then be sure to change it)

# The loopback network interface
    auto lo
    iface lo inet loopback
    iface lo inet6 loopback


    # RR Bond0
    auto bond0
    iface bond0 inet static
        address 192.168.0.2
        gateway 192.168.0.254
        netmask 255.255.255.0
        dns-nameservers 192.168.0.254
        bond-slaves eth0 eth1
        bond-primary eth0
        bond-mode 0
        bond-miimon 100
        bond-downdelay 200
        bond-updelay 200


    iface bond0 inet6 manual
        pre-down ip -6 addr flush dev bond0

save it and reboot.
Hopefully that will work. If it doesn't... then I dunno and will have to defer to a higher power

Thanks,

It's the interface file that is not correct.
Thanks for your help

Hi,

I had the very same situation yesterday with new two OMV boxes: one HP N54L and a HP N40L, with a NC360T dual NIC each.

O each box I have three NICs: the internal one (eth0) and the dual NC360T (eth1 and 2), the last ones bonded.

When I create the bond as dynamic IP and 802.3ad (LACP), everything works, but as soon as I change the bond to static IP, the interface crashes.

The solution was to login locally and edit /etc/network/interfaces by deleting the duplicated settings for the bond0 (as the quoted example) and restart:

removed----------------------------
dns-nameservers 10.0.105.2
bond-slaves eth0 eth1
bond-primary eth0
bond-mode 0
bond-miimon 100
bond-downdelay 200
bond-updelay 200
--------------------------------------

So, the problem remains on the v0.5.30.

Thanks for a great project.

Zitat von "bysard"

I will do this when I come home from work today. What i've done so far to test exactly what you asked for:

1. Installed fresh 0.5 OMV
2. copied interfaces to interfaces.old
3. tried to create bond which resulted always in network crash
4. compared the two files - and are exactly the same!

Will post the file today.

EDIT:

Ok, I tested again by the steps described above. Last step is different then before. The files are not the same.

Old interfaces file before bond creation:
#########################################
# The loopback network interface
auto lo
iface lo inet loopback
iface lo inet6 loopback

# eth0 network interface
auto eth0
allow-hotplug eth0
iface eth0 inet static
address 10.0.105.10
gateway 10.0.105.2
netmask 255.255.255.0
dns-nameservers 10.0.105.2
iface eth0 inet6 manual
pre-down ip -6 addr flush dev eth0
#########################################

After bond creation:
#########################################
# The loopback network interface
auto lo
iface lo inet loopback
iface lo inet6 loopback

# bond0 network interface
auto bond0
iface bond0 inet static
address 10.0.105.10
gateway 10.0.105.2
netmask 255.255.255.0
dns-nameservers 10.0.105.2
bond-slaves eth0 eth1
bond-primary eth0
bond-mode 0
bond-miimon 100
bond-downdelay 200
bond-updelay 200
dns-nameservers 10.0.105.2
bond-slaves eth0 eth1
bond-primary eth0
bond-mode 0
bond-miimon 100
bond-downdelay 200
bond-updelay 200
iface bond0 inet6 manual
pre-down ip -6 addr flush dev bond0
#########################################

After the page has become inaccessible, I have rebooted OMV from console. Samba and NFS fail to start (because there is no valid ip assigned).
Also I get this error when booting:

Reconfiguring network interfaces.../etc/network/interfaces:19: duplicate option
ifdown: couldn't read interfaces file "/etc/network/interfaces"
monit: Cannot connect to the monit daemon. Did you start it with http support?
monit: Cannot connect to the monit daemon. Did you start it with http support?
monit: Cannot connect to the monit daemon. Did you start it with http support?
monit: Cannot connect to the monit daemon. Did you start it with http support?
monit: Cannot connect to the monit daemon. Did you start it with http support?
monit: Cannot connect to the monit daemon. Did you start it with http support?

After some 10 to 15 minutes after last monit error I was able to login. I ran ifconfig at it returns nothing, not even lo0. omv-first-aid command not found so I cannot repair it.
The file /etc/network/interfaces is there and as user root I can access it. I forgot to check for "interfaces" file permissions before and after bond creation as I have already re-installed OMV.

EDIT2:

Please disregard my stupidity in typing omv-firstaid. Its works, I've tried again, It repairs the network.

Alles anzeigen

I created a bug report so that Volker looks at the erro again and can hopefully can fix it finally.

http://bugtracker.openmediavault.org/view.php?id=952

Greetings
David

Great!

Thanks

From Volker:

Fixed in openmediavault 0.5.31, see http://sourceforge.net/p/openmediavault/code/849

nice .i told this month ago but no one reacted. now i can install my dual intel card again and setup the bond again. thanks god

Better late than never guys.

Volker doesn't watch the forums so often these days because he is busy coding, so we sometimes have to just fill out a bugtracker report that he gets notice of it.

Also the last request from Volker here was the output of the interfaces file, he didn't got notice of it so I added this to the request, because of that he could fix the bug now.

Greetings
David

Zitat von "WastlJ"

From Volker:
Fixed in openmediavault 0.5.31, see http://sourceforge.net/p/openmediavault/code/849

I can confirm that link bonding works with 0.5.0.31 and I am very happy about that.

Been waiting for this fix since my post here a few months (!) ago. I'll try it after I upgrade/reinstall/wait for v6. Probably the latter since .4 has been working.