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: <54D424BD.2090402@gmail.com>
Date:	Thu, 05 Feb 2015 19:19:41 -0700
From:	David Ahern <dsahern@...il.com>
To:	roopa <roopa@...ulusnetworks.com>
CC:	netdev@...r.kernel.org, ebiederm@...ssion.com,
	Dinesh Dutt <ddutt@...ulusnetworks.com>,
	Vipin Kumar <vipin@...ulusnetworks.com>,
	Nicolas Dichtel <nicolas.dichtel@...nd.com>,
	hannes@...essinduktion.org
Subject: Re: [RFC PATCH 00/29] net: VRF support

On 2/5/15 4:12 PM, roopa wrote:
> Wondering if you have thought about some of the the below cases in your
> approach to vrfs ?.
> - Leaking routes from one vrf to another

Can you give me an example of what you mean by this?

> - route lookup in one vrf on failure to fallback to the global vrf (This
> for example can be done using throw if we used ip rules and route tables
> to do the same).
> - A route in one vrf pointing to a nexthop in another vrf

I have been more focused on the initial VRF infrastructure and have not 
spent too much time on these use cases or other route lookup features 
(e.g., allow an application to handle route lookup misses similar to arp 
misses, allow custom route lookup modules) that are needed to approach 
the feature richness provided by high end routers.

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

Powered by blists - more mailing lists