Hide Forgot
Description of problem: In the F18 System Administrators Guide (and shouldn't that have an apostrophe after the 's'?), ยง8.2.3 it says: ----------------------- For a channel bonding interface to be valid, the kernel module must be loaded. To ensure that the module is loaded when the channel bonding interface is brought up, create a new file as root named bonding.conf in the /etc/modprobe.d/ directory. Note that you can name this file anything you like as long as it ends with a .conf extension. Insert the following line in this new file: alias bondN bonding Replace N with the interface number, such as 0. For each configured channel bonding interface, there must be a corresponding entry in your new /etc/modprobe.d/bonding.conf file. ------------------------ This is not true. The network scripts in /etc/sysconfig/network-scripts define the function install_bonding_driver which is called whenever a bonding slave or master is detected. Version-Release number of selected component (if applicable): F18 How reproducible: Always Steps to Reproduce: 1. Configure a bond 2. Miss out the step that adds "alias bondN bonding" to a modprobe conf file 3. Notice that bonding actually works (NetworkManager notwithstanding) Actual results: works as expected when ignoring the documentation Expected results: works as expected when not ignoring the documentation Additional info: The install_bonding_driver has been around for a while, but the final piece of code to make it reliable comes from, I think, * Mon Aug 15 2011 Petr Lautrbach <plautrba> 9.03.24-1 ... - make sure the bond exists when we bring up the slaves. (#694501) (commit id 3de0e06afda2e572d0952941498446fdda7f3f42)
Hello John Thanks for taking the time to report this. About the name, this is before my time but I believe the name without apostrophe was decided on on the grounds of style. Regards Stephen
Hello I have removed the text as explained in #c0 I have also removed this text from the section "Using Channel Bonding" in the chapter "Specific Kernel Module Capabilities": = = = As root, create a new file named bonding.conf in the /etc/modprobe.d/ directory. Note that you can name this file anything you like as long as it ends with a .conf extension. Insert the following line in this new file: alias bondN bonding Replace N with the interface number, such as 0. For each configured channel bonding interface, there must be a corresponding entry in your new /etc/modprobe.d/bonding.conf file] = = = thanks again for raising the bug
WORKSFORME, no explicit modprobe.conf-ing required.
Hello Note that this section was moved to the Networking Guide http://docs.fedoraproject.org/en-US/Fedora/20/html/Networking_Guide/sec-Using_Channel_Bonding.html Thank you