Implement multi domains #102
Description
Why
- reduce onboarding time
- don't require long list of vpn endpoints
- make it possible to administrate by geolocation
- use common gluon domain features
- further increase scalability of FFAC domains
How
We could use something like:
https://github.com/freifunkh/ffh-packages/blob/master/gluon-segment-mover/
which also has a backend like this one:
https://github.com/ff3l/ff3l-api
(though the signature features is missing here I think)
This was temporarily used in freifunkh, as it adds traffic by requesting the API every 5 minutes.
One could add a trigger to nodes, so that they only request their api if the node was reached.
Related communities approaches
- FFMUC has separate domains which are decided by the user - separate domains do not mesh together (neither through VXLAN, nor through Wifi-mesh)
- FFS resolves the DNS to different ip addresses, depending on the requesting node - which is also cumbersome
- FFH used to use the gluon-segment-mover, but does not anymore, has normal domains instead
- FFNW uses the hoodselector