Not only that, but these instructions are confusing. The differences between the two options are left unexplained, and the reader isn't told the benefits of each, if any. - KitchM 21:30, 24 October 2010 (EDT)
- if you just stop the module from being loaded during boot, it still gets autoloaded by various programs (same thing happens with bluetooth modules and gnome) - this article is correct, the beginner's guide method will likely end up with the module loaded anyway after boot thestinger 23:08, 24 October 2010 (EDT)
Another possibility seems to be adding "!ipv6" to the modules line in rc.conf. It would seem that this would keep the original module from loading at all. Any comments anyone? - KitchM 17:06, 1 November 2010 (EDT)
- it stops the module from loading during boot, but the udev will end up loading it anyway when you receive any ipv6 packets or a program tries to use ipv6 (it might work if you have a very minimal environment and your router doesn't send ipv6 stuff by default) thestinger 17:17, 1 November 2010 (EDT)
- So the basic concept appears that it can't actually be stopped from loading, since it will load whenever there is ipv6 activity. And since that cannot be stopped, one never knows when that might occur?
- I had understood that one can configure her ethernet settings to only use ipv4. But if that is so, then ipv6 will never activate in the first place. Or is that wrong? Are we getting into some sort of weird catch-22? - KitchM 18:16, 1 November 2010 (EDT)
The page only mentions how to setup static IP address with netcfg. Shouldn't some explanation about the default network daemon also be present ? --Gyscos 12:44, 27 April 2012 (UTC)
Disabling IPv6 by adding to GRUB
ipv6.disable=1 to the kernel line disables the whole IPv6 stack.
To add this using grub, add ipv6.disable=1 to
/etc/default/grub in the GRUB_CMDLINE_LINUX_DEFAULT= line, then regenerate grub.cfg with:
# grub-mkconfig -o /boot/grub/grub.cfg