Known issues and bugs - a list

RouterOS General
1

Hey guys,

Since there is currently no official known issues list / bug tracker, lets start one here on the forums.

First, a few disclaimers:

  1. This is not an official list, and is not in any way affiliated with MikroTik
  2. Only bugs that are still present in current version will be kept here.
  3. This is a user forum, and MikroTik is not required to view/acknowledge anything that is written in here.
  4. If you report a bug here, please also report it to support@mikrotik.com
  5. This is not a “doesnt work for me” list, but a list of reproducable bugs.

How to get a bug added to the list:
See this post for instructions and a template:
http://forum.mikrotik.com/viewtopic.php?f=2&t=78816#p395374


Here is the current list:
1) MTU error in a PPPoE session on a bonding interface

Hopefully, more people can contribute.

2

How to get a bug added to the list:

  1. Post in a separate post
  2. Post the exact symptoms, and an exact steps required to reproduce and test the bug
  3. Make sure you are testing with the newest version
  4. Please post the ticket number from Mikrotik Support under which the bug is submitted.
  5. If support has acknowledged the bug, you can update your post with details / info if it will be fixed.

Here is a template you can use to structure you bug report posts:

Issue:
[Insert a short name/description for the issue here]

Description:
[Insert a more detailed description here]

Versions affected:
[If more versions than the current version are affected, include them here]

How to reproduce:
[Provide step-by-step instructions on how to reliably reproduce the issue]

Notes:
[Provide any notes or additions you would like]

Support TicketID:
[Ticket ID from support@mikrotik.com]

3

Issue:
MTU error in a PPPoE session on a bonding interface

Description:
It is impossible to run full 1500 byte frames inside of a PPPoE session if the PPPoE session built on top of a bonding interface.
If you send a 1500 MTU frame over the PPPoE session, it is dropped, and this therefore creates MTU issues in this scenario.

Versions affected:
6.x, not tested on 5.x

How to reproduce:
Lets consider the following topology:
3 RouterBoards: AC, swch and client:

L2 connections:
   AC           swch       client
 ehter4 ------ ether4
 ehter5 ------ ether5
               ether3------ether5

AC:/interface bridge
add name=“br - pppoe”
/interface ethernet
set [ find default-name=ether4 ] name=“ether4 - to swch”
set [ find default-name=ether5 ] name=“ether5 - to swch”
/interface bonding
add lacp-rate=1sec mode=802.3ad name=“lacp1 - ether4, ether5” slaves=“ether4 - to swch,ether5 - to swch”
/ip pool
add name=PPPoE ranges=10.4.0.0/24
/ppp profile
add local-address=1.1.1.1 name=pppoe remote-address=PPPoE
/interface bridge port
add bridge=“br - pppoe” horizon=1 interface=ether3
add bridge=“br - pppoe” interface=“lacp1 - ether4, ether5”
/interface pppoe-server server
add default-profile=pppoe disabled=no interface=“br - pppoe” max-mru=1500 max-mtu=1500
/ppp secret
add name=123 password=123 profile=pppoe
/system identity
set name=ACswch:/interface bridge
add name=“br - switch”
/interface ethernet
set [ find default-name=ether3 ] name=“ether3 - to client”
set [ find default-name=ether4 ] name=“ether4 - to AC”
set [ find default-name=ether5 ] name=“ether5 - to AC”
/interface bonding
add lacp-rate=1sec mode=802.3ad name=“lacp1 - ether4, ether5” slaves=“ether4 - to AC,ether5 - to AC”
/interface bridge port
add bridge=“br - switch” interface=“ether3 - to client”
add bridge=“br - switch” interface=“lacp1 - ether4, ether5”
/system identity
set name=swchclient:/interface pppoe-client
add add-default-route=yes disabled=no interface=ether5 max-mru=1500 max-mtu=1500 name=pppoe-out1 password=123 user=123
/system identity
set name=clientNow lets ping the AC inside of the pppoe session from the client:

As you can see, we cant run full 1500 byte frames inside of the PPPoE session, even tho everything is configured properly.

Notes:
This problem occurs because a binding interface does not report its L2MTU, therefor RouterOS assumes that L2MTU = MTU for the bonding interface, which causes a problem, since the PPPoE session adds 8 bytes as the PPPoE header.

Support TicketID:
Ticket#2013080766000343

4

Issue:
SMS receiving stops working and cant be re-enabled

Description:
After 30 minutes, SMS receiving stops working by itself.
It is impossible to re-enable it unless you reboot the router.

Versions affected:
6.11 → 6.4, not tested rest

How to reproduce:/tool sms
set keep-max-sms=20 port=usb1 receive-enabled=yes secret=passwordWait more then 30 minutes and send a SMS to the device.
Log will show:
15:23:16 gsm,error unable to load unread sms: timeoutTrying to re-enable sms receiving by receive-enabled=yes you get a timeout error"
/tool sms set receive-enabled=yes
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)Notes:
Tested with Huawei e220 and e1752
More info also in http://forum.mikrotik.com/t/gsm-error-unable-to-load-unread-sms-timeout/71268/1

Support TicketID:
Ticket#2014031466000686

5

Issue:
“/system leds” is not exported correctly

Versions affected:
6.6 and 6.5, not tested rest

