netdev - Re: problem with flowi structure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1284741295.3391.100.camel@edumazet-laptop>
Date:	Fri, 17 Sep 2010 18:34:55 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Nicola Padovano <nicola.padovano@...il.com>
Cc:	AIJAZ BAIG <aijazbaig1@...il.com>,
	netfilter-devel <netfilter-devel@...r.kernel.org>,
	netdev@...r.kernel.org
Subject: Re: problem with flowi structure

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 netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html