From: Lorenzo Colitti <lorenzo@google.com>
To: "Maciej Żenczykowski" <zenczykowski@gmail.com>
Cc: netdev@vger.kernel.org, Brian Haley <brian.haley@hp.com>
Subject: Re: [PATCH] ipv6: addrconf: clear IPv6 addresses and routes when losing link
Date: Thu, 28 Oct 2010 15:23:29 -0700 [thread overview]
Message-ID: <AANLkTim-2ghTVVEaJesMkXcRL-eCPBoHkehKF8HXhyK+@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=AyYrmSWDTZVWb2s+jgnyjNyHo-fkV4U+Fm45n@mail.gmail.com>
On Wed, Oct 27, 2010 at 1:39 PM, Maciej Żenczykowski
<zenczykowski@gmail.com> wrote:
> static int __ipv6_regen_rndid(struct inet6_dev *idev) {
> get_random_bytes(idev->rndid, sizeof(idev->rndid));
> idev->rndid[0] &= ~0x02;
>
> certainly seem to point towards it being totally random.
It's random, but the random interface ID is a property of the
interface, not of the address, and thus survives interface up/down:
# ip -6 a li dev wlan0 secondary
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 2620:0:1000:fd01:952f:2586:ed6f:408c/64 scope global
secondary dynamic
valid_lft 604363sec preferred_lft 85363sec
# ip link set wlan0 down
# ip -6 a li dev wlan0 secondary
# ip link set wlan0 up
# ip -6 a li dev wlan0 secondary
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 2620:0:1000:167d:952f:2586:ed6f:408c/64 scope global
secondary dynamic
valid_lft 604799sec preferred_lft 85799sec
next prev parent reply other threads:[~2010-10-28 22:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 2:08 [PATCH] ipv6: addrconf: clear IPv6 addresses and routes when losing link Lorenzo Colitti
2010-10-26 4:38 ` Stephen Hemminger
2010-10-26 5:44 ` Lorenzo Colitti
2010-10-26 15:28 ` Stephen Hemminger
2010-10-26 17:11 ` Lorenzo Colitti
2010-11-02 2:54 ` Dan Williams
2010-11-05 6:40 ` Lorenzo Colitti
2010-10-26 16:58 ` Brian Haley
2010-10-26 17:09 ` Lorenzo Colitti
2010-10-26 17:10 ` David Miller
2010-10-26 17:13 ` Lorenzo Colitti
2010-10-26 17:21 ` David Miller
2010-10-26 17:37 ` Lorenzo Colitti
2010-10-26 17:47 ` David Miller
2010-10-26 17:50 ` Lorenzo Colitti
2010-10-26 17:55 ` David Miller
2010-10-26 18:02 ` Lorenzo Colitti
2010-10-26 18:21 ` David Miller
2010-11-02 2:50 ` Dan Williams
2010-10-26 18:17 ` Lorenzo Colitti
2010-10-26 18:23 ` David Miller
2010-10-26 22:53 ` Lorenzo Colitti
2010-10-27 15:51 ` David Miller
2010-10-27 16:01 ` Lorenzo Colitti
2010-10-27 16:05 ` David Miller
2010-10-27 2:31 ` Brian Haley
2010-10-27 8:35 ` Maciej Żenczykowski
2010-10-27 16:03 ` Lorenzo Colitti
2010-10-27 20:39 ` Maciej Żenczykowski
2010-10-28 22:23 ` Lorenzo Colitti [this message]
2010-10-28 22:41 ` Lorenzo Colitti
2010-10-28 22:50 ` Maciej Żenczykowski
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=AANLkTim-2ghTVVEaJesMkXcRL-eCPBoHkehKF8HXhyK+@mail.gmail.com \
--to=lorenzo@google.com \
--cc=brian.haley@hp.com \
--cc=netdev@vger.kernel.org \
--cc=zenczykowski@gmail.com \
/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).