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]

Date:	Fri, 17 Sep 2010 19:05:14 +0200
From:	Nicola Padovano <nicola.padovano@...il.com>
To:	Eric Dumazet <eric.dumazet@...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

ok man :)
the last question is about  fl.nl_u.ip4_u.saddr = 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
...saddr = 0
....daddr = google
....tos =....
i get nexthop1 or nexthop2. right?


On Fri, Sep 17, 2010 at 6:34 PM, Eric Dumazet <eric.dumazet@...il.com> wrote:
> 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
>
>
>
>



-- 
Nicola Padovano
e-mail: nicola.padovano@...il.com
web: http://npadovano.altervista.org
--
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