-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[frr]: Move to version 7.2 #3704
Conversation
@tylerlinp I've removed 0005-Support-VRF.patch from the patchset. I see that sonic-net/sonic-frr#15 you asked for RT_TABLE_COMPAT instead of RT_TABLE_UNSPEC from frr team. You referred to fpmsyncd compatibility. Is it still valid? Should I add an extrapatch for frr 7.2? |
@pavel-shirshov It doesn't matter RT_TABLE_UNSPEC or RT_TABLE_COMPAT, it would be ignored, so there is no need to change it again. Yes, a new patch is needed in frr 7.2 to revert the table_id to vrf_id. Now fpmsyncd codes are basing on vrf_id. This is the part to revert:
|
@tylerlinp Thank you for your prompt reply. |
retest vs please |
there are a few patches removed? can you explain why? because they are included in the frr 7.2? |
Yes. All removed patches are parts of FRR 7.2 now. |
@tylerlinp , can you follow up on Pavel's question? |
In my oponion using vrf_id is better. If to use table_id, it will get much more work and loss of efficiency. It is a subject deserved to discuss. |
* Use 7.2 tree to generate frr packages * Adapt patches for frr/7.2 * Use vrf_id
- What I did
Moved to frr 7.2
- How I did it
Changed frr sources and adapted patches
- How to verify it
Build an image and run it on your dut
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)