iproute2: ip-monitor: Properly track interface names

ip-monitor does not currently update interface names for tracked ids,
even if they change on the system. This causes route messages to print
with the wrong interface name, making them indistinguishable from each
other on dynamic interfaces that all start as `eth0` on the system.

We need this to support USB connectivity on SmartNICs that use a USB
NCSI path.

Tested: Booted a machine with USB interfaces that rename to verify that the names are properly tracked now. Old images have a 100% reproduction rate of this issue.

Fusion-Link: https://fusion2.corp.google.com/7d1a7a23-0878-3d5c-a126-82ef2bd7ce8e (platform11)
Fusion-Link: https://fusion2.corp.google.com/fcdb0235-156e-3088-8f26-c02891f10d59 (platform11-emr)
Fusion-Link: https://fusion2.corp.google.com/01dec9b3-ebb3-3316-ad1a-d7da08a96494 (platform15)
Fusion-Link: https://fusion2.corp.google.com/d0617ef2-6d9f-3446-b173-7027a63cef6a (platform17)
Fusion-Link: https://fusion2.corp.google.com/f1cd0acd-bb90-3654-a3cb-c1a9e3b24c28 (platform5)

Google-Bug-Id: 428743767
Change-Id: If6b0864dfc2bf0107e34ddaa541ad34f16ab8abc
Signed-off-by: William A. Kennington III <wak@google.com>
3 files changed
tree: 5a18cae97f29578662dbc8715a2cf0ffa1143040
  1. classes/
  2. conf/
  3. dynamic-layers/
  4. recipes-bsp/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-google/
  10. recipes-kernel/
  11. recipes-phosphor/
  12. recipes-support/
  13. recipes-tpm1/
  14. recipes-tpm2/
  15. LICENSE
  16. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.