From: Eric Dumazet <eric.dumazet@gmail.com>
To: Nicola Padovano <nicola.padovano@gmail.com>
Cc: AIJAZ BAIG <aijazbaig1@gmail.com>,
netfilter-devel <netfilter-devel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: problem with flowi structure
Date: Fri, 17 Sep 2010 18:34:55 +0200 [thread overview]
Message-ID: <1284741295.3391.100.camel@edumazet-laptop> (raw)
In-Reply-To: <AANLkTi=r__RA=5UfNnhsKizDF6OFVYXcSe9KOPx1zW0u@mail.gmail.com>
Le vendredi 17 septembre 2010 à 18:27 +0200, Nicola Padovano a écrit :
> > With different keys (src addr, tos, fwmark, ...) we can have a lot of
> > different routes for apparently same destination
> and why this reasoning it isn't present on the routing table?
> I mean: there will be a reason for which this isn't present in the routing table
>
>
It is present, of course, since route cache can be flushed (or
bypassed), you need to be able to rebuild it from a stable reference.
ip rule ls
ip ro list table xxx
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-09-17 16:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 15:14 problem with flowi structure Nicola Padovano
2010-09-16 15:26 ` Eric Dumazet
2010-09-16 15:30 ` Nicola Padovano
2010-09-16 15:54 ` Eric Dumazet
2010-09-16 19:25 ` Nicola Padovano
2010-09-17 5:40 ` AIJAZ BAIG
2010-09-17 8:46 ` Nicola Padovano
2010-09-17 9:08 ` Eric Dumazet
2010-09-17 9:53 ` Nicola Padovano
2010-09-17 16:27 ` Nicola Padovano
2010-09-17 16:34 ` Eric Dumazet [this message]
2010-09-17 17:05 ` Nicola Padovano
2010-09-17 17:51 ` Eric Dumazet
2010-09-17 18:01 ` Nicola Padovano
2010-09-17 18:07 ` Eric Dumazet
2010-09-17 18:25 ` Nicola Padovano
2010-10-01 23:46 ` Jan Engelhardt
2010-10-02 8:08 ` Nicola Padovano
2010-10-02 20:18 ` David Miller
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=1284741295.3391.100.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=aijazbaig1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=nicola.padovano@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