Mayby I am reinventing wheel but IMHO it is better to inform all that not.

I have been upgrading 433 configured as CAPSMAN from 6.3.92.to 6.40.3 and "incidentally" I have disabled Wireless package ... do not ask why ... please do not
After upgrade there was no WiFi in the building ... I am not suprised ... so I have reenabled Wireless and .... there was no CAP interfaces configured, bridges with "unknown" interfaces .... simply writing: "disaster". Security settings have recurred but CAPSMan was in not working mode.

Lucky me ... I have had a backup ... download ros_6.39.2 ... downgrade ... restore .... restore CAPs to previos version of ROS ... everything works as previously ... oof!!!!!

The moral no 1 from this story is: always have a backup
The moral no 2 is: disabling Wireless module could kill CAPSMAN configuration.

Hello

Moral no 3 is to test in a lab.

How many times have I done something thinking it was routine and it went baaaad. [emoji1]

Thanks for sharing.


Sent from Tapatalk

Interesting.

Funny thing is I've seen Routerboards keep hardware configs for hardware that wasn't there any more, pretty tough to pull bad data out of a config short of a full reset.

Windows has a similar issue. If a network interface is dead (lightning, removed, etc) and you rename the new interface with the same name (I tend to name my wireless cards by their hardware, 802.11ac, bgn, an, Atheros AC, etc), the old name is still in the registry but the interface is gone. You cannot have two devices with the same name but you can't delete settings on a device that isn't there. In Windows there are a dozen different ways to fix that, not so much in ROS.

Odd how disabling the wireless package cleared out your config like that.

Info to store away for a later time...

Interesting is that removed part of it ... dynamic interfaces and therefore they have gone from bridges.
Missing interfaces have been recreated but names have been different so there was no match in bridge configs .

The interesting thing I have learned is that disabling module does not just disable all configuration from "disabled package area". It could just vanish.

I do not want to decide if it is bad or not, just sharing info to prevent configuration damage before, not after.