From: David Miller <davem@davemloft.net>
To: ratheesh.ksz@gmail.com
Cc: user-mode-linux-user@lists.sourceforge.net,
user-mode-linux-devel@lists.sourceforge.net,
netdev@vger.kernel.org
Subject: Re: routing table error in 2.6.39 ..
Date: Thu, 22 Sep 2011 14:21:10 -0400 (EDT) [thread overview]
Message-ID: <20110922.142110.1470776655731016807.davem@davemloft.net> (raw)
In-Reply-To: <CAGZFCEHtyE1MutMmhKefFm9Xx5rri1j7DR7L=cFU3KUg7ejs4g@mail.gmail.com>
From: ratheesh kannoth <ratheesh.ksz@gmail.com>
Date: Thu, 22 Sep 2011 21:25:47 +0530
> in 2.6.38 routing table is correct. But in 2.6.39 default gw appears
> on top of the routing table. same problem persist in 3.0.0 also.
You cannot depend upon the order in which routing table entries
are listed by the kernel.
The table internally is correct, and lookups will match using the
proper longest-matching-prefix algorithm.
prev parent reply other threads:[~2011-09-22 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 15:55 routing table error in 2.6.39 ratheesh kannoth
2011-09-22 18:21 ` David Miller [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=20110922.142110.1470776655731016807.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ratheesh.ksz@gmail.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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).