Jason Joines wrote:

Jason Joines wrote:

...

There was a USE_IPV6 variable in the 9.3 /etc/sysconfig/network/config that could be set to "no" to disable IPv6. There is no such variable in the 10.0 /etc/sysconfig/network/config. How do you disable IPv6 in 10.0?

Thanks,

Jason Joines ==============================

Looking at the stuff in 9.3 it looked like the command "ip -6 address flush dev eth0" would work. Running it manually does work just fine. I added the USE_IPV6=no variable to the /etc/sysconfig/network/config file on the 10.0 box. Then this was added to the /sbin/ifup script on the 10.0 box in the same place as it was found on the 9.3 box:

if [ "$SCRIPTNAME" != ifstatus -a "$USE_IPV6" = no ] ; then ip -6 address flush dev $INTERFACE fi

With this I could manually go down to runlevel 1 and then back up to runlevel 3 and see that there were no ipv6 addresses assigned to any NICs. However, if I rebooted the box, the interfaces would again have ipv6 when it came back up.

I tried adding this script to flush ipv6 to /etc/sysconfig/network/if-up.d/

#!/bin/bash for J in `ifconfig | grep Link | awk '{print $1}'` do echo flushing IPv6 from $J ip -6 addr flush dev $J done

Again, running it manually works fine. However, when the box boots I see the output "nothing to flush" for each interface and then they still have ipv6 addresses when the box if completely up. Seems like the ipv6 stuff must be happening after these scripts run but I haven't got it sorted it out yet.

Are there any ways of disabling ipv6 support in the kernel at boot? Any other good way to disable it?

Jason Joines =================================

The solution posted by Joachim Schrod ( http://thread.gmane.org/gmane.linux.suse.general/158968 ) works great: " Add to modprobe.conf.local: # We don't need and don't want no stinkin' IPv6. install sit0 /bin/true install ipv6 /bin/true install net-pf-10 /bin/true "

On Friday 11 November 2005 06:06, Michael James wrote:

Also, could someone explain how modprobe.conf, modprobe.conf.local, and modprobe.d/*.conf work, or point me to some doco. Not "one includes the other" but why : install net-pf-10 /bin/true turns it OFF.

This has been discussed many times on this list The "install" directive tells modprobe what to do when it tries to load the module *instead of* loading the module. In other words, if you don't have an install directive for the module, modprobe will just load it. If you do, then modprobe will run the command(s) you have listed there instead In this case, it will simply run /bin/true, which does nothing and returns a value that indicates that it was successful. In English it looks a little backwards, and you are tempted to use /bin/false instead, but that returns a value that indicates that it fails, which causes all sorts of problems. You want something there that returns "success" You could use any command there, and it will get run instead of loading the module. You can also use it to run "prerequisites", things that need to be done before loading the module. Then you would end the sequence with the command "modprobe --ignore-install <module name>" which will load the module without going to the "install" directive