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

Documentation on how to add communities #19

Open
funzoneq opened this issue Apr 17, 2024 · 1 comment
Open

Documentation on how to add communities #19

funzoneq opened this issue Apr 17, 2024 · 1 comment

Comments

@funzoneq
Copy link

Hi,

In your DENOG presentation and on the demo, you use nice names for BGP communities. I can't find anywhere in the documentation on how to accomplish this. Can you share some details on how configure this?

Thanks!

@vista-
Copy link

vista- commented Apr 17, 2024

By default, the NLNOG RING communities (https://github.com/NLNOG/lg.ring.nlnog.net/tree/main/communities) get automatically embedded in the released binaries like so:
https://github.com/wobcom/fernglas/blob/main/src/api.rs#L27

During build time, the directory containing the NLNOG RING community files get fed into a Python script (https://github.com/wobcom/fernglas/blob/main/contrib/print_communities.py), which outputs the communities.json in the dictionary format that Fernglas expects.

The configuration option communities_file under the api configuration can be used to override this behaviour, and you can point Fernglas to your own communities.json instead.

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

2 participants