-
Notifications
You must be signed in to change notification settings - Fork 557
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
Set next hop to something valid for vxlan routes #1347
Set next hop to something valid for vxlan routes #1347
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.
Looks good @malanovo, I think your changes make sense. Would you also be able to add a test case for this? Thanks.
Sure, I can work on that. I've got several devices I can pull from for an example. |
Test case has been added. Please note that the test case relies on the fix for issue #1069 having been applied (which was just recently merged into the |
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.
Looks good to me. Thanks @malanovo!
This is a small change that stops Napalm from bombing out on EOS when attempting a get_route_to() on a VXLAN route, and inserts some values that make it useful. The next hop is set to the IP of the destination VTEP, and the exit interface is set to vxlan1. Granted we're assuming the interface name will be vxlan1, but at the moment, that's all it can be on EOS. It might need alteration in the future if Arista changes that.