All of lore.kernel.org
 help / color / mirror / Atom feed
From: YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: hideaki.yoshifuji@miraclelinux.com, network dev <netdev@vger.kernel.org>
Subject: Re: [RFC] ipv6: use a random ifid for headerless devices
Date: Tue, 1 Dec 2015 16:39:11 +0900	[thread overview]
Message-ID: <565D4E9F.2000605@miraclelinux.com> (raw)
In-Reply-To: <87r3j74mnh.fsf@nemi.mork.no>

Hi,

Bjørn Mork wrote:
> 吉藤英明 <hideaki.yoshifuji@miraclelinux.com> writes:
> 
>>>> +static int addrconf_ifid_random(u8 *eui, struct net_device *dev)
>>> +{
>>> +       get_random_bytes(eui, 8);
>>> +       eui[0] |= 0x02;
>>> +       return 0;
>>> +}
>>> +
>>
>> Since random identifier is locally assigned, drop the global bit
>> instead if setting it.
> 
> Yes, definitely. Thanks.  I'm considering reusing __ipv6_regen_rndid()
> which already does this correctly, and also avoids some locally assigned
> addresses with special meanings.
> 
> Another issue with the initial RFC is that every prefix will have a new
> random ifid, which isn't necessarily what the users expect.  I wonder if
> it would be acceptable to abuse the rndid field for storing a "permanent"
> random ifid?

Well, I think we should introduce ifid in inet6_dev.
After that we could use it from other ifid methods.

--yoshfuji

> 
> 
> Bjørn
> 

-- 
Hideaki Yoshifuji <hideaki.yoshifuji@miraclelinux.com>
Technical Division, MIRACLE LINUX CORPORATION

  reply	other threads:[~2015-12-01  7:39 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 [this message]
2015-12-01 11:22 ` Hannes Frederic Sowa
2015-12-03 19:29   ` Bjørn Mork
2015-12-04 10:41     ` Hannes Frederic Sowa
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=565D4E9F.2000605@miraclelinux.com \
    --to=hideaki.yoshifuji@miraclelinux.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.