-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
On Docker, zebra crashed when interface state moved from up->down->up #13523
Comments
Same here. link_ifp is NULL (gdb) p link_ifp |
This issue is stale because it has been open 180 days with no activity. Comment or remove the |
This issue will be automatically closed in the specified period unless there is further activity. |
The problem seems to be that whenever there's a link down/up change in an interface which is a macvlan, where the parent interface isn't visible in the network namespace the zebra process is running, the zebra_if_update_link call will leave zif->link as null, which will then crash in if_up->zebra_vxlan_macvlan_up as that assumes the link pointer is non-null. |
Fixing in #15010 |
While running FRR on Docker, zebra crashed when interface state moved from up->down->up
Topology:
Peer Device -------------17.0.0.0/8------------------- FRR on Docker (with macvlan mode)
Crash log
Configuration :
Describe the bug
To Reproduce
Once BGP neighbor-ship is established bring down interface of peer device by issuing "shutdown" and then "no shutdown"
Expected behavior
BGP should re-establish the neighbor ship and zebra should not crash
Versions
FRR Version: FRRouting 8.5.1 (81ce0b40637c)
Docker : 20.10.5+dfsg1
The text was updated successfully, but these errors were encountered: