From: Roman Mamedov <rm@romanrm.ru>
To: <netdev@vger.kernel.org>
Subject: Re: Problem with IPv6 Route Cache
Date: Fri, 11 Jan 2013 22:37:55 +0600 [thread overview]
Message-ID: <20130111223755.714ddf7f@natsu> (raw)
In-Reply-To: <20130111185126.56cababe@natsu>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
Hello,
I have discovered that when the problem is occuring, I have:
root@neru:~# ip -6 neigh
fd39:20::39 dev tun-rm FAILED
fe80::20b:45ff:fe80:c000 dev eth0 lladdr 00:0b:45:80:c0:00 router REACHABLE
2a02:e00:ffff:56::1 dev eth0 lladdr 00:0b:45:80:c0:00 router REACHABLE
Launching "ping6 fd39:20::39" turns fd39:20::39 from FAILED to REACHABLE.
After that, "ip -6 route flush cache" actually succeeds in removing the route
via default gateway, and I then get the proper route entry:
root@neru:~# ip -6 route get fd39::100
fd39::100 from :: via fd39:20::39 dev tun-rm src fd39:20::3 metric 0
cache
So I conclude that my issue is very similar to [1] mentioned in a Bugzilla
entry [2] linked here just today.
[1] https://lkml.org/lkml/2012/5/25/96
[2] https://bugzilla.kernel.org/show_bug.cgi?id=42991
--
With respect,
Roman
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-01-11 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 12:51 Problem with IPv6 Route Cache Roman Mamedov
2013-01-11 12:58 ` Roman Mamedov
2013-01-11 15:06 ` Hannes Frederic Sowa
2013-01-11 16:37 ` Roman Mamedov [this message]
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=20130111223755.714ddf7f@natsu \
--to=rm@romanrm.ru \
--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 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).