After downgrading from 3.x to 2.x all wireless settings are lost after reboot. The cards are disabled and set with default setttings. It was tested on rb100 and rb500.
Yes, you will loose all the wireless configuration when you downgrade back to v2.9, that is why you should load the backup after downgrade.
that’s hard to do when you’re downgrading from a remote location. Is there anyway to load the backup or run a script on reboot?
You could write a script and run it with a schedule item scheduled to run at Startup. I would put a :wait 10 at the beginning to make sure everything is up. It’s risky non-the-less. I wouldn’t try it without a good B-Plan.
Yeah i thought of that.. but when using NTP it doesn’t set the clock until its connected to the network..
The NTP doesn’t matter in this mode, I believe, since the script is running at a special “Startup” time not a specific time. When you create the Schedule item, there is a special Startup value for the time. You can also disable the NTP client and you are sure the clock will start at 00:00:00 1/1/1970.
Again, it’s all risky unless you have a connection besides the wireless itself. You can also cut yourself off doing various 2.9 and 3.x upgrades as Mikrotik has changed the country codes and the frequency sets of the countries, so your frequency may not be available in a newer version.
The moral of the story… test, test, test.