[kea-dev] Shared subnet requirements

mailinglists at sogetel.net mailinglists at sogetel.net
Wed Jun 14 14:40:09 UTC 2017


Hi,

Back in February 2017, I did a suggestion to address this issue.  At that time, "shared subnet" wasn't a hot topic... I kindly repost my suggestion :

> In the Mikrotik's RouterOS, there is a "next pool" directive that make possible to "chained" subnet to subnet and so on...
> 
> Why not using the same kind of concept?  If a subnet is exhausted, it will look at the new "next-subnet" option, look at it, pick and IP (if available), if not, look for an other next "next-subnet" option and so on...  That way, you don't have to implement some form of grouping.
> 
> Obviously each subnet in a chain have their gateway's IP configured on the router physical interface (as we already do).  The IP of the first subnet in the chain must be configure as the "primary" IP on the router interface since DHCP we request will come from that IP...  Not a big deal.



regards,


Dominic Germain
---------------------------------------------
Administrateur réseau / Network administrator
Sogetel
www.sogetel.net

mailinglists at sogetel.com



> Le 14 juin 2017 à 09:30, S. M. Hossein Hamidi <hossein.hamidi at gmail.com> a écrit :
> 
> Hi,
> 
> See a few remarks below:
> 
> - I don't relate to the term "shared subnet" while considering the definition. My impression from the term "shared subnet" is a subnet which is shared between more than a single tenant. However, it seems here it is more about a shared physical link to DHCP server.
> 
> - There is a use case which, I guess, lies in the category of 5 from there are managed Virtual Private Networks.
> 
> Regards,
> 
> 
> On Wed, Jun 14, 2017 at 1:46 PM, Tomek Mrugalski <tomasz at isc.org <mailto:tomasz at isc.org>> wrote:
> Hi,
> 
> One of the major parts of upcoming Kea 1.3 will be shared subnets, an
> ability of the DHCP server to handle multiple IP subnets in the same
> physical location.
> 
> Similar to other new features, the process assumes we write down
> requirements first, discuss them and later come up with a design that
> fulfils them. So far, the requirements are ready for review:
> 
> http://kea.isc.org/wiki/SharedSubnets <http://kea.isc.org/wiki/SharedSubnets>
> 
> There's also a stub page for a design, but please ignore it for now.
> It's very early work in progress, not ready for broader discussion.
> 
> Tomek
> _______________________________________________
> kea-dev mailing list
> kea-dev at lists.isc.org <mailto:kea-dev at lists.isc.org>
> https://lists.isc.org/mailman/listinfo/kea-dev <https://lists.isc.org/mailman/listinfo/kea-dev>
> 
> _______________________________________________
> kea-dev mailing list
> kea-dev at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-dev/attachments/20170614/ea907032/attachment.html>


More information about the kea-dev mailing list