Robert A. Rawlinson wrote:
Darryl Gregorash wrote:
Robert A. Rawlinson wrote:
Change
alias net-pf-10 ipv6
to
alias net-pf-10 ipv6 install ipv6 /bin/true
Bob Rawlinson
I have a Suse 9.1 with the 2.4 kernal but I updated it to the 2.6 kernal. So I had both files mentioned. So I made the change in both files and rebooted. I still get the ipv6 and I still have the problem. Bob Rawlinson
All I can suggest, again, is that you check /etc/sysconfig/sysctl to see if things like IPV6_PRIVACY are set to "yes". If any of them are (there are 2 in 9.0) then the ipv6 module will be loaded anyway, in /etc/init.d/boot.ipconfig, no matter what it says in your modules.conf or whatever it may be called.
I have checked and all those are correct. Still ipv6 IS running. I looked in /etc/sysconfig/sysctl and /etc/init.d/boot.ipconfig and I could see no where it should start ipv6. The system I have in Ohio did not have this problem. Only the system I have with me in Tucson Az. I think the DSL line back home handled the ipv6 but the WiFi I have here will not.
You have nothing in /etc/init.d/boot.ipconfig that looks like this? # Enable IPv6 forwarding ? # LOAD_IPV6="no" case $IPV6_FORWARD in yes) LOAD_IPV6="yes" ;; esac case $IPV6_PRIVACY in yes) LOAD_IPV6="yes" ;; esac test "$LOAD_IPV6" = "yes" && /sbin/modprobe ipv6 >/dev/null 2>&1 # If not, then I believe similar code must be elsewhere in one of the /etc/init.d/boot* files. Try grep "modprobe ipv6" /etc/init.d/boot* and if nothing turns up, also grep for "insmod ipv6". Those 2 variables, IPV6_FORWARD and IPV6_PRIVACY, are in /etc/sysconfig/sysctl in 9.0, but they may have been moved in 9.1. Grep recursively for "IPV6_" in /etc/sysconfig/* They may of course, be renamed, so look at the script that turns up when you grep for "modprobe". Please don't think I am being condescending or arrogant or anything here, Bob. I don't want to think how many wrong turns I took until I stumbled onto this (plus the part in SuSEfirewall2 where ip6_tables is loaded, no matter what you do with ipv6 :-) ) I never encountered this myself; as soon as I turned it off in modules.conf, ipv6 stopped being loaded. But that is only what always gets loaded when the kernel is loaded, and other places abound where a module can optionally get loaded. The above is one such instance, and I am positive you must have the same, or a similar, instance on your system. In fact, I think it might have been your first description of this problem that got me looking into all this. It *has* to be there, or failing that, copy modules.conf (or whatever it's called with 2.6) to *.old, edit out ALL the ipv6 references, and boot with that. If ipv6 still gets loaded, then we haven't looked far enough to find where :-)