From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Emmanuel Thierry <ml@sekil.fr>
Cc: Sharat Masetty <sharat04@gmail.com>, netdev@vger.kernel.org
Subject: Re: IPV6 routing problem
Date: Fri, 24 Jan 2014 14:59:32 +0100 [thread overview]
Message-ID: <20140124135932.GR7269@order.stressinduktion.org> (raw)
In-Reply-To: <CD36411A-7584-48B1-A406-E1584B3D32DD@sekil.fr>
On Fri, Jan 24, 2014 at 10:36:54AM +0100, Emmanuel Thierry wrote:
> Hello,
>
> Le 23 janv. 2014 à 08:15, Sharat Masetty a écrit :
>
> > Unfortunately toggling this config setting CONFIG_IPV6_ROUTER_PREF did
> > not help, I see the same problem in both cases.
> > The kernel version I am using is 3.10.0.
> >
> > Thanks for confirming that this is a non issue on 3.13 kernel version.
> > Would you happen to know which patch would have potentially fixed this
> > issue?
>
> Your problem looks like the following one :
> http://marc.info/?l=linux-netdev&m=137280268407054&w=2
>
> Which has been fixed in 3.10.4, and 3.11+
Yes, that could very well be the case. We resolve the gateway while
inserting the route (if not on-link), and it may not be available
because of missing probes or no traffic went to it, yet. Thanks for
looking after this, Emmanuel.
I really recommend using the stable kernels btw. instead of the vanialla
point zero releases.
Thanks,
Hannes
next prev parent reply other threads:[~2014-01-24 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 1:41 IPV6 routing problem Sharat Masetty
2014-01-22 7:07 ` Hannes Frederic Sowa
2014-01-22 7:11 ` Hannes Frederic Sowa
2014-01-23 7:15 ` Sharat Masetty
2014-01-24 9:36 ` Emmanuel Thierry
2014-01-24 13:59 ` Hannes Frederic Sowa [this message]
2014-01-24 18:50 ` Sharat Masetty
2014-01-24 20:05 ` Cong Wang
2014-01-26 13:57 ` Rami Rosen
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=20140124135932.GR7269@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=ml@sekil.fr \
--cc=netdev@vger.kernel.org \
--cc=sharat04@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).