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

rename gateway_nexthop fields in statistics #170

Open
christf opened this issue Nov 12, 2019 · 2 comments
Open

rename gateway_nexthop fields in statistics #170

christf opened this issue Nov 12, 2019 · 2 comments
Labels

Comments

@christf
Copy link

christf commented Nov 12, 2019

gateway_src and gateway_nexthop are very specific terms and they sit flat in statistics.
There are network topologies that cannot be covered by this structure. Especially when there is src-specific routing in place. Instead of gateway_nexthop I propose the following structure:

gateway: [
{
    "src": "aaa:bbb:ccc:ddd:eee:111:2222:333/64"
    "via": "aaa:bbb:ccc:ddd:eee:111:2222:333/64"
    ("dest": "aaa:bbb:ccc:ddd:eee:111:2222:333/64")
}
]

The terminology "src" and "via" means the structure is re-usable between different mesh protocols.
Optionally we could include a "dest" field as well, however at the moment I guess only 2000::/3 is relevant.

@genofire
Copy link
Member

i will implement it, if it is in the master-branch on https://github.com/freifunk-gluon/gluon

@genofire
Copy link
Member

is there any update on this, or could we close the yanic issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants