netdev - Re: [PATCH 1/2] ipv4/ipv6: Prepare for new route gateway semantics.

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] [day] [month] [year] [list]

Message-Id: <20120127.163400.1656316431173173490.davem@davemloft.net>
Date:	Fri, 27 Jan 2012 16:34:00 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	bcook@...akingpoint.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 1/2] ipv4/ipv6: Prepare for new route gateway semantics.

From: Brent Cook <bcook@...akingpoint.com>
Date: Fri, 27 Jan 2012 12:59:51 -0600

> On Thursday, January 26, 2012 02:55:44 PM David Miller wrote:
>> In the future the ipv4/ipv6 route gateway will take on two types
>> of values:
>> 
>> 1) INADDR_ANY/IN6ADDR_ANY, for local network routes, and in this case
>>    the neighbour must be obtained using the destination address in
>>    ipv4/ipv6 header as the lookup key.
>> 
>> 2) Everything else, the actual nexthop route address.
>> 
>> So if the gateway is not inaddr-any we use it, otherwise we must use
>> the packet's destination address.
> 
> Under what cases would this be expected to help keep the # of lookup keys at a 
> minimum?

The point is to accomodate the future wherein a single route might cover
an entire subnet's worth of destinations.

I am going to remove the routing cache, and route lookups will use the
routing table entries directly.

In order to accomodate that two thing have to happen:

1) Neighbour entires cannot be referred to by the routes, they must be
   looked up as-needed.  This is because a neighbour refers to a specific
   single nexthop, whereas routes in the future will refer potentially
   to many nexthops.

2) Routes must also not refer directly to inetpeer entries, this is also
   because routes will refer to potentially several destinations whereas
   inetpeer entries only apply to specific destinations.

--
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