[kea-dev] shared-network solution idea

[mailinglists at sogetel.net]

Hi,

Regarding the shared-network thread that involve Tomek Mrugalski...

https://lists.isc.org/mailman/htdig/kea-users/2016-December/000709.html

I would like to add a "me too".  Laking that feature is also a show stopper for us.  We also have large networks with multiple subnets that couldn't managed by simply enlarging mask.

That beeing said, I fully understand that implementing some kind of "grouping" is complicated and not in the actual roadmap.

That's why I would like to suggest something...

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



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