2.9.14 Released

RouterOS General
1

What’s new in 2.9.14:

*) fixed upgrade from version 2.8 to keep correct order in web-proxy
rule lists and radius server list;
*) ping shows more types of ICMP reply messages, including
destination unreachable;
*) fixed some ethernet card autonegotiation/speed/duplex settings;
*) RB500 ether1 interface has mdix-enable feature (enabled by default)
*) fixed bgp in routing package, did not work in previous version;
*) fixed amount of free-hdd-space on RB500;

2

On this post:
http://forum.mikrotik.com//viewtopic.php?p=30397#30397

@normis say:

we fixed it. you could say that RouterOS is the first program to detect and drop this super encrypted azureus traffic Smile

But on the change log doesn’t say nothing of azureus

Maximliano Dobladez
Intercity SRL
Rio Cuarto - Argentina

3

What’s new with BGP? When do you expect the routing-test package to go “gold” and appear in WinBox?

Thanks,

Brad

4

Well is seems it works now, I wouldnt hold your breath about it going gold, its still extremely unstable in alot of cases, certainly too many for it to be considered stable.

Static routes for the win :stuck_out_tongue:

5

See this post…
http://forum.mikrotik.com/t/2-9-13-bgp-broken/5279/1

If you extensively use BGP do not bother with 2.9.14 …. Stick to 2.9.12. It’s the last known version with BGP working. That being said, at some point in time MT has to change default settings of keepalive and hold timers to something else than 0. Its not good practice and we use it with different settings. We are still testing an optimum combination for our network but going by the book it seems that keepalive-timer=10
hold-timer=30 seem to work ok..

Due to the large network we have over here (see http://wind.awmn.net ), and with extensive use of BGP and OSPF we are in position to discover bugs in the routing packages in a matter of hours if not much less.

2.9.13 and 14 have a weird problem leaving you with all peers at an “unknown” state when links around start to flap or wireless links on a router are administratively shutdown or they are just shut down from the other side due to errors or maintenance. It looks like the BGP kicks off, calculates shortest paths ok, but when something goes wrong somewhere in the network it falls in a loop or something and it crashes??…

Most of the above are speculations of buggy behavior but the fact remains that the BGP package, even the stable one has hick ups whereas at this point the package can not be called stable at all.

During the update, one of the routers had some warnings on screen after the update and did not reboot at all. It needed a manual switch off/on.
Another one crashed completely… but for that one I have advised it’s admin to post his comments, troubleshooting files and details.

We will be very glad to help (IF we can at any way) and resolve issues as fast as possible…

6

i just changed back to 2.9.13 because one of my rb532 with 2x 2.4ghz and 1x 5ghz AP has been rebooted twice allready by the watchdog timer !!

never had this before

7

looks like the change didn’t make it into 2.9.14 after all. .15 then

8

While we’re at it, can you also please include the graphing tool bug fix in the next realease? MT v2.9.14 still doesn’t save the interface graphs (the previous graphs dissappear every time MT is rebooted).

Thanks!

9

I upgraded main main box from 2.9.11 to 2.9.14 and soo i started have problems about ethernet. In facet on some interfaces after some triffic they stooped to work, a disable/enable cycle let them to work again.
Some hours later my box freezedup without any log and I didn’t have the possibility to supout a file.

Now I reverted back to 2.9.11 and teh ethernet problems went away, but I got the second freez this morning. This never happen before.

What could be broken???
Any similar experience?

Regards
Rosario

10

did you send a supout.rif file that was made during the problem? very important these files

11

yes I send the supout file about ethernet problem yesterday evening.

But I was not able to make supout after the system lockup because I had to hard reset it.

Let me know what can I do in those cases.
Rosario

12

more tests on a spare box pushed me to think that the problem is related to the presence of routerboard package on a x86 box, disabling it the problem went away.
But it was only a quick test so I don’t bet on it.

Regards
Rosario