I have observed, that when adding a configuration in the WiFi menu and adding it as slave configuration within a provisioning entry and then later on removing the configuration but still leaving it in the provisioning config, it adds an "unknown" entry and a wifi interface with a missing ssid pops up.
Steps to reproduce: (Existing capsman configuration running)
This creates the following entry in winbox:
and in the CLI:
And after running the provisioning step I get some interfaces with missing ssid:Is this normal behaviour or is this a bug? I think normally the missing configuration in the provisioning entries should ideally provision nothing and never create interfaces.
Steps to reproduce: (Existing capsman configuration running)
Code:
/interface/wifi/configuration/add name=buggyConfig ssid=testSSID security.passphrase=test1234/interface/wifi/provisioning/set 2 slave-configurations=buggyConfig/interface/wifi/configuration/remove buggyConfigThis creates the following entry in winbox:
and in the CLI:
And after running the provisioning step I get some interfaces with missing ssid:Is this normal behaviour or is this a bug? I think normally the missing configuration in the provisioning entries should ideally provision nothing and never create interfaces.
Statistics: Posted by robtor — Fri Feb 16, 2024 9:12 pm