Hi Red Hat;
In the 5.4 release notes, there is a section that describes changes to the
binding module in relation to ipv6:
In this update the bonding driver has been updated to the latest upstream
version. This update, however has introduced symbol/ipv6 module dependency
capabilities. Therefore, if bonding has been previously disabled (by inserting
the install ipv6 /bin/false line in the /etc/modprobe.conf file) this upgrade
to the bonding driver will result in the bonding kernel module failing to load.
The install ipv6 /bin/false line needs to be replaced with install ipv6
disable=1 for the module to load properly. (BZ#462632)
The documentation is incorrect. At least, it would seem to fail. Instead of
using:
install ipv6 disable=1
I propose that you mean to say:
options ipv6 disable=1
modprobe -nv and modprobe -v reveal the cause of failure, which is install ipv6
disable=1 does nothing with the ipv6 module.
BAD:
r...@cclinux02(/root)
# modprobe -v bonding
install disable=1
insmod /lib/modules/2.6.18-164.el5/kernel/drivers/net/bonding/bonding.ko
FATAL: Error inserting bonding
(/lib/modules/2.6.18-164.el5/kernel/drivers/net/bonding/bonding.ko): Unknown
symbol in module, or unknown parameter (see dmesg)
GOOD
r...@cclinux02(/root)
# modprobe -v bonding
insmod /lib/modules/2.6.18-164.el5/kernel/net/ipv6/ipv6.ko disable=1
insmod /lib/modules/2.6.18-164.el5/kernel/drivers/net/bonding/bonding.ko
Furthermore, there are several other ways folks may have disabled the ipv6
module (in our case, we ran /bin/true instead of false - I believe we took our
approach straight from the NSA document on securing RHEL v5).
Thanks,
Devin Nate
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
