3 ms·

I really wish developers of OSS systems like this would design them, from the ground up, for multiple access points. None of the required changes are rocket sc

by amluto 3y ago

I really wish developers of OSS systems like this would design them, from the ground up, for multiple access points. None of the required changes are rocket science, but IMO all of the features should be pleasant to use with more than one AP, and the network architecture should support it. OpenWRT, for example, handles fast roaming in a way that is IMO quite miserable to configure. (It would be really nice if the actual 802.11 standards specified a way for an AP to delegate management to a separate device so that any vendor’s AP could join such a network. Oh well.)

spr-alex 3y ago
Would love to hear from you if you'd be interested in chatting you can find us on the discord or outreach [at] supernetworks.org. I assume your comment is about SPR's micro-segmentation and not the blog post if I understand? SPR does support mesh nodes with backhaul which is currently for PLUS members -- however, we have not explored supporting multiple independent routers with micro-segmentation. Would love to hear your use case, we have an API which should already make it possible for users to automate and code up what they need to sync up disparate SPR instances on distinct routers, for example. For affecting the 802.11 spec that's out of scope for our reach today.