-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
staticd: Handle static routes appropriately #16684
base: master
Are you sure you want to change the base?
staticd: Handle static routes appropriately #16684
Conversation
b57adc6
to
abb1a4d
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.
Please format the commit as per workflow.rst specifies. Additionally put the description of what is going on in the commit message. Finally we do not use c++ style comments either, please fix that.
Signed-off-by: DennyAgussy <[email protected]>
abb1a4d
to
0daba99
Compare
Possible to reproduce this with a topotest? |
Hi @ton31337 The topotests which are failing in the master branch are also being failed in the fix we had done. Apart from that rest of the tests were success. Test cases failed:
Master branch commit(9a009e1) Thanks |
zebra not restore routes when have more then one iface with common network and one iface is flaping (up, then get IP) #16110
Introduction:
As per the bug when setting up a route via dum2 and assuming it will be restored after the interface is restored. There is a weird behavior. Good behavior "get addr + up" then the route is activated as expected. But when "up + get addr" the route is inactive, though the interface is up and the connected route is added.
Implementation details:
We have added a check whether the interface is up or not and triggering the function which potentially leads to route walk.
Hope this implementation is a good an approach, if not let's know the alternative one, so that we can work on it.
Thanks
Denny Agussy