From: zhuyj <zyjzyj2000@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: zhuyj <zyjzyj2000@gmail.com>
Subject: ipv6 global address remains while route item disappears after this interface is restared in 2.6.34.x
Date: Mon, 26 Aug 2013 10:28:03 +0800 [thread overview]
Message-ID: <521ABD33.7070905@gmail.com> (raw)
With two directly connected targets running kernel 2.6.34.x.
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.
The root cause is:
IPv6 address 3000::1/64 remains while the ipv6 route on eth1 disappears.
Thus on TargetB, running "ping6 3000::1" can not succeed.
Compared with 3.4.x, ipv6 address and ipv6 route item are removed when
an interface is restarted in the.
Best Regards!
zhuyj
next reply other threads:[~2013-08-26 2:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 2:28 zhuyj [this message]
2013-08-26 2:43 ` [PATCH 1/1] ipv6:remove ipv6 global address after the interface is down zhuyj
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=521ABD33.7070905@gmail.com \
--to=zyjzyj2000@gmail.com \
--cc=linux-kernel@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