Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement multi domains #102

Open
maurerle opened this issue May 14, 2024 · 0 comments
Open

Implement multi domains #102

maurerle opened this issue May 14, 2024 · 0 comments

Comments

@maurerle
Copy link
Member

maurerle commented May 14, 2024

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant