zebra: supports to listen teamd nlmsg as bond type #14712
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this feature is to support teamd driver when configing ethernet segment's id and sys_mac via vtysh/zebra.
there are 2 approaches to support lacp protocol.
1st: linux bonding driver via tool (ifenslave_2.13~deb11u1_all.deb) via ip link cli command.
2nd: via teamd driver by nlmsg
https://github.com/jpirko/libteam/blob/master/libteam/libteam.c#L477
example for nlmsg from bonding driver:
https://cpp.hotexamples.com/examples/-/-/rtnl_link_add/cpp-rtnl_link_add-function-examples.html
comparison between bonding driver and teamd driver:
https://github.com/jpirko/libteam/wiki/Bonding-vs.-Team-features
hence, support teamd driver as what bonding driver does. we should add teamd nlmsg as bond type so that we are able to config associated es data.