From: Brian Haley <brian.haley@hp.com>
To: "Kolbjørn Barmen" <linux@kolla.no>
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>,
davem@davemloft.net, yoshfuji@linux-ipv6.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] IPv6: Add 'autoconf' and 'disable_ipv6' module parameters
Date: Wed, 25 Mar 2009 11:28:06 -0400 [thread overview]
Message-ID: <49CA4D86.4070403@hp.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0903250526050.6682@firda.kolla.no>
Kolbjørn Barmen wrote:
> On Tue, 24 Mar 2009, 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'...
>
> I bet that should have been "net.ipv6.conf.all.disable_ipv6=1" yes. :)
No, the module parameter disabled it, but we need to re-enable the
.all.disable_ipv6 knob in order for lo to be able to configure itself.
If I follow Vlad's advice of only setting the .default knob then you
won't have to do this.
>> 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.
>
> Isnt this the normal way anyways, or do new interfaces send some sort of
> "I'm new here, give me a prefix and router announcement, please!" normally
> when they go online? If so, maybe that should be done here as well.
I'll see about putting in a callback to send a router solicitation. But
on the flip side if someone changes eth0.disable_ipv6=0 to 1, we won't
be removing the address either. An ifdown/ifup cycle would remove the
need for us to do anything here.
-Brian
next prev parent reply other threads:[~2009-03-25 15:28 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 [this message]
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
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=49CA4D86.4070403@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).