diff options
| author | Christian Breunig <christian@breunig.cc> | 2026-10-07 19:57:10 +0200 |
|---|---|---|
| committer | Christian Breunig <christian@breunig.cc> | 2026-10-31 09:58:29 +0000 |
| commit | 5fdfcca2a97dabf3c6410a1362c0726142d2acc8 (patch) | |
| tree | b7fbbdebe7d1f12552fcb3c938e8e1baa74bb184 /interface-definitions/include/interface/vlan-protocol.xml.i | |
| parent | fb0e36092529d4d6947749009c00d7ff74b0c551 (diff) | |
| download | vyos-1x-5fdfcca2a97dabf3c6410a1362c0726142d2acc8.tar.gz vyos-1x-5fdfcca2a97dabf3c6410a1362c0726142d2acc8.zip | |
interfaces: T3871: never rename an interface which is in use
Editing the map and then plugging any card in applied the edit to every
interface at once, because the pass re-resolves the whole system whatever
woke it. A running port was renamed out from under the configuration still
naming it, a bridge member included since members became discoverable.
Leave a name alone while the system is relying on it - the port is up, or it
has a master. At boot that is true of nothing, as the pass runs before the
configuration is applied, so naming is unaffected; afterwards it is true of
everything configured, and a card which has just arrived is still down. Say
in the log and the status file when a rename was refused, as the map and the
running system then disagree until the next boot.
Diffstat (limited to 'interface-definitions/include/interface/vlan-protocol.xml.i')
0 files changed, 0 insertions, 0 deletions
