netdev - Re: [PATCH] ipv6: addrconf: clear IPv6 addresses and routes when losing link

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTim-2ghTVVEaJesMkXcRL-eCPBoHkehKF8HXhyK+@mail.gmail.com>
Date:	Thu, 28 Oct 2010 15:23:29 -0700
From:	Lorenzo Colitti <lorenzo@...gle.com>
To:	Maciej Żenczykowski <zenczykowski@...il.com>
Cc:	netdev@...r.kernel.org, Brian Haley <brian.haley@...com>
Subject: Re: [PATCH] ipv6: addrconf: clear IPv6 addresses and routes when
 losing link

On Wed, Oct 27, 2010 at 1:39 PM, Maciej Żenczykowski
<zenczykowski@...il.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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html