-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add support for reading routing operational data for IPv4 #217
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall it looks great. I left some minor commends, mostly cosmetic. I good idea might be to run your diff though checkpatch.pl
from the kernel.
Again, looks really good overall.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with @rical's findings.
Additionally, I think I'd like to see the metric column earlier, before protocol/origin.
In the CLI: admin@infix-00-00-00:/> show routes PREFIX DESTINATION PROTOCOL METRIC 1.1.1.0/24 e0 kernel 192.168.100.0/24 1.1.1.1 static 20 192.168.110.2/32 blackhole static 20 192.168.120.2/32 blackhole static 20 192.168.130.2/32 unreachable static 20
e010697
to
6055009
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Looking forward to an update in doc/networking.md, example of how to add a route and read routing table remotely using NETCONF ;-)
Should be 2023 not 2013.
16736df
to
45650b5
Compare
In the CLI:
admin@infix-00-00-00:/> show routes
EDIT by @rical : framed output in markdown ```