Hi Federico, I should mention that I have seen https://github.com/openwisp/django-ipam, https://github.com/openwisp/openwisp-ipam, and this post -> https://groups.google.com/forum/#!topic/openwisp/_TIF0bD8NYA ; you know what I am trying to accomplish- make it so a 10-year old can set this up- so, this isn't ultimately helpful. I saw your expo Twitter post, and pulled the PDF, it is very cool, and based on the request therein I am willing to join forces with you; we have a couple of people working on this stuff. But I need to turn this into something usable for everyone, and if you want to help me coordinate the spec to do this *easily*, I am happy to get it programmed.
Thank you again, Stuart On Friday, November 9, 2018 at 8:42:07 AM UTC+5:30, Stuart Trusty wrote: > > Greetings all, > > When we set up a template for something like an 802.11s node, the way I > see this is that we must fixate it with a single IP like 192.168.1.1, but > this isn't conducive to 802.11s, as each router needs 192.168.1.2, .3, etc. > for it to function properly. > > However, the unit can't get on the MAC mesh without knowing its IP in the > first place, so using dhcpd in this scenario is a puzzle to me. > > Is anyone using some dynamic or incremental feature in a template to > assign IP's on a group of routers, or I am I thinking about going about > this in the wrong way? Clearly Google Wifi has solved this issue, what is > the best approach here? > > Thank you in advance, > Stuart > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
