From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicola Padovano Subject: Re: problem with flowi structure Date: Fri, 17 Sep 2010 19:05:14 +0200 Message-ID: References: <1284650768.3352.37.camel@edumazet-laptop> <1284652453.3352.38.camel@edumazet-laptop> <1284714533.3391.53.camel@edumazet-laptop> <1284741295.3391.100.camel@edumazet-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: AIJAZ BAIG , netfilter-devel , netdev@vger.kernel.org To: Eric Dumazet Return-path: Received: from mail-wy0-f174.google.com ([74.125.82.174]:62290 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752314Ab0IQRFg convert rfc822-to-8bit (ORCPT ); Fri, 17 Sep 2010 13:05:36 -0400 In-Reply-To: <1284741295.3391.100.camel@edumazet-laptop> Sender: netfilter-devel-owner@vger.kernel.org List-ID: ok man :) the last question is about fl.nl_u.ip4_u.saddr =3D 0... is it a kind of "jolly" selector of the source address? i.e. if we have a simplified cache route SOURCE IP DEST IP NEXT HOP ips1 google nexthop1 ips2 google nexthop2 with =2E..saddr =3D 0 =2E...daddr =3D google =2E...tos =3D.... i get nexthop1 or nexthop2. right? On Fri, Sep 17, 2010 at 6:34 PM, Eric Dumazet = wrote: > Le vendredi 17 septembre 2010 =E0 18:27 +0200, Nicola Padovano a =E9c= rit : >> > 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 r= outing 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 > > > > --=20 Nicola Padovano e-mail: nicola.padovano@gmail.com web: http://npadovano.altervista.org -- To unsubscribe from this list: send the line "unsubscribe netfilter-dev= el" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html