Andrey Smirnov f0ea478cb8

feat: support address priority ...

See https://github.com/jsimonetti/rtnetlink/pull/256

See https://github.com/siderolabs/talos/issues/10696

Support setting address priority, this is important to ensure that the
prefix route has appropriate priority.

For now, we don't have it exposed in the machine config except for the
DHCP4 operator, so now both routes created explicitly by DHCP and routes
created implicitly have same metric/priority:

```
172.20.0.2   network     RouteStatus   inet4//172.20.0.0/24/1024                                1         172.20.0.0/24                                enp0s2      1024
172.20.0.2   network     RouteStatus   inet4/172.20.0.1//1024                                   1                                         172.20.0.1   enp0s2      1024
```

Before this change, the first route would have a metric zero.

Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>

2025-04-16 13:35:37 +04:00

..

network.proto

feat: support address priority

2025-04-16 13:35:37 +04:00