Closed fbecker closed 2 weeks ago
@cathay4t do you know if we have an issue at nmstate for this ?
As the message indicate, you cannot have route on disabled IP stack.
You have to enable IP stack even without address mentioned.
---
routes:
config:
- destination: 198.51.100.0/24
metric: 150
next-hop-interface: eth1
table-id: 254
interfaces:
- name: eth1
type: ethernet
state: up
ipv4:
enabled: true
On second thought, nmstate should support YAML provided by @fbecker , let generate a patch for it.
https://github.com/nmstate/kubernetes-nmstate/issues/1231#issuecomment-2121944023 could be used as workaround.
I have PR https://github.com/nmstate/nmstate/pull/2677 created to support:
---
routes:
config:
- destination: 198.51.100.0/24
metric: 150
next-hop-interface: eth1
table-id: 254
interfaces:
- name: eth1
type: ethernet
state: up
ipv4:
enabled: true
address: []
But routes on disabled IP is still invalid use case.
What happened: Static route configuration fails when configuring next-hop-interface to an interface where ip is disabled.
I'm getting the following error from nnce:
What you expected to happen: To be able to add a route without a next-hop-interface or configured IP address. Just like
How to reproduce it (as minimally and precisely as possible):