Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#25730 - [initscripts] bonding of multiple NICs doesn't work
Attached to Project:
Arch Linux
Opened by Christian Stadegaart (c.stadegaart) - Tuesday, 23 August 2011, 14:34 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 23 August 2011, 15:06 GMT
Opened by Christian Stadegaart (c.stadegaart) - Tuesday, 23 August 2011, 14:34 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 23 August 2011, 15:06 GMT
|
DetailsDescription:
Bonding of multiple NICs isn't correctly supported by the /etc/rc.d/network script. It is not correctly implemented. Legacy support for bonding works fine, but if an end-user uses the newer configuration method for /etc/rc.conf, bonding will fail. I am not sure if this is since the implementation of iproute2 in favour of the now deprecated iproute, because I just started using the bond feature, but this might be possible. Additional info: * package version(s): 2011.07.03-1 * config and/or log files etc. === /etc/rc.conf === MODULES=(... bonding ...) interface=bond0 address= netmask= gateway= === /etc/conf.d/bonding === bond_bond0="alias_nic1 alias_nic2 ..." BOND_INTERFACES=(bond0) === /etc/modprobe.d/bonding.conf === options bonding miimon=100 Steps to reproduce: Install ifenslave. Bond two or more NICs into bond0. Either give bond0 interface a static IP or use a DHCP server. With my config file, /etc/rc.d/network will setup bond0 interface with DHCP. With no altered files, the bond will not be initialised on startup and /sbin/dhcpcd will not succeed since bond0 interface is not ready (although it does exist, since the module is loaded). I did not test a static IP, but my guess of the outcome is that bond0 interface will have an address, but will not work since it doesn't have any enslaved interfaces initialised. In order for my bond0 interface to work, I edited /etc/rc.d/network. I attached the 'diff -c' output, so you can patch it if needed. I'm pretty sure this might work a a solution, but some additions may be needed. |
This task depends upon
Closed by Dave Reisner (falconindy)
Tuesday, 23 August 2011, 15:06 GMT
Reason for closing: Not a bug
Tuesday, 23 August 2011, 15:06 GMT
Reason for closing: Not a bug
Comment by Dave Reisner (falconindy) -
Tuesday, 23 August 2011, 15:06 GMT
Bonding is not supported through the new interface in /etc/rc.conf. You can use the legacy bonding support until something such as netcfg supports it (we won't remove legacy support until there's an alternative).
diff