There is always a matching iproute2 package to the Kernel.
Right now we still run iproute2 4.14 but with a 4.19 series Kernel. This should be fixed to also get all the latest features of 4.19.
There is always a matching iproute2 package to the Kernel.
Right now we still run iproute2 4.14 but with a 4.19 series Kernel. This should be fixed to also get all the latest features of 4.19.
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | FEATURE REQUEST | c-po | T1404 Update iproute2 package to 4.19 | ||
Wontfix | FEATURE REQUEST | c-po | T1409 Verify if vyatta-iproute package can be replaced by upstream iproute2 package |
Remaining question is: Why do we need our own iproute fork and can't use the upstream packages commit https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=f900a21611c03e6d83104f2a862cd4c5f160d35f for VyOS? Thats the commit we build right now in https://github.com/vyos/vyatta-iproute
I remember seeing some commits which we used for interface statistics which I have not seen e.g. in the upstream Kernel. Its time to check their validity if those struct extensions are really used in VyOS