Hi Tomek, I have no requirements for VRF support currently.
I was just curious if that is the "multi-tenancy" being referenced... I realize this is a rather generic term, and can be used to refer to anything that creates separation in the forwarding plane. Thanks for the explanation, Jason On Thu, Mar 8, 2018 at 3:22 AM, Tomek Mrugalski <[email protected]> wrote: > On 07/03/2018 15:47, Jason Guy wrote: > > Hi Tomek, > > > > Are you referring to VRF support when you say Multi-Tenancy? > No. Long time ago one company approached us asking about support for > many hotspots, each using the same overlapping address space. Kea would > see the packets coming from different relays. The company disappeared > soon afterwards and nothing came out of it. > > Since Rob asked it, I though it may be a good time to do a quick > experiment. That's it. Just wanted to make it clear there's no secret > plan to develop anything in that area. > > > In the latest Linux kernel (4.9+), the full VRF infrastructure is > > working well, but I don't think a lot of classic services have added > > support. It would be awesome to assign a subnet to a linux VRF. > I don't know anything about vrf, except quick look at this: > https://andir.github.io/posts/linux-ip-vrf/ > > If you want to have overlapping address spaces, comments from my earlier > mail apply. If you want Kea to just be able to provide addresses over > VRF interface that are globally unique, we can explore this a bit > further. How should Kea open sockets here - one for each vrf interface > (10 customers = 10 sockets)? > > We already have a knob for setting outbound interface (search for > outbound-interface here > https://jenkins.isc.org/job/Kea_doc/guide/kea-guide.html). There are > some improvements coming in that area soon (http://kea.isc.org/ticket/5515 > ). > > Tomek >
_______________________________________________ Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
