disable/enable ipv6 connectivity
Hello everyone,
I just finished setting up my slack machine as a home server (printers & files) and I noticed that I have an IPv6 address (from ifconfig)... I didn't know I did. I used to work in tech support and when a windows or OSx machine didn't connect properly on a LAN, disabling IPV6 was a common troubleshooting step. Anyway, my questions is: Is there a way to easily turn inet6 connectivity off/on in Slackware? (I want to keep the ability to get an IPv6, we will all use those in the future) |
From this http://www.linuxquestions.org/questi...1/#post4207411
i.e. 'echo "blacklist ipv6" > /etc/modprobe.d/ipv6.conf' and IPv6 will be disabled on next boot. Just remove the file to reenable IPV6. |
that worked, thank you allend :D
|
That does not work anymore in Slackware 14 RC4.
Code:
"blacklist ipv6" > /etc/modprobe.d/ipv6.conf' Since /etc/modprobe.d seems to be deprecated I dont know anymore how to control what modules are loaded what not. The path /lib/modprode.d contains some files but there is nothing about ipv6 and others that I dont need. |
Yes, I discovered that too the other day. This is what I do now
Code:
gazl@ws1:~$ cat /etc/modprobe.d/ipv6.conf |
I think that with "options ipv6 disable=1" it still loads the ipv6 module, but ipv6 is "administratively disabled" (check messages). I use this:
Code:
alias net-pf-10 off |
IPv6 support is mandantory now: see RFC 6540. Disabling IPv6 serves no purpose. By disabling it, you deliberately break your network configuration.
The "IPv6 address" you see is just a link-local one. It's harmless. |
@petri, Yes, what I do still results in the ipv6 module being loaded, but presumably it is being loaded because something is dependent upon it. Using disable=1, or if that is too extreme disable_ipv6=1 seems cleaner to me than using the 'alias off' definitions.
@jstn, that RFC is really just the iETF saying "We'd *really* like everyone to get off their arses and start transitioning to ipv6, NOW! Please.", but until my upstream ISP transitions it makes absolutely no sense for me to enable ipv6 locally, and in-fact when I've tried leaving it enabled in the past it has caused my browsing to slowdown (presumably while the ipv6 resolver tries and fails to do a lookup before falling back to ipv4). When my ISP supports ipv6, I'll enable ipv6, until then, it is staying disabled. |
I had problems blacklisting the modules, so I added this to "/etc/sysctl.conf":
Quote:
|
|
Quote:
Quote:
|
All times are GMT -5. The time now is 06:18 PM. |