netdev - Re: ipv6:remove ipv6 global address after the interface is down

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: <20140401093544.GF24150@order.stressinduktion.org>
Date:	Tue, 1 Apr 2014 11:35:44 +0200
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	zhuyj <zyjzyj2000@...il.com>
Cc:	Paul Gortmaker <paul.gortmaker@...driver.com>,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: ipv6:remove ipv6 global address after the interface is down

On Tue, Apr 01, 2014 at 05:30:31PM +0800, zhuyj wrote:
> Hi, Paul
> 
> With kernel 2.6.34.x, the following problem will appear.
> 
>  TargetA ------------------------- TargetB
> 3000::1/64 3000::2/64
> 
>  TargetA
>    - bring the interface down by doing an "ifconfig eth1 down"
>    - bring the interface back up by doing an "ifconfig eth1 up"
> 
> TargetB
>    - ping6 3000::1
>       ping6 succeeds the first time
>    - after bringing the interface on TargetA down and then back up, 
> ping6 to the interface fails.
> 
> With the latest mainline kernel(3.4+), this problem is resolved. When 
> eth1 is down, ipv6 address and route item are removed.
> But with kernel 2.6.34.x, when eth1 is down, ipv6 address remains while 
> route item is removed.
> 
> So when eth1 is up and assign the previous ipv6 address, with 2.6.34.x, 
> some errors will appear. But with latest mainline kernel, it can work well.
> 
> So I made a patch to fix this problem in kernel 2.6.34.x. Please merge 
> this to kernel2.6.34.x.

2.6.34 stable is EOL and won't get updated anymore. If this is problem is also
present in other, still maintained, stable kernel this would be possible.

Can you identify the upstream commit which repaired this problem and when it
got introduced?

Thanks,

  Hannes

--
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