FS#24802 - [netcfg] Add support for network bonding
Attached to Project:
Arch Linux
Opened by Massimiliano Torromeo (mtorromeo) - Monday, 20 June 2011, 17:08 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Saturday, 15 October 2011, 10:24 GMT
Opened by Massimiliano Torromeo (mtorromeo) - Monday, 20 June 2011, 17:08 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Saturday, 15 October 2011, 10:24 GMT
|
Details
Netcfg doesn't seem to support network bonding.
This is probably to be considered more like a bug than a feature request. Since netcfg is meant to replace the old networking script I think that it should provide at least the same level of functionalities. |
This task depends upon
Closed by Rémy Oudompheng (remyoudompheng)
Saturday, 15 October 2011, 10:24 GMT
Reason for closing: No response
Additional comments about closing: Partial implementation in netcfg 2.7
Saturday, 15 October 2011, 10:24 GMT
Reason for closing: No response
Additional comments about closing: Partial implementation in netcfg 2.7
This was possible with the old network scripts, as described here: https://wiki.archlinux.org/index.php/Configuring_Network#Bonding
If netcfg exists within a git repo I can push the changes to you.
bonding (0.7 KiB)
- https://github.com/reactor10/archlinux-netcfg
1) Adding the module to the kernel (not part of the script)
$ modprobe bonding
2) Putting the Interface up and Initialising it with an IP
$ ip addr add 192.168.100.33/24 brd + dev bond0
$ ip link set dev bond0 up
3) Make eth3 and eth2 slaves of bond0
$ ifenslave bond0 eth2 eth3
I have almost directly translated this, however using the in-build netcfg functions
2) bring_interface up "$INTERFACE"
2) "$CONN_DIR/ethernet" up "$1"
3) for bond_client in $BOND_INTERFACES; do
3) bring_interface up "$INTERFACE"
3) $IFENSLAVE $INTERFACE $bond_client
3) done
$BOND_INTERFACES are described in the profile.