There are special interface features or statistics available that can only be retrived via netlink messages.
We do not have a netlink wrapper as of now, but one interesting setting would be: IFLA_BOND_AD_LACP_BYPASS which would be the equivalent to "channel 20 mode active" in a Cisco Port-Channel
Design a Python helper to talk Netlink
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | FEATURE REQUEST | None | T5718 Add netlink wrapper to talk to the Kernel | ||
| Resolved | FEATURE REQUEST | HollyGurza | T6641 Show command for interface messages | ||
| Duplicate | None | T3876 Replace vyos-netplug with a VyOS link state monitor service |
With T6641 implemented and a discussion with @jestabro and @dmbaturin this would be a perfect addition.
The idea is to use said daemon and extend its functionality to receive messages (preferrably RabbitMQ), decode them, and call an interface to the Linux Kernel. Messages could be send from e.g. https://github.com/vyos/vyos-1x/blob/current/python/vyos/ifconfig/bond.py.
The second part would be gathering intel form the Kernel itself in op-mode. So we would need a small client (Python library function to be re-usable) to ask the Kernel about specific information - like interface counters or when was the last link up/down event.