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

[FEATURE] Allow combination of separate domain codes for a multi domain setup #56

Closed
herbetom opened this issue Feb 27, 2020 · 3 comments · Fixed by #59
Closed

[FEATURE] Allow combination of separate domain codes for a multi domain setup #56

herbetom opened this issue Feb 27, 2020 · 3 comments · Fixed by #59

Comments

@herbetom
Copy link
Contributor

Currently there is no way to use the new -n <domain code> option (thanks for implementing that) in a multi domain setup. Unless you start for every domain a seperate instance of mesh-announce.

In the example for a multi-domain setup:
respondd.py -d /opt/mesh-announce/providers -i meshvpn-one -i br-one -i bat-one -b bat-one -i meshvpn-two -i br-two -i bat-two -b bat-two -i meshvpn-three -i br-three -i bat-three -b bat-three
it seems to be suggested not to run multiple instances of mesh-announce for multi domain.

I don't know which would be the best way to include this information, but somehow you should be able to do this.

This also extends to other options, but -n seems to me like something esential for multi domain.

@AiyionPrime
Copy link
Contributor

ffh has the same interest. What do you thin about an option e.g. called "-df" for domain file, which would specify the path to a json file containing a dictionary with keys called like bat interfaces and values called like the matching domainname?

@herbetom
Copy link
Contributor Author

herbetom commented Apr 4, 2020

For me that sounds like an interesting idea.

@AiyionPrime
Copy link
Contributor

I just forgot to hit the comment button two hours ago.
The PR is incoming. :)

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

Successfully merging a pull request may close this issue.

2 participants