From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] ipv6: use a random ifid for headerless devices
Date: Fri, 04 Dec 2015 11:41:52 +0100 [thread overview]
Message-ID: <1449225712.287884.457895729.21AD000E@webmail.messagingengine.com> (raw)
In-Reply-To: <87vb8fjpou.fsf@nemi.mork.no>
Hello,
On Thu, Dec 3, 2015, at 20:29, Bjørn Mork wrote:
> Hannes Frederic Sowa <hannes@stressinduktion.org> writes:
>
> > I see no problem with the patch as it eases operating those devices. I
> > would also suggest storing the ifid in the inet6_dev so it does only
> > change during device creation and destruction. Otherwise I would
> > recommend to use stable privacy addresses to generate the link local
> > addresses. EUI-48 based LL creation should hopefully not be used anymore
> > soon.
>
> Thanks for commenting on this. Yes, the stable privacy addresses looks
> like they will solve this and other problems. But enabling them require
> an adminstrator action.
>
> After looking more at addrconf, I started wondering if we couldn't abuse
> ipv6_generate_stable_address() for this purpose? We could add a new
> addr_gen_mode which would trigger automatic generation of a secret if
> stable_secret is uninitialized. This would be good enough to ensure
> stability until the interface is destroyed. And it would still allow
> the adminstrator to select IN6_ADDR_GEN_MODE_STABLE_PRIVACY by entering
> a new secret.
I am fine with your proposal but I would really like to see it only
happen on the per-interface stable_secret instance.
Thanks,
Hannes
next prev parent reply other threads:[~2015-12-04 10:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 11:55 [RFC] ipv6: use a random ifid for headerless devices Bjørn Mork
2015-11-30 12:01 ` 吉藤英明
2015-11-30 13:55 ` Bjørn Mork
2015-12-01 7:39 ` YOSHIFUJI Hideaki
2015-12-01 11:22 ` Hannes Frederic Sowa
2015-12-03 19:29 ` Bjørn Mork
2015-12-04 10:41 ` Hannes Frederic Sowa [this message]
2015-12-05 19:02 ` Bjørn Mork
2015-12-08 13:44 ` Hannes Frederic Sowa
2015-12-08 18:57 ` Bjørn Mork
2015-12-14 21:30 ` Hannes Frederic Sowa
2015-12-14 21:43 ` Bjørn Mork
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=1449225712.287884.457895729.21AD000E@webmail.messagingengine.com \
--to=hannes@stressinduktion.org \
--cc=bjorn@mork.no \
--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).