<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">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 :</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class="">In the Mikrotik's RouterOS, there is a "next pool" directive that make possible to "chained" subnet to subnet and so on...<br class=""><br class="">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.<br class=""><br class="">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.</blockquote></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">regards,</div><div class=""><br class=""></div><div class=""><br class=""><div class="">
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Monaco; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><p style="margin: 0.0px 0.0px 0.0px 0.0px" class="">Dominic Germain</p><p style="margin: 0.0px 0.0px 0.0px 0.0px" class="">---------------------------------------------</p><p style="margin: 0.0px 0.0px 0.0px 0.0px" class="">Administrateur réseau / Network administrator</p><p style="margin: 0.0px 0.0px 0.0px 0.0px" class="">Sogetel</p><p style="margin: 0.0px 0.0px 0.0px 0.0px" class=""><a href="http://www.sogetel.net" class="">www.sogetel.net</a></p><div class=""><br class="khtml-block-placeholder"></div><div class=""><a href="mailto:mailinglists@sogetel.com" class="">mailinglists@sogetel.com</a></div><div class=""><br class="khtml-block-placeholder"></div><br class="Apple-interchange-newline"></span>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">Le 14 juin 2017 à 09:30, S. M. Hossein Hamidi <<a href="mailto:hossein.hamidi@gmail.com" class="">hossein.hamidi@gmail.com</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi,<div class=""><br class=""></div><div class="">See a few remarks below:</div><div class=""><br class=""></div><div class="">- 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.</div><div class=""><br class=""></div><div class="">- There is a use case which, I guess, lies in the category of 5 from there are managed Virtual Private Networks.</div><div class=""><br class=""></div><div class="">Regards,</div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, Jun 14, 2017 at 1:46 PM, Tomek Mrugalski <span dir="ltr" class=""><<a href="mailto:tomasz@isc.org" target="_blank" class="">tomasz@isc.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br class="">
<br class="">
One of the major parts of upcoming Kea 1.3 will be shared subnets, an<br class="">
ability of the DHCP server to handle multiple IP subnets in the same<br class="">
physical location.<br class="">
<br class="">
Similar to other new features, the process assumes we write down<br class="">
requirements first, discuss them and later come up with a design that<br class="">
fulfils them. So far, the requirements are ready for review:<br class="">
<br class="">
<a href="http://kea.isc.org/wiki/SharedSubnets" rel="noreferrer" target="_blank" class="">http://kea.isc.org/wiki/<wbr class="">SharedSubnets</a><br class="">
<br class="">
There's also a stub page for a design, but please ignore it for now.<br class="">
It's very early work in progress, not ready for broader discussion.<br class="">
<br class="">
Tomek<br class="">
______________________________<wbr class="">_________________<br class="">
kea-dev mailing list<br class="">
<a href="mailto:kea-dev@lists.isc.org" class="">kea-dev@lists.isc.org</a><br class="">
<a href="https://lists.isc.org/mailman/listinfo/kea-dev" rel="noreferrer" target="_blank" class="">https://lists.isc.org/mailman/<wbr class="">listinfo/kea-dev</a><br class="">
</blockquote></div><br class=""></div>
_______________________________________________<br class="">kea-dev mailing list<br class=""><a href="mailto:kea-dev@lists.isc.org" class="">kea-dev@lists.isc.org</a><br class="">https://lists.isc.org/mailman/listinfo/kea-dev</div></blockquote></div><br class=""></div></body></html>