*) sstp - report TLS encryption as well;
*) safe mode - do not allow user with less permissions to disrupt active safe mode;
*) console - print command does not try to reuse item numbers assigned by
previous invocations of ‘print’ when doing ‘print where’ or ‘print follow’,
items are numbered consecutively starting from ‘0’.
*) console - fix compact export of some partially modified
configuration values;
*) api - use the same syntax for property values as is used in ‘print detail’
output, with the exception of numbers, that are not shown with suffixes
(K/M/G/T or bitrate) and are not contracted or separated into digit groups,
and “yes”/“no” values that continue to be reported as “true”/“false”.
*) console - show internal numbers in the form returned by ‘find’ (like *9A0F)
instead of “(unknown)” when configuration refers to
deleted items. This change also applies to API.
*) ipsec - fix addition of default policy template;
*) console - values of type ‘nil’ were returning ‘nil’ as result of most
operations. Now it compares less than all values except ‘nil’
and ‘nothing’, and compares inequal to all values except ‘nil’.
This was changed to make ‘print where’ and ‘find where’ more useful.
An example. Previously the following command
/ip route print where routing-mark!=nosuch
Would not print routes that had no value for ‘routing-mark’ set, because
(nil != “nosuch”) was equal to nil. Now it evaluates to ‘true’, and this
command will also print all routes that have no ‘routing-mark’ value set.
*) l2tp - fixed problem on CCR where server responded with wrong source address;
*) console export - put qutes around item names that start with a digit;
*) sntp client - added support for dns lookup of ntp servers;
*) console - when exporting to file, use name ending in ‘.in_progress’, and
rename when export finishes;
*) bridge setups sometimes could crash on CCR devices;
*) fixed port flapping in 1G mode on sfp-sfpplus1 on CRS226;
*) fixed SXT ac model losing it’s interface if changing regulatory settings in “routerboard” menu
As usual, version can be found on our download page, or just click “check for updates” if you already run som v6.x release
Yeah, its not supposed to work on x86, but the fact that the menu is completely missing is a bit misleading to me personally.
It would make more sense IMO to show it anyway, but show “Only supported on RouterBoards”
Also, importing an export file which has “/ip cloud” setting defined in it will fail on x86 this way.
Of course, that is nit-picking and only my personal opinion
Ok, if I install this version, the wireless package; is it the ‘legacy’ one, or the new -fp one? Or do I still install the wireless CAPsMAN package to get the new wireless package?
Or, when a radio already has wireless-fp installed, an upgrade (with the auto process in sys/package/upgrade sequence) will automatically install the upgrade for the wireless -fp, or do I also load the Wirless CAPsMAN?
So, can we have a very, very clear statement on what we need to do in the upgrade from different versions, already or not already installed -fp, to get the new wireless features installed on a board that is going to run 6.18…
It will not mess with your packages. CAPSMAN and 802.11ac still requires Wireess-FP.
If you use legacy wireless, upgrade will install legacy wireless. If you have wireless-fp, upgrade will update wireless-fp.
If you use wireless legacy, and decide you want to use wireless-fp, simply upgrade, and then enable wireless-fp in packages menu (it is included in the bundle).
*) webfig: fixed right when creating new script or schedule, now is possible to set/unset ftp right;
*) winbox: fixed right when creating new script or schedule, now is possible to set/unset ftp right;
*) user-manager: fixed profile limitation creation, now is possible to specify the owner;
You are joking with me? All the bug I find and (very thanks!) your staff fix are never written on changelog!!!
Secondary BUG/ Missing feature: /interface wireless reset-configuration DO NOT ASK FOR CONFIRMATION ON CLI
(using Winbox and pressing the button ask the confirmation)
I’ve remotely upgraded my home 951G-2HnD from 6.17 to 6.18 and after reboot I can’t ping anything, mac address and vlans were disappeared from my home switch but link is up - after work I will check what’s wrong, CCR-1009-1S-1S+ was been successfully updated without problems…
7 hours after the 6.18 was made available still only a hand full of small issues surfaced amongst us users??? What is this, do we finally see a very reliable version or is everybody already having his friday afternoon party before going on holidays…
All I notice so far is the package upgrade in winbox is not working. Probably because the servers are either overloaded, or also on holiday…?
IGMP proxy is still broken in 6.18!!!
Since when do you plan ignoring major bugs and problems??? I can’t understand that mikrotik don’t know how to fix simple problem with IGMP proxy, for which I believe half hour would be enough!
It’s sad that you are selling broken products, you don’t wont to fix them nor you wont refund money!
When upgrade from System Packages Check for Upgrades - I resieve ERROR - getting changelog —>Error:conection timed out
When click on “Download &Upgrade” nothing is hapen.
All the bug I find and (very thanks!) your staff fix are never written on changelog!!!