netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ashwanth@codeaurora.org
To: netdev@vger.kernel.org
Cc: "eric.dumazet@gmail.com" <roszenrami@gmail.com>
Subject: Uncreachable default lo route in table 0
Date: Thu, 28 Jul 2016 13:31:46 +0530	[thread overview]
Message-ID: <1c8b25ef7ed1c8a79a5ad932e802ea65@codeaurora.org> (raw)


On an Android device(using 3.18 kernel version) we see multiple entries 
as the following added to the route table 0(unspec) by kernel. We 
noticed that this typically happens when we toggle WIFI repeatedly. The 
problem we see is that under such stress test, the table 0 gets filled 
with these entries(4096) and after that no further routes can get added 
leading to unstability.

unreachable default dev lo table 0 proto kernel metric 4294967295 error 
-101

Can you please let us know why does this route get added for lo device 
and when is this supposed to be flushed out?

             reply	other threads:[~2016-07-28  8:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28  8:01 ashwanth [this message]
2016-08-10 11:45 ` Uncreachable default lo route in table 0 ashwanth

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=1c8b25ef7ed1c8a79a5ad932e802ea65@codeaurora.org \
    --to=ashwanth@codeaurora.org \
    --cc=netdev@vger.kernel.org \
    --cc=roszenrami@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).