How to reproduce:

Default config:
/system leds> exp

jan/02/1970 00:01:07 by RouterOS 6.6

software id = 7IXG-ZI8H

/system leds
set 0 interface=wlan1
set 1 interface=ether1/system leds> exp ver

jan/02/1970 00:01:08 by RouterOS 6.6

software id = 7IXG-ZI8H

/system leds
set 0 disabled=no interface=wlan1 leds=led1,led2,led3,led4,led5 type=wireless-signal-strength
set 1 disabled=no interface=ether1 leds=user-led type=interface-activityApply a little change:
/system leds
:foreach i in=[find] do= { set $i led=“” }Wrong export output:
/system leds> exp

jan/02/1970 00:03:11 by RouterOS 6.6

software id = 7IXG-ZI8H

/system leds
set 0 interface=wlan1
set 1 interface=ether1/system leds> exp ver

jan/02/1970 00:03:24 by RouterOS 6.6

software id = 7IXG-ZI8H

/system leds
set 0 disabled=no interface=wlan1 leds=“” type=wireless-signal-strength
set 1 disabled=no interface=ether1 leds=“” type=interface-activity
Notes:
As you can see leds=““ is not present in the compact export output.

Support TicketID:
Ticket#2013110566000681

6

Thanks for this list. I hope that will not soon deleted :slight_smile:

7

I will be adding more.

If MikroTik chooses to delete this topic, its their choice.
I would be unhappy, but its their forum :slight_smile:

8

There’s another bug list here: http://bugs.mikrotik-routeros.com/view_all_bug_page.php. I don’t know how active it is though…

9

I ca. Confirm the MTU Issue over L2TP and EOIP
http://forum.mikrotik.com/t/ros-fragment-udp-drop/71533/1

Mistry7

10

This is great idea but at the moment account cannot be created there. Captcha is not working.

11

No offense to the maintaners of that list, but it seems to be kinda abandoned.
There are issues there that are still about 5.x, and only a handful have confirmed/resolved status.

Also, finding a list in the official forums is much easier imo.
I will be rechecking all of the issues here with each new ROS release.

12

Mikrotik Support did you read these thread?

13

MikroTik support is located at support@mikrotik.com, just like it says on top of this page. It would be much better and efficient, to submit bugs to mikrotik support, not post them on various (and multiple) online webpages.

14

As tomaskir wrote. All bugs on this site have their own Support TicketID
This means that bugs were reported …

15

Can we please not argue in here? It seems the topic is headed in that direction, and that is not what I want. :slight_smile:
We are all here because we like MikroTik, use it, and care about it.

The point of this topic is not to point out flaws and bugs, but to put together a list so people know about existing verified issues/problems, and dont bash their heads agains walls. Every software has bugs and flaws.
I am hoping more people can contribute, and submit issues here in a nicely formatted, reproducable manner, so we all know if something doesnt work and is here in this topic, its a reproducable, support-reported issue.

Please read disclaimer 3.

All of the bugs/issues which I personally listed in this topic are reported to support.
One of the points I was hoping to accomplist with this topic is that people submit their bugs to support more and see in what format they could do it to be more helpful.

Even if they are reported, bugs still take a while to fix, MikroTik doesnt have 10 developers they can just throw right away at any issue that arises, we have to understand that. Im not saying there arent issues, or that there arent issues that should have been fixed a long time ago, there certainly are.
And while it is frustrating, being passive-aggressive to a MikroTik staff on forums is not going to help anything :slight_smile:

16

We need a bugzilla web interface to view and edit.

17

I like your idea behind this post and also agree with pcunite that we need a good way to track and organize the bugs. A forum post gets bloated and tedious quickly imo.

We need something 1) easy to use and 2) easy to find, especially for people new to the forum.

Even something as simple a having a new forum category called Bugs would be helpful. And since you can report a bug directly to MikroTik support when submitting a post, that functionality is already built in.

18

Bugzilla or Other Bug reporting System is good idear
Better then Mail support@mikrotik.com it is like Playing lotto
To get an answer! When i get One After 2-4 weeks to Tell Support,
I send answer but Never got a Feed back, thats Bad!

And it is Not efficient for Support to get the Same Bug 20 Times,
And Not controlable for coustomers if this Bug is reported allready!

Mistry7

19

New Bug

May specific to the RB2011UiAS-RM.

I haven’t seen this previously on the RB2011UAS-RM with ROS 6.1.

Encountered with the “as shipped” ROS 6.1

serial console login goes missing after removing default configuration.

I have 10 being updated and configured, and 50% so far have dropped the serial console.

Power up.
via serial port, (r)emove configuration.
add a config and reboot
no serial port login prompt.

Reset Configuration via LCD doesn’t fix it.

Fix:
via Winbox, System Console add serial0.
:slight_smile:

20

Issue:
Source IP of web proxy can’t be configured in WinBox and WebFig. Configure it in terminal is Ok.

Description:
Configure source IP address of web proxy in Web Fig will simply not show. Configure it in WinBox will course inconsistency display of WinBox and Terminal, and it does not become effective. Will be lost after close WinBox.

Versions affected:
6.5, 6.6

How to reproduce:
251.png
Notes:
None

Support TicketID:
Submit this post as a bug report to MikroTik Technical Support