diff options
Diffstat (limited to 'README.bonding')
| -rw-r--r-- | README.bonding | 52 |
1 files changed, 1 insertions, 51 deletions
diff --git a/README.bonding b/README.bonding index 09733cc..5f14e50 100644 --- a/README.bonding +++ b/README.bonding @@ -1,4 +1,4 @@ -Bonding (link aggrigation) +Bonding (link aggregation) ========================== Features @@ -9,56 +9,6 @@ Features * Custom bonding module options can be provided using the generic parameter IFOPTS[x] in the configuration file. - -Implementation --------------- -[This section can be removed from the final README.bonding as it relates to - implimentation by Pat rather than user level configuration] - -Pat should add a /lib/modprobe.d/bonding.conf (preferred) or -/etc/modprobe.d/bonding.conf file to a package (probably network-scripts), with -content: - options bonding max_bonds=0 - options rtnl-link-bond max_bonds=0 -in order to disable the automatic creation of a bond0 interface when the kernel -module is loaded. - -Rationale: Even though the bond0 interface may be scheduled for creation -because it's configured in rc.inet1.conf, having the interface in an up state -before configuration will prevent it from being configured due to rc.inet1's -checking of interface state before going through the process of setting up the -interface. - -This check is necessary in rc.inet1 because rc.inet1 has no way of knowing -whether the interface has been brought up by itself or by some other means - -there is no state information stored by rc.inet1, which prevents it from -knowing. It is also not possible to rely on the interface being configured -with an IP address to determine if it has been configured or not - a bond -interface may be used as part of a bridge, and would thus not have an IP -configured to validate against. - -Effects: Previous versions of Slackware followed the default behaviour when -loading the bonding module, and would automatically create a bond0 interface -for the user to configure. This behaviour would now change to prevent a bond0 -interface being created at load time in order for rc.inet1 to be able to -configure a user defined bond0 interface in rc.inet1.conf at a later time. - -Since Slackware has never had support for bond interfaces in previous versions, -the automatic creation of a bond interface has never been a defined behaviour - -users should not have relied on that behaviour. - -Effects if not used: In its present form, rc.inet1 checks whether an interface -is up before it tries to configure it based on the interfaces present in -rc.inet1.conf - rc.inet1 will not try to reconfigure an interface which is up -and running, instead issuing an debug message that the interface is already up -when being run with any of the 'start' options. - -Without the inclusing of the bonding.conf options file, rc.inet1 would be -unable to work with a bond0 interface in it's present form. It is also highly -unlikely that rc.inet1 could be coded to *not* check whether an interface is up -before trying to configure it - this check is fundamental to the way it works. - - Configuration ------------- Bonding interfaces can be configured via two new bond specific parameters in |