2.9.13 is out...

RouterOS General
1 
What's new in 2.9.13:

*) added support for SSH DSA keys;
*) fixed bug - nstreme link with framer-policy=dynamic-size was not
   taking into account framer-limit;
*) fixed bug - RADIUS disconnect request did not work;
*) fixed problem - PPPoE server had too aggressive initial timeouts, and 
   some clients could not connect;
*) improved WPA link establishment for WDS;
*) fixed problem - interface graphs got lost on reboots;

Any comments? :wink:

2

yup, x86, uploaded, rebooted, kernel panic, ā€œattempt to kill initā€, used netinstal to rebuild with 2.9.12, uploaded 2.9.13, reboot, now all packages enabled (wireless, w-legacy, routing, routing-test, ā€¦). Now going to disable unwanted packagesā€¦

3

I have upgraded my 2.9.11 to 2.9.13 and OSPF log is not working now. Problem is with both routing and routing-test.

4

what are you waiting for? report to support@mikrotik.com with supout.rif files

5

Does anyone know why this happens with an upgrade from 2.9.12 to 2.9.13, in a RB532A with 6 ether doughter board.

WARNING: link failed: Invalid cross-device link
WARNING: link failed: Invalid cross-device link
WARNING: link failed: Invalid cross-device link
WARNING: link failed: Invalid cross-device link
WARNING: link failed: Invalid cross-device link
installed routeros-rb500-2.9.13
mount: Mounting /root on / failed: Device or resource busy
Restarting system.

6

You can ignore these errors.

7

This version of routing-test has a very broken OSPF.

  1. OSPF logging does not work

  2. OSPF ā€˜diesā€™, all routes go missing, and entire platform responds very slowly at least 5 times per day.

Rolled back to 2.9.12 + 2.9.12 routing-test and all is well again.

Not worth sending a supout.rif - its easily replicated.


Why do the change logs never contain everything ? eg:-
Resource graphs from 2.9.12 fixed
OSPF in routing-test modified in some way but weā€™re not fully sure what we actually did to it