From: Brian Haley <brian.haley@hp.com>
To: Vlad Yasevich <vladislav.yasevich@hp.com>
Cc: davem@davemloft.net, yoshfuji@linux-ipv6.org, linux@kolla.no,
netdev@vger.kernel.org
Subject: Re: [PATCH] IPv6: Add 'autoconf' and 'disable_ipv6' module parameters
Date: Wed, 25 Mar 2009 11:22:33 -0400 [thread overview]
Message-ID: <49CA4C39.7020701@hp.com> (raw)
In-Reply-To: <49C99315.6070504@hp.com>
Vlad Yasevich wrote:
> Brian Haley wrote:
>> This is the quick and easy patch to add autoconf and
>> disable_ipv6 module parameters to IPv6. I don't think anything
>> more complicated is needed, assuming you play with the /etc
>> configuration files.
>>
>> For example, if you wanted to enable IPv6 just on 'lo' you
>> would:
>>
>> 1. Add "ipv6" to /etc/modules (if you don't, step #3 might fail)
>>
>> 2. Add this to /etc/modprobe.conf:
>>
>> options ipv6 disable_ipv6=1
>>
>> 3. Add these to /etc/sysctl.conf:
>>
>> net.ipv6.conf.all.disable_ipv6=0
>> net.ipv6.conf.lo.disable_ipv6=0
>
> This is kind of confusing. First you say, disable IPv6, then you say enable IPv6, but
> nothing happens. Unless you typo-ed the 'all.disable_ipv6 = 0'...
Well, at least on my test system, this worked. Loading the IPv6 module
with disable_ipv6=1 sets the .all and .default (and all interfaces) to
disable, then sysctl turns them back on selectively. If you don't
enable the .all.disable_ipv6 knob nothing will actually work - see the
change in addrconf_prefix_rcv(). You still have to enable it on each
interface for anything to happen.
> Also, it looks like if someone decides to switch IPv6 back on for a particular
> interface, they would have to wait until the next RA to get an address. Not an
> optimum solution.
Yes, if someone later-on enables IPv6 on an interface they'll need to
ifdown/ifup.
>> + } else {
>> + /* these will be inherited by all namespaces */
>> + all->autoconf = dflt->autoconf = ipv6_defaults.autoconf;
>> + all->disable_ipv6 = dflt->disable_ipv6 =
>> + ipv6_defaults.disable_ipv6;
>
> Why set 'all'? Since no interfaces are created yet, setting dflt accomplishes
> what you want.
Yeah, that's probably not necessary, I assumed if the user passed the
parameter and saw .all.foo different than .default.foo they might be
confused.
-Brian
prev parent reply other threads:[~2009-03-25 15:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 1:49 [PATCH] IPv6: Add 'autoconf' and 'disable_ipv6' module parameters Brian Haley
2009-03-25 2:12 ` Vlad Yasevich
2009-03-25 4:28 ` Kolbjørn Barmen
2009-03-25 11:51 ` Vlad Yasevich
2009-03-25 15:28 ` Brian Haley
2010-01-19 23:45 ` IPv6 autoconf/accept_ra default values - revisited Kolbjørn Barmen
2010-01-20 16:55 ` Brian Haley
2010-02-16 21:58 ` Kolbjørn Barmen
2010-02-17 16:54 ` Brian Haley
2009-03-25 12:36 ` [PATCH] IPv6: Add 'autoconf' and 'disable_ipv6' module parameters Vlad Yasevich
2009-03-25 15:54 ` Brian Haley
2009-03-25 15:22 ` Brian Haley [this message]
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=49CA4C39.7020701@hp.com \
--to=brian.haley@hp.com \
--cc=davem@davemloft.net \
--cc=linux@kolla.no \
--cc=netdev@vger.kernel.org \
--cc=vladislav.yasevich@hp.com \
--cc=yoshfuji@linux-ipv6.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).