Re: [linux-vrf-core] First code release
Status: Beta
Brought to you by:
jleu
From: James R. L. <jl...@mi...> - 2002-03-06 21:35:59
|
On Wed, Mar 06, 2002 at 04:16:43PM -0500, Nick Eggleston wrote: > Jim, > > Could you take a few minutes and type up a note that describes from a > system level the way you have implemented this? How are you > conceptualizing the kernel mods to support the vrfs? The base change of this implementation is make the fib_table array a double index array. Prior to this it was only indexed by the table id. I added a vrf id. So everywhere that create/gets/modifies a table had to have an extra piece of info added to the call. The other change to the 'fib' is that the fib_rules are now index by vrf as well. fib_rules are the structuire behind maintaining the order in which tables do route lookups. (ie the local table alway is looked up before the main table, whicb is before the default table). By allowing VRFs to have rules, policy routing and teh like still work within a VRF (I think NAT will work as well!). The next large change is how the tcp/udp/raw sockets account for used port numbers. Every where a lookup or a comparison is made I add the vrf to the mix. The other place where VRF show s up, the route cache, route messages, link messages, rules messages, socket hash tables, skbs. This is a very quick overview. I will try to come up with a better one and add it to the README. Maybe some of the questions you guys come back with will hlep form this description. Jim > Thanks! > > Nick > > On Wed, 6 Mar 2002, James R. Leu wrote: > > > Hey guys, > > > > I know its been a LONG time since we talked about this, but I have been > > thinking about it, and I've done some work. I placed my first crack at a > > VRF implementation for the kernel. Take a look at the README inside it > > then post questions :-) > > > > Jim > > > -- James R. Leu |