Wireless is now unified to a single “wireless” package.
Update on some package configurations is dangerous!!!
*) wireless - “wireless-rep” renamed to “wireless”;
*) wireless - “wireless-cm2” discontinued, uninstall it before update;
*) wireless - “wireless” package included in bundle “routeros” package;
*) check-for-updates - with bundle “routeros” package, will replace wireless package automatically;
*) check-for-updates - with one standalone wireless package, will replace wireless package automatically;
*) check-for-updates - with two or more standalone wireless packages, will result in no wireless packages installed, uninstall extra packages first;
*) ccr/crs - fixed SFP+ interface ddmi info reporting function. Info is now refreshed on regular intervals.
*) dude - (changes discussed here: http://forum.mikrotik.com/t/the-dude-v6-37rc-test-builds/100037/1 );
*) ovpn - add special exception route for tunnel itself when using add-default-route;
*) ping - fixed freezing on “not running” interfaces;
*) resource - fixed free-memory reporting after disk eject;
*) x86 - fixed crash when igmp-proxy interface becomes “not running” while passing traffic;
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
Works. Disable, reboot, upgrade. Please do not write uninstall when that is not possible. or be more specific disable if package is bundled in your setup, uninstall if you have manually installed the package.
Updated from 6.36 to 6.37rc4 on a RB951-2n.. Did the update over wireless, but of course it didn’t not come back.
I see I should have updated it over Ethernet.
I had to manually enable ‘Wireless’ package and manually enable the wlan1 interface and re-program SSID/frequency etc.. So its like a fresh new interface (nothing was copied over from cm2)
Apart from that the update went ok.
Using it ok at the moment as a test box..
We are sorry for any inconvenience. As we just released only one wireless package and there were actually four of them in the past, we are still updating our upgrade server so it would work correctly for any case.
When we will fix it only way that you can lose wireless connection will be if you have more than one wireless package outside of bundle package. You have to remove packages manually until only one standalone package is installed. Then (hopefully today) upgrade process must go automatically and you should not see “missing wireless package” errors any more.
So we are to expect that the problems upgrading over wireless will be limited to the rc versions and when final comes out we will be able to do it with the upgrade process automatically uninstall absolete packages ?
Thanks for clarification.
That sounds good enough and for someone like me who always installs bundled package this is a no issue. And I have installed wireless-rep as a separate on a few boards for testing, but only that I can reach by lan.
*) address-list - allow DNS names with “_” symbol;
*) conntrack - fixed ipv6 timeout display;
*) conntrack - fixed removing icmpv6 connections;
*) dude - (changes discussed here: http://forum.mikrotik.com/t/the-dude-v6-37rc-test-builds/100037/1);
*) export - removed unnecessary “log-prefix” on firewall export;
*) firewall - fixed time based rules on time/timezone changes;
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
