Happens on Hap and Cap Ax3 devices when provisioned by capsman.
My config renames the master wifi1 and wifi2 interfaces, however on reboot a cap under capsman control at the time recreates wifi1 and wifi2 interfaces with no config.
If I disable capsman at the cap and reboot, it doesn’t happen. Capsman provisioned config is the same as local provisioned config for fallback if capsman is unavailable.
Everything is scripted. Everything else works as expected.
Slaves Static = ON
Is this behavior by design, a config issue on my part or a bug, timing issue?
Why would you want to do that ??
It’s a cap, who cares what the interfaces are labeled then ?
You are making it yourself difficult by deviating from all default config, help pages, instructions, …
How are your provisioning rules ?
Static enabled or dynamic enabled or … ?
If you want more detailed answers, it might be needed to provide config for both capsman controller as well as cap.
But I would stop renaming those interfaces. Problems most likely will already stop then.
In my script I wasn’t setting manager=local-or-capsman in /interface wifi configuration
Instead, I was setting it manually after applying the script Winbox, under the configuration tab in the wifi settings as an override rather than setting it in the named configuration.
Setting the manager in a named configuration rather than overriding resolves the issue.