mozillafirefix Posted October 3, 2014 Share Posted October 3, 2014 I have most recently upgraded my UnRaid hardware and hence taken the opportunity to upgrade the software to the latest beta (6.0beta10). I now have 5 GigE interfaces and have enabled round robin teaming. I noted that upon boot, only the first four interfaces were bonded. I looked into file /etc/rc.d/rc.inet1.conf and understood that it reads configurations in /boot/config/network.cfg file for a BONDNICS setting, and defaults to the first four NICS, i.e. elif [ "${BONDING}" = "yes" ]; then # bonding selected BONDNAME=${BONDNAME:="bond0"} BONDNICS=${BONDNICS:="eth0 eth1 eth2 eth3"} BONDING_MODE=${BONDING_MODE:="1"} BONDING_MIIMON=${BONDING_MIIMON:="100"} IFNAME=$BONDNAME So I edited the file /boot/config/network.cfg and appended the following line: BRNICS="eth0 eth1 eth2 eth3 eth4" Upon rebooting, I can see that my 5th interfaced is up (without the above-mentioned tweak, my 5th interface is never up). However, it was still not bonded with the other four and never took serious traffic as expected. See below: root@unraid:/boot/config# ifconfig bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500 inet 10.0.1.1 netmask 255.0.0.0 broadcast 10.255.255.255 ether 00:13:3b:0e:2d:c2 txqueuelen 0 (Ethernet) RX packets 13646293 bytes 10121024642 (9.4 GiB) RX errors 0 dropped 27092 overruns 0 frame 0 TX packets 9281072 bytes 10969887392 (10.2 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=6467<UP,BROADCAST,RUNNING,PROMISC,SLAVE,MULTICAST> mtu 1500 ether 00:13:3b:0e:2d:c2 txqueuelen 1000 (Ethernet) RX packets 3241515 bytes 2519244956 (2.3 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2320272 bytes 2740422278 (2.5 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth1: flags=6467<UP,BROADCAST,RUNNING,PROMISC,SLAVE,MULTICAST> mtu 1500 ether 00:13:3b:0e:2d:c2 txqueuelen 1000 (Ethernet) RX packets 3519554 bytes 2447589668 (2.2 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2320268 bytes 2743149598 (2.5 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth2: flags=6467<UP,BROADCAST,RUNNING,PROMISC,SLAVE,MULTICAST> mtu 1500 ether 00:13:3b:0e:2d:c2 txqueuelen 1000 (Ethernet) RX packets 3250498 bytes 2559057475 (2.3 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2320268 bytes 2739958728 (2.5 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth3: flags=6467<UP,BROADCAST,RUNNING,PROMISC,SLAVE,MULTICAST> mtu 1500 ether 00:13:3b:0e:2d:c2 txqueuelen 1000 (Ethernet) RX packets 3634726 bytes 2595132543 (2.4 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2320264 bytes 2746356788 (2.5 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth4: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether 00:13:3b:0e:90:0b txqueuelen 1000 (Ethernet) RX packets 22541 bytes 3277890 (3.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 0 (Local Loopback) RX packets 231 bytes 20864 (20.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 231 bytes 20864 (20.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Question: Is there anything else that I need to tweak in order to properly bond all my 5 interfaces? Thanks. Link to comment
jonp Posted October 3, 2014 Share Posted October 3, 2014 Oh man, this is either going to need to be answered by one of the mods or when Tom gets back next week. Interesting setup though! Link to comment
mozillafirefix Posted October 3, 2014 Author Share Posted October 3, 2014 I think I've just solved my own puzzle. Previously I looked into the wrong section of the inet1 configuration file. Since I am bonding the NICs, the correct line to append to network.cfg should read: BONDNICS="eth0 eth1 eth2 eth3 eth4" Key: BOND instead of BR (bridge) After this change, my ifconfig looks like: root@unraid:~# ifconfig bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500 inet 10.0.1.1 netmask 255.0.0.0 broadcast 10.255.255.255 ether 00:13:3b:0e:2d:c2 txqueuelen 0 (Ethernet) RX packets 6085 bytes 1152443 (1.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 6016 bytes 1929343 (1.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 00:13:3b:0e:2d:c2 txqueuelen 1000 (Ethernet) RX packets 1197 bytes 231380 (225.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1207 bytes 385042 (376.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 00:13:3b:0e:2d:c2 txqueuelen 1000 (Ethernet) RX packets 1224 bytes 229679 (224.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1203 bytes 386529 (377.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth2: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 00:13:3b:0e:2d:c2 txqueuelen 1000 (Ethernet) RX packets 1214 bytes 232531 (227.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1201 bytes 387409 (378.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth3: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 00:13:3b:0e:2d:c2 txqueuelen 1000 (Ethernet) RX packets 1223 bytes 230013 (224.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1205 bytes 384639 (375.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth4: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 00:13:3b:0e:2d:c2 txqueuelen 1000 (Ethernet) RX packets 1227 bytes 228840 (223.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1200 bytes 385724 (376.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 0 (Local Loopback) RX packets 76 bytes 6424 (6.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 76 bytes 6424 (6.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 And I am a happy camper now! Link to comment
jonp Posted October 3, 2014 Share Posted October 3, 2014 Nice! Marking resolved then? Link to comment
mozillafirefix Posted October 4, 2014 Author Share Posted October 4, 2014 Yes, this particular issue is resolved. Now I am exploring the possibility of connecting different NICs to different subnetworks, and hence having > 1 IP addresses for the same box. Anyone has done this before? Link to comment
kciaccio Posted December 22, 2014 Share Posted December 22, 2014 That is awesome. Is there an script out there to bond just the two nics on my motherboard? I have a managed switch on the way. Link to comment
fmlouder Posted January 25, 2015 Share Posted January 25, 2015 hello i know this has been resolved but does that mean with your 4 interfaces you get 4 gig bandwith? im kinda thinking about switching from open media vault which has been a lil bit of a pain for bonding never really worked as i hope but yea if someone could answer that it would be really really helpfull Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.