-
Notifications
You must be signed in to change notification settings - Fork 40
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
Labels
Comments
i will implement it, if it is in the |
7 tasks
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
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:
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.
The text was updated successfully, but these errors were encountered: