What’s new in 6.6 (2013-Nov-01 15:16):
*) winbox - fixed problem where all previous session opened windows were read only;
*) certificate - no more ‘reset-certificate-cache’ and ‘decrypt’ commands,
private keys can be decrypted only on ‘import’, use ‘decrypt’ before upgrade if needed;
*) fixed arp-reply only with more than one ip address on interface;
*) fixed RB400 not to reboot by watchdog during micro-sd format;
*) web proxy - fix SPDY server push handling;
*) certificate - merged ‘/certificate ca issued’, ‘/certificate scep client’ and
‘/certificate templates’ into ‘/certificate’;
*) added support for new Intel 10Gb ethernet cards (82599);
*) certificates - fixed certificate import;
*) wireless - fixed crash when dfs was enabled on pre-n wireless cards;
MT team, can you tell me if the problem here fixed or not?
What’s new in 6.6 (2013-Nov-05 16:15):
*) winbox - fixed problem where all previous session opened windows were read only;
*) certificate - no more ‘reset-certificate-cache’ and ‘decrypt’ commands,
private keys can be decrypted only on ‘import’, use ‘decrypt’ before upgrade if needed;
*) fixed arp-reply only with more than one ip address on interface;
*) fixed RB400 not to reboot by watchdog during micro-sd format;
*) web proxy - fix SPDY server push handling;
*) certificate - merged ‘/certificate ca issued’, ‘/certificate scep client’ and
‘/certificate templates’ into ‘/certificate’;
*) console - :foreach command can iterate over keys and values in an array,
by specifying two counter variables, e.g.:
:foreach k,v in=[/system clock get] do={:put “$k is $v”};
*) added support for new Intel 10Gb ethernet cards (82599);
*) certificates - fixed certificate import;
*) wireless - fixed crash when dfs was enabled on pre-n wireless cards;
*) winbox - fixed problem where all previous session opened windows were read only;
*) certificate - no more ‘reset-certificate-cache’ and ‘decrypt’ commands,
private keys can be decrypted only on ‘import’, use ‘decrypt’ before upgrade if needed;
*) fixed arp-reply only with more than one ip address on interface;
*) fixed RB400 not to reboot by watchdog during micro-sd format;
*) web proxy - fix SPDY server push handling;
*) certificate - merged ‘/certificate ca issued’, ‘/certificate scep client’ and
‘/certificate templates’ into ‘/certificate’;
*) console - :foreach command can iterate over keys and values in an array,
by specifying two counter variables, e.g.:
:foreach k,v in=[/system clock get] do={:put “$k is $v”}; ) added support for new Intel 10Gb ethernet cards (82599); ) certificates - fixed certificate import; ) wireless - fixed crash when dfs was enabled on pre-n wireless cards;
**[u]) fixed port flapping on CCR;[/u]
What’s new in 6.6 (2013-Nov-06 10:23):
*) winbox - fixed problem where all previous session opened windows were read only;
*) certificate - no more ‘reset-certificate-cache’ and ‘decrypt’ commands,
private keys can be decrypted only on ‘import’, use ‘decrypt’ before upgrade if needed;
*) fixed arp-reply only with more than one ip address on interface;
*) fixed RB400 not to reboot by watchdog during micro-sd format;
*) web proxy - fix SPDY server push handling;
*) certificate - merged ‘/certificate ca issued’, ‘/certificate scep client’ and
‘/certificate templates’ into ‘/certificate’;
*) console - :foreach command can iterate over keys and values in an array,
by specifying two counter variables, e.g.:
:foreach k,v in=[/system clock get] do={:put “$k is $v”};
*) added support for new Intel 10Gb ethernet cards (82599);
*) certificates - fixed certificate import;
*) wireless - fixed crash when dfs was enabled on pre-n wireless cards;
*) fixed port flapping on CCR;
I know this has been asked before, but I cannot find a definitive answer, so let me ask again: Mikrotik, are you working on NV2 tweaking and/or optimization, especially towards reducing jitter and improving throughput in PtMP scenarios?
Also, are you looking into the much-reported low TCP throughput issues? Can we expect a relevant upgrade in the 6.x series?
have you specified the timezone in the correct places? you know, the timezone can be specified for the router, the customer and the user - all separate places.