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

Discovery though open port on Mikrotik gateway #16

Open
3 tasks
abitrolly opened this issue May 27, 2020 · 1 comment
Open
3 tasks

Discovery though open port on Mikrotik gateway #16

abitrolly opened this issue May 27, 2020 · 1 comment

Comments

@abitrolly
Copy link
Member

abitrolly commented May 27, 2020

An alternative to #15 for hackerspace service discovery is make Mikrotik gateway expose its IP mapping to internal and internal ports.

The benefit is that if we've got two physical spaces with two external gateways, we could get services from each of them separately.. The gateway can also ping them and collect uptime stats. The only problem is to find out how to run a process in Mikrotik that can:

  • survive reboots
  • run a responding service on internal and external port
  • read current IP mapping

Other idea for service discovery through dedicated ports besides #15 is rethinking portmapper from the previous era.

@abitrolly
Copy link
Member Author

Mikrotik has its own discovery protocol. Looks pretty rad. Might reuse that.

https://wiki.mikrotik.com/wiki/Manual:IP/Neighbor_discovery

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