From: Brian Haley <brian.haley@hp.com>
To: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: disabling ipv6 (when ipv6 module is already loaded or built in)
Date: Fri, 25 Mar 2011 16:22:08 -0400 [thread overview]
Message-ID: <4D8CF970.7020601@hp.com> (raw)
In-Reply-To: <201103251817.04583.a.miskiewicz@gmail.com>
On 03/25/2011 01:17 PM, Arkadiusz Miskiewicz wrote:
>
> Hi,
>
> There are two options for disabling some ipv6 functionality in ipv6 module -
> disable and disable_ipv6. The second option is also available as sysctl and
> can be switched runtime.
>
> First is nicer because it also prevents apps from creating sockets by using
> socket(AF_INET6, ...). Various apps use AF_INET6 socket creation to deterine
> if ipv6 is supported on the system. Unfortunately "disable" one doesn't exist
> as sysctl and this is a problem.
>
> Is it possible to make "disable" sysctl option, too? Currently there is no
> runtime way to disable ipv6 (or I'm unaware of such way).
Not really, the module parameter causes IPv6 to be loaded just enough to
allow other modules that rely on it to load, but it never registers
any of the protocol handlers, sysctls, tables, etc. to make it usable.
And the IPv6 module isn't unloadable, so you have to reboot to change
this setting.
When there are no addresses it's not very usable since you can't send
out packets...
-Brian
next prev parent reply other threads:[~2011-03-25 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 17:17 disabling ipv6 (when ipv6 module is already loaded or built in) Arkadiusz Miskiewicz
2011-03-25 20:22 ` Brian Haley [this message]
2011-03-25 22:53 ` Arkadiusz Miskiewicz
2011-03-25 22:56 ` David Miller
2011-03-27 21:19 ` Arkadiusz Miskiewicz
2011-03-27 21:24 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D8CF970.7020601@hp.com \
--to=brian.haley@hp.com \
--cc=a.miskiewicz@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).