Community discussions

 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Known issues and bugs - a list

Tue Nov 12, 2013 4:49 pm

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 ... 16#p395374


Here is the current list:
1) MTU error in a PPPoE session on a bonding interface
- http://forum.mikrotik.com/viewtopic.php ... 75#p395375
2) SMS receiving stops working and cant be re-enabled
- http://forum.mikrotik.com/viewtopic.php ... 77#p395377
3) Unable to initialize a system variable via SMS
- http://forum.mikrotik.com/viewtopic.php ... 50#p406340
4) Router looks in the main routing table and not in a VRF for ICMP TTL exceeded (type 11)
- http://forum.mikrotik.com/viewtopic.php ... 00#p414018
5) Queue type default-small not exported with export compact
- http://forum.mikrotik.com/viewtopic.php ... 49#p417649
6) "RouterOS Default Configuration" windows shows when it should not
- http://forum.mikrotik.com/viewtopic.php ... 56#p422756
7) Can't list or delete files with overly long filenames
- http://forum.mikrotik.com/viewtopic.php ... 73#p424572
8) Winbox doesn't unlock files after uploading a whole folder
- http://forum.mikrotik.com/viewtopic.php ... 58#p426189


This list is current for v6.17 release.

Hopefully, more people can contribute.
Last edited by tomaskir on Fri Jul 18, 2014 6:52 pm, edited 60 times in total.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Tue Nov 12, 2013 4:50 pm

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]
----- ----- -----
Last edited by tomaskir on Tue Nov 12, 2013 5:33 pm, edited 1 time in total.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Tue Nov 12, 2013 4:51 pm

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:

ros code

/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=AC
swch:

ros code

/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=swch
client:

ros code

/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=client
Now lets ping the AC inside of the pppoe session from the client:
Image

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
Last edited by tomaskir on Thu Apr 24, 2014 2:29 pm, edited 5 times in total.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Tue Nov 12, 2013 4:59 pm

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:

ros code

/tool sms
set keep-max-sms=20 port=usb1 receive-enabled=yes secret=password
Wait more then 30 minutes and send a SMS to the device.
Log will show:

ros code

15:23:16 gsm,error unable to load unread sms: timeout
Trying to re-enable sms receiving by receive-enabled=yes you get a timeout error"

ros code

/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/viewtopic.php?f=2&t=78593

Support TicketID:
Ticket#2014031466000686
Last edited by tomaskir on Tue Mar 25, 2014 5:23 pm, edited 4 times in total.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Tue Nov 12, 2013 5:10 pm

Issue:
"/system leds" is not exported correctly

Versions affected:
6.6 and 6.5, not tested rest

How to reproduce:

Default config:

ros code

/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

ros code

/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-activity
Apply a little change:

ros code

/system leds
:foreach i in=[find] do= { set $i led="" }
Wrong export output:

ros code

/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

ros code

/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
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
honzam
Forum Guru
Forum Guru
Posts: 2292
Joined: Wed Feb 27, 2008 10:27 pm
Location: Czech Republic

Re: Known issues and bugs - a list

Tue Nov 12, 2013 6:11 pm

Hey guys,
Since there is currently no official known issues list / bug tracker, lets start one here on the forums.
Thanks for this list. I hope that will not soon deleted :)
LAN, FTTx, Wireless. ISP operator
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Tue Nov 12, 2013 6:15 pm

Thanks for this list. I hope that will not soon deleted :)
I will be adding more.

If MikroTik chooses to delete this topic, its their choice.
I would be unhappy, but its their forum :)
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
skot
Long time Member
Long time Member
Posts: 586
Joined: Wed Nov 30, 2011 3:05 am

Re: Known issues and bugs - a list

Sat Nov 16, 2013 9:02 am

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...
I don't need any karma... I have Ιησους Χριστος!
 
mistry7
Forum Guru
Forum Guru
Posts: 1326
Joined: Tue Oct 13, 2009 11:57 am
Location: Germany

Re: Known issues and bugs - a list

Sun Nov 17, 2013 1:58 am

I ca. Confirm the MTU Issue over L2TP and EOIP
http://forum.mikrotik.com/viewtopic.php?f=2&t=78880

Mistry7
 
User avatar
payday
Member Candidate
Member Candidate
Posts: 233
Joined: Thu Aug 16, 2012 11:05 pm

Re: Known issues and bugs - a list

Sun Nov 17, 2013 2:51 am

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...
This is great idea but at the moment account cannot be created there. Captcha is not working.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Sun Nov 17, 2013 4:28 pm

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...
This is great idea but at the moment account cannot be created there. Captcha is not working.
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.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
mistry7
Forum Guru
Forum Guru
Posts: 1326
Joined: Tue Oct 13, 2009 11:57 am
Location: Germany

Re: Known issues and bugs - a list

Tue Nov 19, 2013 10:27 am

Mikrotik Support did you read these thread?
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Tue Nov 19, 2013 12:29 pm

Mikrotik Support did you read these thread?
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.
No answer to your question? How to write posts
 
User avatar
honzam
Forum Guru
Forum Guru
Posts: 2292
Joined: Wed Feb 27, 2008 10:27 pm
Location: Czech Republic

Re: Known issues and bugs - a list

Tue Nov 19, 2013 7:01 pm

As tomaskir wrote. All bugs on this site have their own Support TicketID
This means that bugs were reported ......
LAN, FTTx, Wireless. ISP operator
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Tue Nov 19, 2013 7:19 pm

Can we please not argue in here? It seems the topic is headed in that direction, and that is not what I want. :)
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.
Mikrotik Support did you read these thread?
Please read disclaimer 3.
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.
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.
As tomaskir wrote. All bugs on this site have their own Support TicketID
This means that bugs were reported ......
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 :)
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
pcunite
Forum Veteran
Forum Veteran
Posts: 945
Joined: Sat May 25, 2013 5:13 am
Location: USA

Re: Known issues and bugs - a list

Tue Nov 19, 2013 7:41 pm

We need a bugzilla web interface to view and edit.
 
User avatar
skot
Long time Member
Long time Member
Posts: 586
Joined: Wed Nov 30, 2011 3:05 am

Re: Known issues and bugs - a list

Tue Nov 19, 2013 7:51 pm

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.
I don't need any karma... I have Ιησους Χριστος!
 
mistry7
Forum Guru
Forum Guru
Posts: 1326
Joined: Tue Oct 13, 2009 11:57 am
Location: Germany

Re: Known issues and bugs - a list

Tue Nov 19, 2013 11:57 pm

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
 
K1w1user
newbie
Posts: 31
Joined: Thu Mar 21, 2013 12:28 am

Re: Known issues and bugs - a list

Wed Nov 20, 2013 3:13 am

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.
:)
 
Sander
newbie
Posts: 30
Joined: Sat Aug 18, 2012 5:50 am
Location: Shanghai

Re: Known issues and bugs - a list

Wed Nov 20, 2013 4:55 am

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
You do not have the required permissions to view the files attached to this post.
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Wed Nov 20, 2013 9:23 am

This has been explained before. Why Bugzilla interface will not work.

1. Somebody reports a "bug". Something is not working
2. Everyone thinks this is a bug, and starts to worry, to downgrade, to switch to other hardware
3. Support finds that "bug" was actually caused by typo mistake in firewall rule.
4. Bug is closed as "Invalid" but damage in #2 can't be undone

In support emails, 90% of bugs are not bugs, but mistakes. Imagine what will happen, if they will all be listed publicly as "bugs".
No answer to your question? How to write posts
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Wed Nov 20, 2013 11:58 am

Normis, a question:
Does "Submit this post as a bug report to MikroTik Technical Support" here in the forums work? Is sending a ticket directly to support preferable?
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Wed Nov 20, 2013 12:01 pm

Normis, a question:
Does "Submit this post as a bug report to MikroTik Technical Support" here in the forums work? Is sending a ticket directly to support preferable?
It works, but it is preferred that you include a supout.rif file and full description, because we only receive this one post, not whole thread.
No answer to your question? How to write posts
 
dadaniel
Member Candidate
Member Candidate
Posts: 158
Joined: Fri May 14, 2010 11:51 pm

Re: Known issues and bugs - a list

Wed Nov 20, 2013 12:04 pm

In support emails, 90% of bugs are not bugs, but mistakes.
Your e-mail-support is very good, but getting an answer takes way to long. I do not have the time to wait 1 week for each reply of the same case number. Sorry...
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Wed Nov 20, 2013 12:08 pm

Issue:
Source IP of web proxy can't be configured in WinBox and WebFig. Configure it in terminal is Ok.
Tested on a few devices here on my end as well, confirmed. Added to the list, thanks!
New Bug
May specific to the RB2011UiAS-RM.
I haven't seen this previously on the RB2011UAS-RM with ROS 6.1.
Please remember to use the format outlined in the 2nd post if you want a bug added. Also, please remember to use newest ROS, which is 6.6.
Also, please remember, the bugs/issues in here have to be reliably reproducable.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
pcunite
Forum Veteran
Forum Veteran
Posts: 945
Joined: Sat May 25, 2013 5:13 am
Location: USA

Re: Known issues and bugs - a list

Wed Nov 20, 2013 3:13 pm

This has been explained before. Why Bugzilla interface will not work.

... SKIP ...

In support emails, 90% of bugs are not bugs, but mistakes. Imagine what will happen, if they will all be listed publicly as "bugs".
Normis,
I respectfully disagree with the conclusion of what Bugzilla will do for MikroTik. If you're truly getting 90% configuration mistakes then you have just identified a big problem: communication.

Us techies are here to help your brand for free and I can tell you that they are asking for the simplest of things. I wish there was a place I could send them, a link for the same questions over and over. Bugzilla, at least for me, would show them proof there is not bug.

The perception I'm getting from others about your brand is that, it is buggy. Bugzilla is not your problem. Small thinking will be the death of you guys. Think big!
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Wed Nov 20, 2013 3:21 pm

RouterOS is very complex, there are huge configurations that can be made. Sometimes finding this configuration mistake takes days. There will be no "one place" to send them to, as every case is unique. RouterOS is not something like "Firefox", where all solutions are "click here, not here". It is very rare that two people will have same problem and same solution.
No answer to your question? How to write posts
 
User avatar
pcunite
Forum Veteran
Forum Veteran
Posts: 945
Joined: Sat May 25, 2013 5:13 am
Location: USA

Re: Known issues and bugs - a list

Wed Nov 20, 2013 3:41 pm

Normis,
You know more about MikroTik than I do, so I won't argue your points. However, understand that I'm personally responsible for people purchasing seven different MikroTik products in the last months and I did not make a dime on that.

Give us something to help your brand. Make videos of the most common questions. If it was not for Greg Sowell's outdated videos on YouTube I would be lost. The MUM videos are way too hard to hear or understand. This is not an insult but those people are not gifted teachers, they are techies.

MikroTik can do better. We are on your side. Open up some more ... nothing bad will come of that.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Wed Nov 20, 2013 4:11 pm

On the issue of bugzilla, or a similar public web-interface, I am also against it. It would get bloated to death with millions of posts that are not bugs, but problems in configs, people not understanding how something works, etc. Also, you have to realize that implementing something as bugzilla into their system, MikroTik is opening more potential security holes into their systems, has another system for maintanance, etc. You have to look at it from MikroTiks point of view as well, it would be a lot of work, testing, verification and QA needed to implement it, for potentionally small benefits.

I do agree that there really should be an official bug/issue tracker, but that has been discussed on the forums forever... so lets not go into that. If/when MikroTik chooses to make one, it will happen, untill then we can only hope.

I would really like if wiki was more often updated tho. Also, in some sections, its bloated with not-needed material, while in others, it lacks details. But again, MikroTik is what it is in that regard, its the same as with ROS change-logs, people have been asking for more detailed change-logs forever now.

To pcunite:
Send those people to wiki. I often find that people just refuse to read, when most of MikroTik is actually fairly well described and documented on the wiki.

Since official "manual" content on the wiki can not be edited by users, maybe a system where edits can be offered, considered and then approved by official MikroTik staff would help. You know, wiki's are kinda made for that.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Wed Nov 20, 2013 4:15 pm

Wiki is open for registration by request. I will gladly offer you editing rights to our Wiki. Public registration was closed because of spam, and people promoting their services. If you only wish to correct the occasional mistake in our content, you are welcome to contact us for an account
No answer to your question? How to write posts
 
voxframe
Member Candidate
Member Candidate
Posts: 126
Joined: Thu Dec 16, 2010 2:51 pm

Re: Known issues and bugs - a list

Wed Nov 20, 2013 4:19 pm

Normis,

I agree that an open public bug system is a bad idea.

HOWEVER, what I wish Mikrotik would do is have some form of public list of EXACTLY what known bugs are currently in the firmware, what kind of fixes are being applied, and what is the ETA of each one.

There needs to be a single, up-to-date reference for people to check so they may become aware of what are the known issues.

If someone sends you a support file, and you find a bug, POST IT!
If you're working on a bug that you found, and it's scheduled to be in update XX, POST IT!

There needs to be more clear communications from the development team regarding issues/bugs/problems/fixes/ETAs/etc.

Currently they are a mess of spread out topics on a forum, they are nearly impossible to search without wasting a lot of time.

The forum is NOT a good method for dealing with this, unless it is a locked topic that is sticky to the top of each page (And it actually gets updated on a regular basis! Every morning for example)
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Wed Nov 20, 2013 4:23 pm

I agree with Voxframe. We currently post very widespread issues on the Download page in a "Note", but this is not always the case. We will try to improve in this area. We would like to avoid scaring people from upgrading, if the known bug is specific only to some configurations, it's one of the reasons we haven't made such list yet.
No answer to your question? How to write posts
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Wed Nov 20, 2013 4:28 pm

Wiki is open for registration by request. I will gladly offer you editing rights to our Wiki. Public registration was closed because of spam, and people promoting their services. If you only wish to correct the occasional mistake in our content, you are welcome to contact us for an account
Are you talking about actually editing the topics uder Manual? http://wiki.mikrotik.com/wiki/Manual:TOC

I have a wiki account from the days of old, and I have written a few wiki articles. However, currently on the wiki there is only editing, there is no way to offer and edit that can be discussed and then approved by you (MikroTik).

I would be happy to offer some edits and changes from my perspective. I would happily spend time going through the wiki, looking for for things that can be clarified, potential errors, etc.
But I do not want to touch the official documentation without my changes first being reviewed and approved by MikroTik staff, and afaik, that functionality is not on the wiki.

EDIT: Also thank you for joining us and actually discussing these things with us Normis.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
pcunite
Forum Veteran
Forum Veteran
Posts: 945
Joined: Sat May 25, 2013 5:13 am
Location: USA

Re: Known issues and bugs - a list

Wed Nov 20, 2013 4:50 pm

I'm really scared to edit the wiki because I need my writings to be verified. For example my VoIP QoS article has not been verified by experts. It's almost like we need a separate area for document writers and testers to share their experiences and get feedback from experts at MikroTik. Keep out the newbs in this area. MikroTik is not going to scare me personally away from their products because I'm made aware of bugs. I already know about your bugs! :-)

Here is what MikroTik needs to work hard on and get us all on board with.
  • 1. Why are we scared to update? Fear of the unknown is one reason.
    2. Who is the public product evangelist for MikroTik that makes me look good when I refer people to you?
    3. Who is responsible for making beautifully done videos (and wiki articles) that answer the top 20 questions?
I’m not an Apple fan boy (I use Android) but they control the software and the hardware and that makes for a great experience. MikroTik needs to control the platform for the education and support of their users. By platform I mean a great website where I can help others, where MikroTik helps me. Why is VoIP optimization sold by a third party individual for $200 when MikroTik knows how to do this better than anyone? I can make money and so can MikroTik if we open up the communication better.
 
User avatar
honzam
Forum Guru
Forum Guru
Posts: 2292
Joined: Wed Feb 27, 2008 10:27 pm
Location: Czech Republic

Re: Known issues and bugs - a list

Wed Nov 20, 2013 5:14 pm

This has been explained before. Why Bugzilla interface will not work.

1. Somebody reports a "bug". Something is not working
2. Everyone thinks this is a bug, and starts to worry, to downgrade, to switch to other hardware
3. Support finds that "bug" was actually caused by typo mistake in firewall rule.
4. Bug is closed as "Invalid" but damage in #2 can't be undone

In support emails, 90% of bugs are not bugs, but mistakes. Imagine what will happen, if they will all be listed publicly as "bugs".
You have true. If bugzila not suitable, suggest a way to inform the (forum) Mikrotik users.
For example: Official topic on forum -> you want to edit it as needed.

For example, in the current version 6.6 is a bug when using the VLAN on Bridge. But how does it know? Read Topic 6.6 and browse and search all sides who reported what ...
LAN, FTTx, Wireless. ISP operator
 
alexspils
Member Candidate
Member Candidate
Posts: 176
Joined: Thu Jun 05, 2008 8:57 pm

Re: Known issues and bugs - a list

Wed Nov 20, 2013 5:59 pm

Issue:
DHCP Not work with intel i350-t4
Versions affected:
6.6->6.2,5.26 ok
How to reproduce:
Enable dhcp server on any of 4 eth ports of card,add lease for test pc or config dynamic pool and try to receive ip.
 
Sander
newbie
Posts: 30
Joined: Sat Aug 18, 2012 5:50 am
Location: Shanghai

Re: Known issues and bugs - a list

Thu Nov 21, 2013 6:30 am

Issue:
DNS cache does not update for static DNS name change

Description:
DNS cache will add new record instead of update when you change a static DNS name.

Versions affected:
6.6

How to reproduce:
Add a static DNS record with name "test.local" and address "192.168.8.1", then change name to "test1.local". You will see a new record "test1.local" added to cache, and "test.local" is still there.
252.png
Notes:
I can't find any way to delete "test.local" in DNS cache, except router reboot.

Support TicketID:
None, not report to MikroTik Technical Support
You do not have the required permissions to view the files attached to this post.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Fri Nov 22, 2013 12:36 pm

Issue:
DNS cache does not update for static DNS name change
Verified and added to the list.

PLEASE submit this to support@mikrotik.com and update your post with a support ticket ID.
Just copy your post from here to the email, it should be enough.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Fri Nov 22, 2013 12:54 pm

Issue:
DNS cache does not update for static DNS name change
Verified and added to the list.

PLEASE submit this to support@mikrotik.com and update your post with a support ticket ID.
Just copy your post from here to the email, it should be enough.
I checked this several times, and can't get it to repeat. Please submit to support with detailed steps how to repeat.
No answer to your question? How to write posts
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Fri Nov 22, 2013 1:03 pm

I checked this several times, and can't get it to repeat. Please submit to support with detailed steps how to repeat.
Here is a ticket with exact steps: Ticket#2013112266000451

Any more info on all the discussion about the wiki? I think that was actually a fairly fruitful and useful debate :)
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
doush
Long time Member
Long time Member
Posts: 625
Joined: Thu Jun 04, 2009 3:11 pm

Re: Known issues and bugs - a list

Fri Nov 22, 2013 2:51 pm

Normis;

Just make a known issues thread for each version. That is very simple.
Let us know what is buggy.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Mon Nov 25, 2013 11:25 am

Issue:
PPTP/SSTP - could not add bridge port - BCP not working

Description:
BCP for SSTP and PPTP does not work, if a client with a bridge configured attemts to connect, he can not. Errors in logs stay "could not add bridge port"

Versions affected:
6.7, 6.6

How to reproduce:
Connect 2 RBs on ether 5.

Apply config for AC:

ros code

/interface pptp-server
add name=pptp-in1 user=pptp
/interface sstp-server
add name=sstp-in1 user=pptp
/interface bridge
add name=br_ppp
/ppp profile
add bridge=br_ppp local-address=2.2.2.1 name=pptp remote-address=2.2.2.2
/interface bridge port
add bridge=br_ppp interface=ether3
/interface pptp-server server
set default-profile=pptp enabled=yes keepalive-timeout=5
/interface sstp-server server
set default-profile=pptp enabled=yes keepalive-timeout=5 max-mru=1450 max-mtu=1450
/ip address
add address=1.1.1.1/24 interface=ether5 network=1.1.1.0
/ppp secret
add name=pptp password=pptp profile=pptp
/system identity
set name=SSTP_AC
Apply configs for client:

ros code

/interface bridge
add name=br_ppp
/ppp profile
add bridge=br_ppp name=pptp
/interface sstp-client
add connect-to=1.1.1.1 keepalive-timeout=5 name=sstp-out1 password=pptp profile=pptp user=pptp verify-server-address-from-certificate=no
/interface pptp-client
add connect-to=1.1.1.1 keepalive-timeout=5 name=pptp-out1 password=pptp profile=pptp user=pptp
/interface bridge port
add bridge=br_ppp interface=ether3
/ip address
add address=1.1.1.2/24 interface=ether5 network=1.1.1.0
/system identity
set name=SSTP_Client
PPTP and SSTP can not connect. Errors in log regarding "could not add bridge port"

Notes:
If you disable the static binding on the AC, sometimes the client connects, and sometimes the same error occurs in the logs on the client.

Support TicketID:
Ticket#2013112566000268
Last edited by tomaskir on Mon Dec 02, 2013 3:43 pm, edited 1 time in total.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Mon Dec 02, 2013 12:37 pm

Issue:
L2TP Server bug - replies from wrong IP address

Description:
When a router has multiple IP addresses on an interface, an L2TP server always uses the lowest IP address as the source address of L2TP packets, which makes the L2TP connection impossible to establish.

Versions affected:
6.14-6.0, 5.x

How to reproduce:
Connect 2 RB's on ether5. Apply configs:

L2TP AC:

ros code

/interface l2tp-server server
set enabled=yes
/ip address
add address=10.0.0.1/24 interface=ether5 network=10.0.0.0
add address=1.1.1.1/32 interface=ether5 network=1.1.1.1
/ip firewall mangle
add action=log chain=input port=1701 protocol=udp
add action=log chain=output port=1701 protocol=udp
/ppp secret
add name=123 password=123
/system identity
set name=AC
L2TP client:

ros code

/interface l2tp-client
add connect-to=1.1.1.1 name=l2tp-out1 password=123 user=123
/ip address
add address=10.0.0.2/24 interface=ether5 network=10.0.0.0
/ip route
add distance=1 gateway=10.0.0.1
/system identity
set name=Client
L2TP will not establish. Looking at the logs will show that the L2TP server replies with a wrong IP address:
Image


Notes:
This is really annoying, especially if you have a public IP which the clients use to connect to the L2TP server on a loopback.
The lowest IP address of the incoming interface will still be used, instead of the public IP on the loopback, making the L2TP AC not work.

You can use NAT as a workaround.

ros code

/ip firewall nat
add action=dst-nat chain=dstnat comment="Fix for an L2TP src-address bug" dst-address="Address you want your L2TP client to connect to" \
 dst-port=1701 protocol=udp to-addresses="src-address that L2TP sends wrong packets with"
Support TicketID:
Ticket#2013020866000414
Last edited by tomaskir on Fri Jul 18, 2014 12:49 pm, edited 6 times in total.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Mon Dec 02, 2013 4:02 pm

All issues re-tested on v6.7 release. The list is now current for v6.7
2 out of 7 bugs on the list at the release of v6.7 were fixed.

The following issues from the list have been fixed in 6.7:

1) "/system leds" is not exported correctly
- http://forum.mikrotik.com/viewtopic.php ... 82#p395382
2) DNS cache does not update for static DNS name change
- http://forum.mikrotik.com/viewtopic.php ... 57#p396750
Last edited by tomaskir on Mon Dec 02, 2013 4:56 pm, edited 1 time in total.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
janisk
MikroTik Support
MikroTik Support
Posts: 6283
Joined: Tue Feb 14, 2006 9:46 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Mon Dec 02, 2013 4:45 pm

regarding this: http://forum.mikrotik.com/viewtopic.php ... 77#p395377
check if your 3g usb module is not hanging. In our testing we did not see any issues.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Mon Dec 02, 2013 4:57 pm

regarding this: http://forum.mikrotik.com/viewtopic.php ... 77#p395377
check if your 3g usb module is not hanging. In our testing we did not see any issues.
It could be specific to only the 2 USB modems I tested, however even if the modems are rebooted with usb-power-reset, the issue continues. (however, after a routerboard reboot, they work)
Also, a few other people in the forum reported problems.
A bit more info can be found here: http://forum.mikrotik.com/viewtopic.php?f=2&t=78593 (and my last post in that topic) or in the support ticket mentioned in the post in this topic.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Thu Dec 05, 2013 8:27 am

Known Issue in v6.7

Duplicate address-list entries (same list name and same address or address range) are causing a crash. Avoid making 2 identical entries, or write to support for v6.8rc1 pre-release version with the fix.

Thanks for your support, and keep sending emails to support if you find any problems.
No answer to your question? How to write posts
 
User avatar
vipe
Member Candidate
Member Candidate
Posts: 166
Joined: Thu Sep 14, 2006 10:05 pm

Re: Known issues and bugs - a list

Thu Dec 05, 2013 10:08 am

 
User avatar
honzam
Forum Guru
Forum Guru
Posts: 2292
Joined: Wed Feb 27, 2008 10:27 pm
Location: Czech Republic

Re: Known issues and bugs - a list

Thu Dec 05, 2013 10:48 am

Thanks for info Normis!!
LAN, FTTx, Wireless. ISP operator
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Thu Dec 05, 2013 11:33 am

Thank you for telling us Normis!

Added to the list.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
andriys
Forum Guru
Forum Guru
Posts: 1187
Joined: Thu Nov 24, 2011 1:59 pm
Location: Kharkiv, Ukraine

Re: Known issues and bugs - a list

Wed Dec 11, 2013 1:46 pm

Issue:
Only a single IPsec VPN client (road warrior) can connect from behind the same NAT.

Description:
Only a single IPsec client can connect to a given RouterOS based VPN concentrator from behind the same NAT device. Even though RouterOS has 'nat-traversal' option in '/ip ipsec peer' configuration, all this option does is it allows using ESP over UDP encapsulation mode. It seems that either IPsec policy processor does not take the client's UDP port number into account, or dynamic policy generator does not put client's UDP port number into the policy it generates, and thus RouterOS can not distinguish between two remote IPsec peers that are behind the same NAT device.

This type of configuration is standardized, is known to work on devices of different vendors, and is thus expected to be supported by the RouterOS as well.

Versions affected:
Tested with 6.6 and 6.7.

Support TicketID:
Ticket#2013120266000273.
Support replied on Dec 10, 2013 that "This setup is not possible with Road Warrior configuration, the router is unable to distinguish clients behind the same NAT."
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Wed Dec 11, 2013 3:31 pm

Issue:
Only a single IPsec VPN client (road warrior) can connect from behind the same NAT.
Sadly, this is not a bug, but rather a missing feature. Its hard to classify it as a bug, since its missing functionality, rather then something that should work, but doesnt.
You could even set generate-policy=port-strict or create a policy yourself with level=unique and it would still not work with multiple peers behind a single NAT.

MikroTik knows this doesnt work, hopefully the feature will be added.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
andriys
Forum Guru
Forum Guru
Posts: 1187
Joined: Thu Nov 24, 2011 1:59 pm
Location: Kharkiv, Ukraine

Re: Known issues and bugs - a list

Wed Dec 11, 2013 3:39 pm

Sadly, this is not a bug, but rather a missing feature.
Anyhow, people should know that IPsec NAT-T support is incomplete (or even broken) on RouterOS. To my knowledge, it has not been documented/mentioned anywhere till now. And for me it also means there's currently not a single viable mobile VPN option available on RouterOS, despite all the new and exciting IPsec features introduced in RouterOS v6. Sad.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Wed Dec 11, 2013 3:43 pm

Sadly, this is not a bug, but rather a missing feature.
Anyhow, people should know that IPsec NAT-T support is incomplete (or even broken) on RouterOS. To my knowledge, it has not been documented/mentioned anywhere till now. And for me it also means there's currently not a single viable mobile VPN option available on RouterOS, despite all the new and exciting IPsec features introduced in RouterOS v6. Sad.
I agree its a pain that its not working. As soon as we have a client that has multiple IPSec clients at the same location, we deploy a router and build a S2S tunnel, thats how we get over this particular problem.

Normis (or any other MikroTik staff), if you are reading this, should this be added into the list of known issues and considered a known issue?
Or is this a missing feature that should be requested in the feature request topic?
Last edited by tomaskir on Wed Dec 11, 2013 3:52 pm, edited 1 time in total.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
andriys
Forum Guru
Forum Guru
Posts: 1187
Joined: Thu Nov 24, 2011 1:59 pm
Location: Kharkiv, Ukraine

Re: Known issues and bugs - a list

Wed Dec 11, 2013 3:51 pm

As soon as we have a client that has multiple IPSec clients at the same location, we deploy a router and build a S2S tunnel, thats how we get over this particular problem.
I need this feature mostly for our employees who travel a lot and often need to access our office network during their business trips. If several travelers are staying in the same hotel at the same time, chances are they are behind the same NAT, and that's a huge problem. And, unfortunately, S2S is not a solution in this case at all.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Wed Dec 11, 2013 3:53 pm

As soon as we have a client that has multiple IPSec clients at the same location, we deploy a router and build a S2S tunnel, thats how we get over this particular problem.
I need this feature mostly for our employees who travel a lot and often need to access our office network during their business trips. If several travelers are staying in the same hotel at the same time, chances are they are behind the same NAT, and that's a huge problem. And, unfortunately, S2S is not a solution in this case at all.
Maybe allow usage of SSTP as a second option?
Of course, that is only viable if you OSs support SSTP.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
andriys
Forum Guru
Forum Guru
Posts: 1187
Joined: Thu Nov 24, 2011 1:59 pm
Location: Kharkiv, Ukraine

Re: Known issues and bugs - a list

Wed Dec 11, 2013 3:56 pm

Maybe allow usage of SSTP as a second option?
Of course, that is only viable if you OSs support SSTP.
Well, I have ASA5505 which handles similar scenarios just fine at the moment. Being able to use Mikrotik for similar tasks is very desirable, but does not seem to be possible, unfortunately.
 
User avatar
winet
Member Candidate
Member Candidate
Posts: 272
Joined: Fri Mar 16, 2007 4:49 pm
Location: Indonesia

Re: Known issues and bugs - a list

Thu Dec 12, 2013 3:13 am

Known Issue in v6.7

Duplicate address-list entries (same list name and same address or address range) are causing a crash. Avoid making 2 identical entries, or write to support for v6.8rc1 pre-release version with the fix.

Thanks for your support, and keep sending emails to support if you find any problems.
dynamic address-list or static address-list? it would be terrible for me to upgrade to v6.7 if the bug also meant for dynamic address-list, because i have port knock filter rules, which keeps re-adding dynamic address-list to keep alive an open connection.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8318
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: Known issues and bugs - a list

Fri Dec 13, 2013 3:21 pm

dynamic address-list or static address-list? it would be terrible for me to upgrade to v6.7 if the bug also meant for dynamic address-list, because i have port knock filter rules, which keeps re-adding dynamic address-list to keep alive an open connection.
firewall rules are not affected, as far as I saw
Russian-speaking forum: https://forum.mikrotik.by/. Welcome!

For every complex problem, there is a solution that is simple, neat, and wrong.

MikroTik. Your life. Your routing.
 
slech
Long time Member
Long time Member
Posts: 533
Joined: Thu Feb 14, 2008 4:03 pm
Location: Moldova, Chisinau

Re: Known issues and bugs - a list

Fri Dec 13, 2013 5:56 pm

Issue:
As patrickmkt mentioned, certificate can't be renamed via Winbox.

Description:
Certificat can't be renamed via Winbox. Now this can be done only via terminal:
certificate set numbers=0 name=certname
Versions affected:
Tested with 6.6, 6.7, 6.8 rc1(09.12.2013)

Support TicketID:
Ticket#2013120266000693
sorry for my english
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Mon Dec 16, 2013 4:06 pm

Issue:
As patrickmkt mentioned, certificate can't be renamed via Winbox.
EDIT: Verified, cant change the name in Winbox, only in Console.

Added to the list.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
Zod
Frequent Visitor
Frequent Visitor
Posts: 91
Joined: Mon Apr 23, 2012 11:02 pm

Re: Known issues and bugs - a list

Wed Jan 01, 2014 9:31 pm

 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Thu Jan 02, 2014 11:18 am

If you can please post the issue in the format outlined in the 2nd post, with steps on how to reliably replicate, that would be great.

Me and others can test and verify, and I will be glad to add it to the list.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
Rudios
Forum Veteran
Forum Veteran
Posts: 966
Joined: Mon Mar 11, 2013 12:58 pm
Location: The Netherlands

Re: Known issues and bugs - a list

Wed Jan 08, 2014 11:58 am

Issue:
DHCP over BCP

Description:
When BCP is used to tunnel over the internet between two devices and one of the devices is DHCP server, clients on the other side of the tunnel won't get IP address

Versions affected:
6.x

How to reproduce:
Connect two RB's

PPTP-server config

ros code

/interface pptp-server
add name=pptp-in-test user=test
/interface bridge
add l2mtu=1598 name=bridge1 protocol-mode=rstp
/ip pool
add name=pool ranges=192.168.88.101-192.168.88.150
/ip dhcp-server
add address-pool=pool disabled=no interface=bridge1 name=dhcp
/ppp profile
add bridge=bridge1 change-tcp-mss=yes name=ppp_bridging use-encryption=yes
/interface bridge port
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
/interface pptp-server server
set default-profile=ppp_bridging enabled=yes max-mru=1460 max-mtu=1460 mrru=1600
/ip address
add address=192.168.88.1/24 interface=bridge1 network=192.168.88.0
/ip dhcp-client
add dhcp-options=hostname,clientid disabled=no interface=ether1
/ip dhcp-server network
add address=192.168.88.0/24 dns-server=192.168.88.1 gateway=192.168.88.1
/ip dns
set allow-remote-requests=yes
/ip firewall nat
add action=masquerade chain=srcnat out-interface=ether1 to-addresses=0.0.0.0
/ppp secret
add name=test password=test service=pptp
PPTP-client config

ros code

/interface bridge
add l2mtu=1598 name=bridge1 protocol-mode=rstp
/ppp profile
add bridge=bridge1 change-tcp-mss=yes name=ppp_bridging use-encryption=yes
/interface pptp-client
add add-default-route=no allow=pap,chap,mschap1,mschap2 connect-to=\
    172.17.39.131 dial-on-demand=no disabled=no keepalive-timeout=60 max-mru=\
    1450 max-mtu=1450 mrru=1600 name=pptp-out-test password=test profile=\
    ppp_bridging user=test
/interface bridge port
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
/ip address
add address=192.168.88.2/24 interface=bridge1 network=192.168.88.0
/ip dhcp-client
add dhcp-options=hostname,clientid disabled=no interface=ether1
/ip firewall nat
add action=masquerade chain=srcnat out-interface=ether1 to-addresses=0.0.0.0
Notes:
MikroTik admitted this to be a bug and will be solved in a later version.
Their comment
Thanks, problem repeated.

Problem are specific to setups when DHCP-server is on the same bridge where pptp
is bridged.

we will fix that in one of the next versions.

Meanwhile you can ether place DHCP server on other device in the network, or use
EoIP over PPTP and bridge EOIP tunnel.
Support TicketID:
Ticket#2013120266000175
Testing setup with: 2 x RB750UP | 2 x RB750GL | 1 x RB951G-2HnD | 1 x RB2011UiAS-IN
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Wed Jan 08, 2014 12:23 pm

Issue:
DHCP over BCP
Excellent bug report, thank you!

Added to the list.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
mrscylla
just joined
Posts: 1
Joined: Mon Jan 27, 2014 11:08 pm

Re: Known issues and bugs - a list

Mon Jan 27, 2014 11:40 pm

Issue:
Web-proxy redirect-to

Description:
The colon symbol disappears from URL of redirect-to field.

Versions affected:
6.7

How to reproduce:

ros code

/ip proxy access add dst-port=80 dst-host=mail.mycompany.ru path="" action=deny redirect-to="https://mail.mycompany.ru/owa"
Notes:
Resulting URL becomes https//mail.mycompany.ru/owa

Support TicketID:
[Ticket#2014012766000763]
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Tue Jan 28, 2014 2:09 pm

2) SMS receiving stops working and cant be re-enabled
- http://forum.mikrotik.com/viewtopic.php ... 77#p395377
Author of this report is not responding to our emails, and we can't repeat it.
3) Source IP of web proxy can't be configured in WinBox and WebFig.
- http://forum.mikrotik.com/viewtopic.php ... 73#p396502
Should be fixed
4) PPTP/SSTP - could not add bridge port - BCP not working
- http://forum.mikrotik.com/viewtopic.php ... 95#p397295
fixed
5) L2TP Server bug - replies from wrong IP address
- http://forum.mikrotik.com/viewtopic.php ... 19#p398319
new ppp package invalidates this
6) Duplicate address-list entries (same list name and same address or address range) are causing a crash.
- http://forum.mikrotik.com/viewtopic.php ... 81#p398855
fixed
7) Certificates can't be renamed via Winbox.
- http://forum.mikrotik.com/viewtopic.php ... 16#p400112
fixed
No answer to your question? How to write posts
 
alexspils
Member Candidate
Member Candidate
Posts: 176
Joined: Thu Jun 05, 2008 8:57 pm

Re: Known issues and bugs - a list

Wed Jan 29, 2014 2:47 pm

is it known bugs?
1. x86.when moving vlan from ethernet interface which is in bonging to bonding interface router freazes? - It can be repeated on any x86 box with defaut config.Cant generate supout file because router freezes.
How to repeat:
/interface vlan add name=vlan1 vlan-id=1 interface=eth1
/interface vlan add name=vlan2 vlan-id=2 interface=eth1
.....
/interface bonding
add arp=enabled arp-interval=100ms arp-ip-targets="" disabled=no down-delay=\
0ms lacp-rate=1sec link-monitoring=mii-type2 mii-interval=100ms mode=\
802.3ad mtu=1500 name=bond1 primary=none slaves=eth1,eth2 \
transmit-hash-policy=layer-3-and-4 up-delay=0m
/interface vlan set vlan1 interface=bond1
after this command router freezes.

2. x86.after some time all subnets(in /ip address on interfaces - (in our case - vlans or bridges) gets status invalid. reboot solves problem.supout file sent, no answer from support.

3. x86+Intel i350 t4+6.x ethernet card dhcp not working-all users are with state offered.With wireshark we dont see any answer from dhcp server,with 5.x with same config all works.Answer from mikrotik:supout file sent.We will fix it sometime, use 5.x for now Ticket#20​1308286600​0867
Last edited by alexspils on Fri Jan 31, 2014 12:22 am, edited 3 times in total.
 
DjM
Member Candidate
Member Candidate
Posts: 111
Joined: Sun Dec 27, 2009 2:44 pm

Re: Known issues and bugs - a list

Thu Jan 30, 2014 2:05 pm

Issue:
Unable to initialite a system variable via SMS

Description:
It is not possible to initialite or change a system variable via SMS as it is described on:
http://wiki.mikrotik.com/wiki/Manual:Tools/Sms#Syntax
Bug is confirmed also by MikroTik, forum thread:
http://forum.mikrotik.com/viewtopic.php?f=9&t=58934

Versions affected:
4.x, 5.x, 6.x (including 6.9)

How to reproduce:
Send SMS in described format with any variable:
http://wiki.mikrotik.com/wiki/Manual:Tools/Sms#Syntax
System variable is not set or changed, so described feature is not working.

Notes:
There is no ETA from MikroTik support team to fix this issue.

Support TicketID:
Ticket#2012083066000462
Ticket#2013010766000731
Last edited by DjM on Mon Feb 03, 2014 9:21 pm, edited 1 time in total.
 
frankc
newbie
Posts: 25
Joined: Fri Oct 04, 2013 4:53 pm

Re: Known issues and bugs - a list

Fri Jan 31, 2014 2:45 am

another one in 6.7

add a static entry for

test.domain.com to any ip...

next add
test.domain.com to another ip

then try to remove first one...
you cant
you need to remove all, reput first one, disable, remove, and then add new one.. else it's like a ghost entry that will round robin with the new one ( flush cached and then still saw it as a Static
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Fri Jan 31, 2014 2:51 pm

I will update all the current issues and add the issues posted here as soon as 6.9 comes out.

Since 6.8 was pulled, I assume 6.9 will be released soon.

Thanks for all the bug fixes Normis!
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
lordzar
Frequent Visitor
Frequent Visitor
Posts: 67
Joined: Sat May 29, 2004 7:47 pm

Re: Known issues and bugs - a list

Fri Jan 31, 2014 5:18 pm

There is an issue where routeros can not talk to sshd servers that have challenge/response turned on.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Mon Feb 03, 2014 6:31 pm

All issues re-tested on v6.9 release. The list is now current for v6.9
4 out of 8 bugs on the list at the release of v6.9 were fixed.

The following issues from the list have been fixed in 6.9:

1) Source IP of web proxy can't be configured in WinBox and WebFig.
- http://forum.mikrotik.com/viewtopic.php ... 73#p396502
2) Duplicate address-list entries (same list name and same address or address range) are causing a crash.
- http://forum.mikrotik.com/viewtopic.php ... 81#p398855
3) Certificates can't be renamed via Winbox.
- http://forum.mikrotik.com/viewtopic.php ... 16#p400112
4) PPTP/SSTP - could not add bridge port - BCP not working
- http://forum.mikrotik.com/viewtopic.php ... 95#p397295
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Mon Feb 03, 2014 7:25 pm

This is a repost of an issue submitted by Rudios: http://forum.mikrotik.com/viewtopic.php ... 31#p402927
Reposted here with an easier to recreate configuration, to make re-testing with newer versions easier.

Issue:
DHCP over BCP does not work

Description:
When BCP is used to tunnel over the internet between two devices and one of the devices is DHCP server, clients on the other side of the tunnel won't get and IP address from the DHCP server.

Versions affected:
6.x

How to reproduce:
Connect three RB's in the following topology:
L2 connections:
 server        client      device
 ehter5 ------ ether5
               ether4------ether4
PPTP-server config:

ros code

/interface bridge
add name=bridge1 protocol-mode=rstp
/interface bridge port
add bridge=bridge1 interface=ether4
/ip address
add address=192.168.88.1/24 interface=bridge1
add address=10.0.0.1/24 interface=ether5
/ip pool
add name=DHCP_pool ranges=192.168.88.101-192.168.88.150
/ip dhcp-server
add address-pool=DHCP_pool disabled=no interface=bridge1 name=dhcp
/ip dhcp-server network
add address=192.168.88.0/24 gateway=192.168.88.1
/ppp profile
add bridge=bridge1 name=ppp_bridging
/interface pptp-server server
set default-profile=ppp_bridging enabled=yes max-mru=1400 max-mtu=1400
/ppp secret
add name=test password=test service=pptp
/interface pptp-server
add name=pptp-in-test user=test
PPTP-client config:

ros code

/interface bridge
add name=bridge1 protocol-mode=rstp
/interface bridge port
add bridge=bridge1 interface=ether4
/ip address
add address=192.168.88.2/24 interface=bridge1
add address=10.0.0.2/24 interface=ether5
/ppp profile
add bridge=bridge1 name=ppp_bridging
/interface pptp-client
add connect-to=10.0.0.1 disabled=no keepalive-timeout=10 max-mru=1400 max-mtu=1400 \
 name=pptp-out-test password=test profile=ppp_bridging user=test
DHCP client config:

ros code

/ip dhcp-client
add default-route-distance=0 dhcp-options=hostname,clientid disabled=no interface=ether4
Notes:
MikroTik confirmed this to be a bug that will be solved in a later version.
Thanks, problem repeated.

Problem are specific to setups when DHCP-server is on the same bridge where pptp
is bridged.

we will fix that in one of the next versions.

Meanwhile you can ether place DHCP server on other device in the network, or use
EoIP over PPTP and bridge EOIP tunnel.
Support TicketID:
Ticket#2013120266000175
Ticket#2014020466000625
Last edited by tomaskir on Tue Feb 04, 2014 4:29 pm, edited 1 time in total.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Tue Feb 04, 2014 2:34 pm

Issue:
Web-proxy redirect-to
I tested this on 6.9 and it seems to work, can you please provide more detail how to reproduce on 6.9?
Issue:
Unable to initialite a system variable via SMS
Added to the list, thanks!
2) SMS receiving stops working and cant be re-enabled
- http://forum.mikrotik.com/viewtopic.php ... 77#p395377
Author of this report is not responding to our emails, and we can't repeat it.
The support response got lost in all my emails, sorry, my fault :)
Will update the ticket asap with the requested info on 6.9
5) L2TP Server bug - replies from wrong IP address
- http://forum.mikrotik.com/viewtopic.php ... 19#p398319
new ppp package invalidates this
This issue is still present in 6.9 with the new ppp package, and can reliably be reproduced with the steps in the linked post.

Other than that, thanks for all the fixes!
Last edited by tomaskir on Tue Feb 04, 2014 3:47 pm, edited 2 times in total.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Tue Feb 04, 2014 2:36 pm

This was fixed in v6.8 as well. if anyone can repeat it, email support with full access, description and supout.rif file
No answer to your question? How to write posts
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Tue Feb 04, 2014 2:38 pm

This was fixed in v6.8 as well. if anyone can repeat it, email support with full access, description and supout.rif file
I will email support asap, can reproduce it with the steps in this post:
http://forum.mikrotik.com/viewtopic.php ... 50#p407146

Edit: sent with [Ticket#2014020466000625]
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
nz_monkey
Forum Guru
Forum Guru
Posts: 1821
Joined: Mon Jan 14, 2008 1:53 pm
Location: Straya
Contact:

Re: Known issues and bugs - a list

Mon Feb 17, 2014 4:14 am

Issue:
Export of BGP VRF configuration does not include the "instance" or "out-filter" entries.

Description:
When exporting the BGP VRF configuration with a "/routing bgp instance vrf export" the output does not include the relevant instance, or any out-filter that is configured. This prevents the user from being able to successfully import the configuration in to another router.

Versions affected:
Confirmed on 6.5 -> 6.10

How to reproduce:
Configure a BGP VRF with an out-filter then:

ros code

/routing bgp instance vrf export
The resulting output will not include the instance or out-filter

Notes:
This looks like RouterOS's configuration database is out of sync between Winbox/CLI and the actual underlying processes.
I worked with Mikrotik support and can confirm the "instance" problem is fixed in RouterOS 6.11 and the out-filter problem was not a problem, just confusion on our part.

Support TicketID:
Ticket#2014021766000093
http://thebrotherswisp.com/ | Mikrotik MTCNA, MTCRE, MTCINE | Fortinet FTCNA, FCNSP, FCT | Extreme Networks ENA
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Wed Feb 19, 2014 11:53 am

Issue:
Export of BGP VRF configuration does not include the "instance" or "out-filter" entries.
Thanks for the report! Added to the list.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
nz_monkey
Forum Guru
Forum Guru
Posts: 1821
Joined: Mon Jan 14, 2008 1:53 pm
Location: Straya
Contact:

Re: Known issues and bugs - a list

Wed Feb 19, 2014 2:13 pm

Issue:
During upgrade of RouterOS IPSEC peers become disabled

Description:
As above.

Versions affected:
Confirmed on 6.9 -> 6.11rc1

How to reproduce:
Upgrade from any release to 6.9, 6.10 or 6.11rc1 check your IPSEC peers after the upgrade and you will notice they are red :(
You can simply enable them and they will start working again.
We have confirmed this on a handful of mipsbe RouterBoards.

Notes:
This one made me laugh, it was just lucky I still allowed management access outside of the tunnel so I could re-enable the peers

Support TicketID:
Ticket# Not yet.
http://thebrotherswisp.com/ | Mikrotik MTCNA, MTCRE, MTCINE | Fortinet FTCNA, FCNSP, FCT | Extreme Networks ENA
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Fri Feb 21, 2014 10:29 am

Issue:
During upgrade of RouterOS IPSEC peers become disabled
Confirmed as well, and added to the list. This one could cause trouble even for me if I upgraded our IPSec AC.

Could you pls create a support ticket and update the post with it when you have the time

Thanks!
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
eldorin
just joined
Posts: 5
Joined: Thu Jun 06, 2013 4:03 am

Re: Known issues and bugs - a list

Fri Feb 21, 2014 2:48 pm

Have a Powerrouter 2200 upgraded from 5.24 to 6.10. Has a single peered interface with AT&T and a full ipv4 routing table with 475596 prefixes plus a full ipv6 routing table with 16374 prefixes.

The gig interface with AT&T is rate limited to only 250Mbit so it's not running much traffic. Averaging about 150Mbit on the unit for now.

Once upgraded to 6.10, I see about a 10% packetloss on the ptp interface to AT&T. Everything seems to be working fine on all other interfaces except the interface peered to the Internet backbone. Rolled back to 5.24 and everything works fine.
 
lordzar
Frequent Visitor
Frequent Visitor
Posts: 67
Joined: Sat May 29, 2004 7:47 pm

Re: Known issues and bugs - a list

Sat Feb 22, 2014 1:36 pm

Let's try this again... (Someone deleted my previous post)

I agree with everyone on "we're sick and tired of all the bugs".

They really need to hire someone who is experienced in software QA testing. It is beyond ridiculous now. Mikrotik seems to introduce just as many new bugs as the ones they fix in each release.

STOP introducing new hardware and start fixing ROS? You put out things like the cloud router and cloud switch, which should be awesome boxes, yet they are pretty much junk, since there is no good software to run on them.

And while we're on the subject, who makes a decision like, stop making the rb1100ah, which is totally capable of running metarouters, and not offering a replacement. I've even had an email from them lying about the ability of the x2 being able to run them.

I reported an issue in 6.7 about not being able to use ssh on a router to connect to a server that has challenge response turned on, and was told that it would be fixed "in the next release". Well, it's still not fixed in 6.10.

All I'm asking is please PLEASE stabilize the software and stop making new hardware. Find a experienced software QA person. Develop some good test plans and stop releasing buggy software, like the whole 6.8, 6.9, 6.10 fiasco.

I've been using mikrotik for over 10 years and have around 100 devices in the field, and yet I find myself on the verge of replacing them with some other vendors product.
 
elmer
newbie
Posts: 40
Joined: Mon Jun 18, 2012 4:02 pm

Re: Known issues and bugs - a list

Mon Feb 24, 2014 9:20 pm

RB951Ui from MUM - RouterOS 6.5, connected to internet and then...
/system package update upgrade
router rebooted, all is ok but PoE firmware = 0.0 ;)
Checked in the day of MUM on two routers, same effect...
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Tue Feb 25, 2014 11:54 am

RB951Ui from MUM - RouterOS 6.5, connected to internet and then...
/system package update upgrade
router rebooted, all is ok but PoE firmware = 0.0 ;)
Checked in the day of MUM on two routers, same effect...
what is the output of these two commands?

/interface ethernet poe settings print
/interface ethernet poe settings upgrade
No answer to your question? How to write posts
 
User avatar
Bergante
Member Candidate
Member Candidate
Posts: 131
Joined: Tue Feb 28, 2012 12:27 pm
Location: Bilbao, Spain

Re: Known issues and bugs - a list

Tue Feb 25, 2014 12:57 pm

Perfectly stable wireless link between two Omnitiks works perfectly with RoterOS <= 6.6.
The link is table, with CCR > 90 % most of the day.

After upgrading to 6.7, it begins to develop problems. Several days after the last reboot, packet loss appears. A reboot of just the one configured as an AP solves it. I tried again with the subsequent releases (6,8, 6,10) with the same results.

The problem seems to affect just the one in AP mode, it's the only one I have downgraded again to 6.6.

The network is, I admit, a bit convoluted (I am running MPLS and trying BGP-VPLS with several virtual networks) but the MPLS network has a total of three nodes and none of the others have shown any problems.

The wireless configuration of the AP one is:
[admin@OmniTik-despa] /interface wireless> export hide-sensitive 
# feb/25/2014 11:55:10 by RouterOS 6.6
# software id = 9SFF-0RWS
#
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
add authentication-types=wpa2-psk eap-methods="" management-protection=\
    required mode=dynamic-keys name=MAIN supplicant-identity=""
/interface wireless
set [ find default-name=wlan1 ] allow-sharedkey=yes band=5ghz-onlyn \
    basic-rates-a/g="" bridge-mode=disabled channel-width=20/40mhz-ht-below \
    disabled=no frequency=5680 frequency-mode=superchannel \
    ht-ampdu-priorities=0,1 ht-basic-mcs=mcs-0,mcs-1,mcs-2,mcs-3 ht-rxchains=\
    0,1 ht-supported-mcs=mcs-0,mcs-1,mcs-2,mcs-3,mcs-10,mcs-11,mcs-12,mcs-13 \
    ht-txchains=0,1 hw-retries=4 l2mtu=2290 max-station-count=2 mode=\
    ap-bridge mtu=1540 nv2-cell-radius=10 nv2-security=enabled \
    periodic-calibration=enabled preamble-mode=short rate-set=configured \
    security-profile=MAIN ssid=TRUNK supported-rates-a/g="" tdma-period-size=\
    3 tx-power=23 tx-power-mode=card-rates wireless-protocol=nv2 wmm-support=\
    enabled
/interface wireless access-list
add interface=wlan1 mac-address=00:0C:42:X:Y:Z

[admin@OmniTik-despa] /interface wireless> 
and, just for the record, the client:
[admin@OmniTik-casa] /interface wireless> export hide-sensitive 
# feb/25/2014 11:56:44 by RouterOS 6.10
# software id = PAXV-BRR1
#
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
add authentication-types=wpa2-psk management-protection=required mode=\
    dynamic-keys name=MAIN supplicant-identity=""
/interface wireless
set [ find default-name=wlan1 ] band=5ghz-a/n bridge-mode=disabled \
    channel-width=20/40mhz-ht-below disabled=no frequency-mode=superchannel \
    ht-ampdu-priorities=0,1 ht-guard-interval=long hw-retries=1 l2mtu=2290 \
    mtu=1540 noise-floor-threshold=-105 nv2-cell-radius=10 nv2-security=\
    enabled periodic-calibration=enabled preamble-mode=short scan-list=\
    5580,5680,5660,5700,5540,5180,5200,5220 security-profile=MAIN ssid=TRUNK \
    tx-power=23 tx-power-mode=card-rates wireless-protocol=nv2 wmm-support=\
    enabled
The link is just crossing a street, nothing fancy, and both units are behind windows, not perfect line of sight. But with 6.6 on the "AP" it works rock solid.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Wed Feb 26, 2014 1:00 pm

All issues retested on v6.10.

No fixes or changes compared to v6.9, since v6.10 was just a quick fix released a few days after v6.9.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
Leto
just joined
Posts: 16
Joined: Wed Aug 10, 2011 9:25 pm

Re: Known issues and bugs - a list

Wed Feb 26, 2014 2:18 pm

Please fix this bug:
http://forum.mikrotik.com/viewtopic.php?f=14&t=79519

Decription:
IPv6 over PPPoE stops working after PPPoE connection disconnect.

To fix you have to disable/enable ipv6 address and then release/renew dhcpv6 client.

Here is video of problem (not made by me)
http://www.youtube.com/watch?v=6Mo1HN4y ... e=youtu.be

Issue is same as in video, but with 6.10 it changed so that additional step is required (releasing/renewing dhcpv6)

Versions affected: 6.x
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Wed Feb 26, 2014 2:37 pm

Please fix this bug:
http://forum.mikrotik.com/viewtopic.php?f=14&t=79519

Decription:
IPv6 over PPPoE stops working after PPPoE connection disconnect.

To fix you have to disable/enable ipv6 address and then release/renew dhcpv6 client.

Here is video of problem (not made by me)
http://www.youtube.com/watch?v=6Mo1HN4y ... e=youtu.be

Issue is same as in video, but with 6.10 it changed so that additional step is required (releasing/renewing dhcpv6)

Versions affected: 6.x
I will try to simulate this problem and create a proper reliable step-by-step process on how to reproduce it.

If i succeed, I will create a support ticket and post it here as a known issue.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
Leto
just joined
Posts: 16
Joined: Wed Aug 10, 2011 9:25 pm

Re: Known issues and bugs - a list

Wed Feb 26, 2014 2:57 pm

Thank you!

Here's the config I am using (it's in Slovenian), if it's any help:

http://go6.si/2013/12/mikrotik-usmerjev ... eko-pppoe/

http://translate.google.com/translate?s ... o-pppoe%2F
 
facetwety
just joined
Posts: 7
Joined: Tue Feb 25, 2014 4:49 pm

bad blocks problem

Thu Feb 27, 2014 12:50 pm

Issue:
bad blocks problem

Description:
I've got a anew rb 433ah with ros ver:6.5 And everything was just fine
but after upgrade to ros ver:6.10 bad blocks counter start raising almost every reboot by .1% and now its 2.3%
so i downgrade the ros version to 6.4 and the bad blocks counter is now stable at 2.3% and not raise up.


Versions affected:
ver:6.10


How to reproduce:
updating router board to lateset ros ver 6.10 and bad block counter start raise by .1% Almost every reboot or power shutdown

Notes:
nand model st
ram model zentel


Support TicketID:
Ticket#2014022766000038]

http://forum.mikrotik.com/viewtopic.php?t=82299
Image
Last edited by facetwety on Thu Feb 27, 2014 12:57 pm, edited 1 time in total.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: bad blocks problem

Thu Feb 27, 2014 12:55 pm

Issue:
bad blocks problem
I tested on a RB750 and a RB951-2n, but it does not happen for me, I dont have a 433ah I can test on.

Do you have a different 433ah you can test on to make sure its not just that one board that presents the problem?
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Thu Feb 27, 2014 12:56 pm

You can actually see in your picture, that you have v6.4, so why do you write that this only happens in v6.10?
No answer to your question? How to write posts
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Thu Feb 27, 2014 12:59 pm

You can actually see in your picture, that you have v6.4, so why do you write that this only happens in v6.10?
He did say he had to downgrade to 6.4.

So he upgraded to 6.10, bad blocks started increasing.
He downgraded to 6.4, bad blocks dont increase anymore.
He is now at 6.4, with 2,3% bad blocks still left.

Atleast thats how I understand his problem :)
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
facetwety
just joined
Posts: 7
Joined: Tue Feb 25, 2014 4:49 pm

Re: Known issues and bugs - a list

Thu Feb 27, 2014 1:07 pm

You can actually see in your picture, that you have v6.4, so why do you write that this only happens in v6.10?
upgraded to 6.10, bad blocks started increasing.
downgraded to 6.4, bad blocks dont increase anymore.
now at 6.4, with 2,3% bad blocks still left.

trying to reinstall with net install with no luck still 2.3%


tomaskir :wink:
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Thu Feb 27, 2014 1:21 pm

trying to reinstall with net install with no luck still 2.3%
Could you please check on another 433ah as I mentioned in here http://forum.mikrotik.com/viewtopic.php ... 50#p411879?

Thanks!
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
facetwety
just joined
Posts: 7
Joined: Tue Feb 25, 2014 4:49 pm

Re: Known issues and bugs - a list

Thu Feb 27, 2014 1:34 pm

Could you please check on another 433ah as I mentioned in here http://forum.mikrotik.com/viewtopic.php ... 50#p411879?

Thanks!
Unfortunately I do not have any other 433ah rb

may be this problem happen to 433ah with st nand only !!!!!!!!
 
HeadCraft
just joined
Posts: 16
Joined: Tue Mar 05, 2013 11:11 am

Re: Known issues and bugs - a list

Thu Feb 27, 2014 3:05 pm

Issue:
Wrong behaivor of SNMP TRAP generator

Description:
In SNMP configuration options there is parameter which means "List of interfaces that traps are going to be sent out"

ros code

/snmp set trap-interfaces=ether1
But it does no effect when sending trap to a subnet, that belongs to another interface. The packet is generated with source address of that "another" interface.

Versions affected:
Tested on 5.6, 5.25, 6.7, 6.10

How to reproduce:

Lets say we have two routers connected with vpn tunnel (10.0.0.0/30) and each of them has local subnet (192.168.0.0/24 on R1, 192.168.1.0/24 on R2) and server connected to router2 which catches traps.
       10.0.0.1            10.0.0.2
  Router1 --------(vpn)------------Router2
  (ether1)                        (ether1)
      |                              |
      |                              |
      |                              |
192.168.0.1                     192.168.1.1
Configuration on Router1

ros code

/ip address add interface=vpn address=10.0.0.1/30
/ip address add interface=ether1 address=192.168.0.1/24
/ip route add gateway=10.0.0.2
/snmp set enabled=yes trap-community=public trap-generators=interfaces,start-trap \
trap-interfaces=ether1 trap-target=192.168.1.2
Configuration on Router2

ros code

/ip address add interface=vpn address=10.0.0.2/30
/ip address add interface=ether1 address=192.168.1.1/24
/ip route add gateway=10.0.0.1
/ip firewall filter add chain=forward comment="Block traffic generated in VPN subnet for security reason" \
in-interface=vpn out-interface=ether1 src-address=10.0.0.0/30 action=drop
So when trap will be generated, server will not recieve it. It will be blocked by firewall because it has source ip address 10.0.0.1, but we need 192.168.0.1.

Notes:

Here is a lack of parameter like "/snmp set trap-source-address=".
We can see how it is made in remote syslog config

ros code

/system logging action
set 3 bsd-syslog=no name=remote remote=192.168.1.2 remote-port=514 src-address=\
    192.168.0.1 syslog-facility=daemon syslog-severity=auto target=remote
Support TicketID:

Ticket#2014022766000752
Last edited by HeadCraft on Mon Mar 03, 2014 8:33 am, edited 1 time in total.
 
IlCarletto
newbie
Posts: 30
Joined: Mon May 10, 2010 3:09 pm
Location: Milan
Contact:

Re: Known issues and bugs - a list

Fri Feb 28, 2014 11:25 am

request:
write a domain name for a remote syslog server, like this (attach)
You do not have the required permissions to view the files attached to this post.
RB433 / R52n + R52n-M - 6.10rc
 
Rudios
Forum Veteran
Forum Veteran
Posts: 966
Joined: Mon Mar 11, 2013 12:58 pm
Location: The Netherlands

Re: Known issues and bugs - a list

Thu Mar 06, 2014 8:35 am

This was fixed in v6.8 as well. if anyone can repeat it, email support with full access, description and supout.rif file
I will email support asap, can reproduce it with the steps in this post:
http://forum.mikrotik.com/viewtopic.php ... 50#p407146

Edit: sent with [Ticket#2014020466000625]
I have tested it with both versions 6.9 and 6.10 but the problem is still there!!!
Testing setup with: 2 x RB750UP | 2 x RB750GL | 1 x RB951G-2HnD | 1 x RB2011UiAS-IN
 
Poki
just joined
Posts: 11
Joined: Thu Jul 26, 2012 3:42 pm

Re: Known issues and bugs - a list

Thu Mar 06, 2014 10:46 am

Hello Mikrotik community.

I guess it's my turn to report a bug.

Issue:
Router always looks in the main table when it has to send ICMP TTL exceeded in transit (type 11)

Description:
As you know, when a packet pass through a router, the TTL is decreased by 1, and when it reaches 0, the router should send ICMP type 11 (TTL exceeded in transit) back to the sender.

However, if that happens to be in a VRF (incoming and outgoing interfaces belong to a specific routing-mark), the router would not look into the corresponding table to send back the ICMP type 11 packet.

It seems that the router is always looking in the main table, no matter what.

Versions affected:
6.10, 6.6, (I guess 6.x)

How to reproduce:

Physical setup:
PC <--> RB <--> PC

Config of the RB:

ros code

/ip address
add address=10.0.0.1/30 interface=ether2 network=10.0.0.0
add address=10.2.0.1/30 interface=ether4 network=10.2.0.0
/ip route vrf
add interfaces=ether2,ether4 routing-mark=vrf1
When a PC with IP address 10.0.0.2 run a traceroute towards 10.2.0.2, the router (first hop) just won't show up.

C:\Users\Poki>tracert -d 10.2.0.2

Tracing route to 10.2.0.2 over a maximum of 30 hops

1 * * * Request timed out.
2 2 ms 1 ms 2 ms 10.2.0.2

Trace complete.

When I disable the VRF, everything is OK.

Notes:
It seems that the router looks only in the main table.

When I use VRF and if I just insert a static route for 10.0.0.0/30 on the ether2 interface in the main table, the router starts to send back the TTL exceeded packets.

The problem is not present on RouterOS 5.26.

Support TicketID:
2014030666000236 - no reply from them yet.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Thu Mar 06, 2014 11:39 am

Issue:
Router always looks in the main table when it has to send ICMP TTL exceeded in transit (type 11)
Tested and confirmed, added to the list.

Thanks!
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Thu Mar 06, 2014 12:43 pm

Issue:
Wrong behaivor of SNMP TRAP generator

Description:
In SNMP configuration options there is parameter which means "List of interfaces that traps are going to be sent out"

ros code

/snmp set trap-interfaces=ether1
But it does no effect when sending trap to a subnet, that belongs to another interface. The packet is generated with source address of that "another" interface.
I took me a bit to understand and simulate your issue, I have a few quesions:

Your problem is that the SNMP trap for an interface is not send from the source-IP of the interface yes?
If so, what is the problem with all the traps from the router being send from a single IP address? You can just allow that single IP to communicate with the SNMP manager. If every interface were to send traps from its IP-address, that would be difficult.
What about PPP interfaces, or interfaces with a DHCP client?

I think the current behaviour is correct, but please do explain more why its not for you, and why you think it should be different.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
MT7
just joined
Posts: 13
Joined: Sun Dec 15, 2013 2:55 pm

Re: Known issues and bugs - a list

Sun Mar 09, 2014 7:40 pm

Hardware: RB2011UAS-2HnD-IN

Firmware: 3.12

RouterOS: 6.10

Problem description: Sometimes the igmp-proxy on my router seems stop working suddenly. When it happens LAN users can't watch IPTV. If I check the igmp-proxy window via winbox it became clean with no rules in it. To correct this problem I have to reboot the router. After reboot all settings in the igmp-proxy window are back and IPTV is back too.

Steps to reproduce: No idea. It is just happened several times per 6 months without any actions from my side.
/routing igmp-proxy
set quick-leave=yes
/routing igmp-proxy interface
add alternative-subnets=10.0.0.0/8 interface=ether2 upstream=yes
add interface=ether7
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Mon Mar 10, 2014 3:08 pm

This is a repost of an issue submitted by Poki: http://forum.mikrotik.com/viewtopic.php ... 00#p413242
Reposted here with an easier to recreate configuration, to make re-testing with newer versions easier.

Issue:
Router looks in the main routing table and not in a VRF for ICMP TTL exceeded (type 11)

Description:
When a packet pass through a router, the TTL is decreased by 1, and when it reaches 0, the router should send ICMP type 11 (TTL exceeded in transit) back to the sender.
However, if that happens to be in a VRF (incoming and outgoing interfaces belong to a specific routing-mark), the router would not look into the corresponding table to send back the ICMP type 11 packet.

It seems that the router is always looking in the main table, no matter what.

Versions affected:
Not working in 6.x
Working in 5.x

How to reproduce:
L2 connections:
 Client1     VRF_Router    Client2
 ehter4 ------ ether4
               ether5------ether5
Config on VRF_Router:

ros code

/ip address
add address=10.0.0.1/30 interface=ether4 network=10.0.0.0
add address=10.2.0.1/30 interface=ether5 network=10.2.0.0
/ip route vrf
add interfaces=ether4,ether5 routing-mark=vrf1
/system identity
set name=VRF_Router
Config on Client1:

ros code

/ip address
add address=10.0.0.2/30 interface=ether4 network=10.0.0.0
/ip route
add distance=1 gateway=10.0.0.1
/system identity
set name=Client1
Config on Client2:

ros code

/ip address
add address=10.2.0.2/30 interface=ether5 network=10.2.0.0
/ip route
add distance=1 gateway=10.2.0.1
/system identity
set name=Client2
Run a trace from Client2 to Client1:
[admin@Client2] > tool traceroute 10.0.0.2
 # ADDRESS                          LOSS SENT    LAST     AVG    BEST   WORST STD-DEV STATUS
 1                                  100%    5 timeout
 2 10.0.0.2                           0%    4   2.4ms     2.1     1.9     2.4     0.2
You will see VRF_Router is not properly sending ICMP TTL exceeded.
If you disable the VRF, everything is OK.

Notes:
It seems that the router looks only in the main table.
When I use VRF and if I just insert a static route for 10.0.0.0/30 on the ether2 interface in the main table, the router starts to send back the TTL exceeded packets.

The problem is not present on RouterOS 5.26

Support TicketID:
2014030666000236
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
Poki
just joined
Posts: 11
Joined: Thu Jul 26, 2012 3:42 pm

Re: Known issues and bugs - a list

Mon Mar 10, 2014 7:53 pm

This is a repost of an issue submitted by Poki: http://forum.mikrotik.com/viewtopic.php ... 00#p413242
Reposted here with an easier to recreate configuration, to make re-testing with newer versions easier.

Issue:
Router looks in the main routing table and not in a VRF for ICMP TTL exceeded (type 11)

Support TicketID:
2014030666000236
Well summarized tomaskir.

I just wanted to mention that I still don't have a reply from Mikrotik about this issue.

It's a shame. Instead of being grateful about helping them improve their OS, they don't even bother to consider our bug reports.
 
janel
just joined
Posts: 11
Joined: Wed Mar 12, 2014 10:41 pm

Re: Known issues and bugs - a list

Wed Mar 12, 2014 10:58 pm

Issue:
CRS125-24G-1S-RM: Configuration elements missing from the Web interface: Switch and LCD

Description:
The configuration sections for the Switch and LCD are missing from the Web interface, but present in the CLI and Winbox.

Versions affected:
6.10

How to reproduce:
Always
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Thu Mar 13, 2014 11:39 am

This is a repost of an issue submitted by Poki: http://forum.mikrotik.com/viewtopic.php ... 00#p413242
Reposted here with an easier to recreate configuration, to make re-testing with newer versions easier.

Issue:
Router looks in the main routing table and not in a VRF for ICMP TTL exceeded (type 11)

Support TicketID:
2014030666000236
Well summarized tomaskir.

I just wanted to mention that I still don't have a reply from Mikrotik about this issue.

It's a shame. Instead of being grateful about helping them improve their OS, they don't even bother to consider our bug reports.
Your bug is still open, and is being investigated. Sorry if that wasn't clear. We answer ALL emails. If you didn't get an answer, either it's in your junk folder, or we are still looking into it.
No answer to your question? How to write posts
 
DjM
Member Candidate
Member Candidate
Posts: 111
Joined: Sun Dec 27, 2009 2:44 pm

Re: Known issues and bugs - a list

Thu Mar 13, 2014 12:17 pm

Your bug is still open, and is being investigated. Sorry if that wasn't clear. We answer ALL emails. If you didn't get an answer, either it's in your junk folder, or we are still looking into it.
Hi normis,

I think that "Thank you, we are working on it, update is awaited in next XX days" is better answer than waiting without reply :-)
One email can make a better picture, I think ;-)
 
Rudios
Forum Veteran
Forum Veteran
Posts: 966
Joined: Mon Mar 11, 2013 12:58 pm
Location: The Netherlands

Re: Known issues and bugs - a list

Thu Mar 13, 2014 1:28 pm

...
...
... We answer ALL emails. If you didn't get an answer, either it's in your junk folder, or we are still looking into it.
Normis. How sure are you about this. I have send an email the 6th about DHCP over BCP
Ticket#2013120266000175

I have not received any response yet.
Testing setup with: 2 x RB750UP | 2 x RB750GL | 1 x RB951G-2HnD | 1 x RB2011UiAS-IN
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Thu Mar 13, 2014 1:30 pm

Ticket#2013120266000175

I have not received any response yet.
In this case you have responded with an update to a 101 days old ticket, which means it gets buried in the priority list. I suggest making a new ticket when you have a new problem.
No answer to your question? How to write posts
 
Rudios
Forum Veteran
Forum Veteran
Posts: 966
Joined: Mon Mar 11, 2013 12:58 pm
Location: The Netherlands

Re: Known issues and bugs - a list

Thu Mar 13, 2014 8:16 pm

Ticket#2013120266000175

I have not received any response yet.
In this case you have responded with an update to a 101 days old ticket, which means it gets buried in the priority list. I suggest making a new ticket when you have a new problem.
But it is not a new problem. You stated it should be solved in version 6.8 but I can still reproduce it in 6.9 and 6.10
Testing setup with: 2 x RB750UP | 2 x RB750GL | 1 x RB951G-2HnD | 1 x RB2011UiAS-IN
 
janel
just joined
Posts: 11
Joined: Wed Mar 12, 2014 10:41 pm

Re: Known issues and bugs - a list

Fri Mar 14, 2014 1:37 am

Issue:
CRS125-24G-1S-RM: Configuration elements missing from the Web interface: Switch and LCD

Description:
Switch setting bridge-type=customer-vlan-bridge is not retained after reboot.
In my case this causes traffic to be copied on all ports linked to the current master, as described before by other users.
/interface ethernet switch port set [find] learn-restricted-unknown-sa=yes
does not work, setting instead
/interface ethernet switch set bridge-type=customer-vlan-bridge
is OK.
In my setup, when the configuration is wrong traffic drops from ~700Mbs to ~120Mbs.

My config:
/interface ethernet
set [ find default-name=sfp1 ] auto-negotiation=no
set [ find default-name=ether1 ] master-port=sfp1
set [ find default-name=ether2 ] master-port=sfp1
set [ find default-name=ether3 ] master-port=sfp1
/interface vlan
add interface=sfp1 l2mtu=1584 name=vlan199 vlan-id=199
/interface ethernet switch
set bridge-type=customer-vlan-bridge
/interface ethernet switch egress-vlan-translation
add customer-vid=199 new-customer-vid=0 port=ether1
add customer-vid=199 new-customer-vid=0 port=ether2
add customer-vid=199 new-customer-vid=0 port=ether3
/interface ethernet switch ingress-vlan-translation
add customer-vid=0 new-customer-vid=199 port=ether1 sa-learning=yes
add customer-vid=0 new-customer-vid=199 port=ether2 sa-learning=yes
add customer-vid=0 new-customer-vid=199 port=ether3 sa-learning=yes
Versions affected:
6.10

How to reproduce:
Set switch bridge type = customer-vlan-bridge then reboot
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Fri Mar 14, 2014 11:35 am

Issue:
CRS125-24G-1S-RM: Configuration elements missing from the Web interface: Switch and LCD
Issue:
CRS125-24G-1S-RM: Switch setting bridge-type=customer-vlan-bridge is not retained after reboot.
I dont have a CRS to test with, could anyone please confirm these?
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Fri Mar 14, 2014 11:41 am

6) Export of BGP VRF configuration does not include the "instance" entries
- viewtopic.php?f=2&t=78816&start=50#p409634
Fixed in v6.11
7) During upgrade of RouterOS IPSEC peers become disabled
- viewtopic.php?f=2&t=78816&start=50#p410240
Marked invalid, since we can't repeat this in any type of setup. Could be a problem with something else in this system/network
No answer to your question? How to write posts
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Fri Mar 14, 2014 11:46 am

7) During upgrade of RouterOS IPSEC peers become disabled
- viewtopic.php?f=2&t=78816&start=50#p410240
Marked invalid, since we can't repeat this in any type of setup. Could be a problem with something else in this system/network
I have tried to replicate this issue for 2 hours without success as well.

I have seen multiple people on the forums say they have this issue, but noone responds to my emails/messages.
nz_monkey is not responding either, nz_monkey, if you are reading this, please contact me :)

For now, removed from the list.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Fri Mar 14, 2014 11:46 am

4) DHCP over BCP does not work
- viewtopic.php?f=2&t=78816&p=407146#p407146
fixed in 6.11
No answer to your question? How to write posts
 
swissiws
Member Candidate
Member Candidate
Posts: 105
Joined: Sat Apr 04, 2009 12:42 am

Re: Known issues and bugs - a list

Fri Mar 14, 2014 12:46 pm

tomaskir

I am not an engineer - i am a project manager feeding of your trail - just spend another 10k on MT products which seems not to work due to already published sw bugs with crs and ccr systems - NO doubt about hardware engineering - first class - software too unpredictable to manage, maybe a bug, maybe engineer issue -

spend another 2k of engineer work to get basic vlan configuration running on CRS - well 4 days into production - user complain re speed issues etc = see posts. ros 6.10


I hope you see my current frustrations re Mikrotik products getting released without proper product certification - CRS as my main concern. CCR does not bond with Cisco as many times posted before.
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Fri Mar 14, 2014 12:57 pm

tomaskir

I am not an engineer - i am a project manager feeding of your trail - just spend another 10k on MT products which seems not to work due to already published sw bugs with crs and ccr systems - NO doubt about hardware engineering - first class - software too unpredictable to manage, maybe a bug, maybe engineer issue -

spend another 2k of engineer work to get basic vlan configuration running on CRS - well 4 days into production - user complain re speed issues etc = see posts. ros 6.10


I hope you see my current frustrations re Mikrotik products getting released without proper product certification - CRS as my main concern. CCR does not bond with Cisco as many times posted before.
If you assume that there are bugs only by reading the forum release topic, I can disappoint you, 90% of those reports are caused by user error, or appear only in very specific situations that most likely will never affect you. Do you actually have any problems yourself, and if yes, tell us the Support ticket number, so I can check if we have fixed it for v6.11
No answer to your question? How to write posts
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Fri Mar 14, 2014 2:01 pm

tomaskir

I am not an engineer - i am a project manager feeding of your trail - just spend another 10k on MT products which seems not to work due to already published sw bugs with crs and ccr systems - NO doubt about hardware engineering - first class - software too unpredictable to manage, maybe a bug, maybe engineer issue -

spend another 2k of engineer work to get basic vlan configuration running on CRS - well 4 days into production - user complain re speed issues etc = see posts. ros 6.10


I hope you see my current frustrations re Mikrotik products getting released without proper product certification - CRS as my main concern. CCR does not bond with Cisco as many times posted before.
I understand your concerns as a project manager. What I would advise is telling your engineers to actually contact official Mikrotik support.
What Normis said is true, most of the so-called "bugs" in release threads are actually config errors.

Tell your engineers not to "blame" problems on posts in the release thread, but to actually work on solving the issues. Support will tell them if its a config issue or a bug.
Without your problem being confirmed as a bug by official MikroTik support, you cant do much. When it is confirmed as a bug by official MikroTik support, then you can push on MikroTik to fix it.
Also if that is the case, please post it in here so we all know about the issue :)

Believe me, I understand the frustration, some of the bugs in here are affecting our systems as well.
But as you can see from this thread, MikroTik is actually solving bugs (of course, at their own pace, and according to their own priorities).
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
NathanA
Forum Veteran
Forum Veteran
Posts: 801
Joined: Tue Aug 03, 2004 9:01 am

Re: Known issues and bugs - a list

Sun Mar 16, 2014 2:00 am

4) DHCP over BCP does not work
- viewtopic.php?f=2&t=78816&p=407146#p407146
fixed in 6.11
Yay! I should have read the forums first...I just submitted a ticket (#2014031566000139) about this very issue yesterday!

Please don't ignore the ticket, though, even though this issue is fixed...I reported a second issue in the same ticket, where you can hard-crash an x86 RouterOS box running PPTP or L2TP server if the incoming request negotiates both MPPE encryption and MLPPP MRRU, if you are using the SMP/multicore kernel.

-- Nathan
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Sun Mar 16, 2014 11:54 am

Please don't ignore the ticket, though, even though this issue is fixed...I reported a second issue in the same ticket, where you can hard-crash an x86 RouterOS box running PPTP or L2TP server if the incoming request negotiates both MPPE encryption and MLPPP MRRU, if you are using the SMP/multicore kernel.

-- Nathan
That is fixed in 6.11 as well:

From 6.11 RC devel log:

What's new in 6.11 (2014-Mar-14 10:13):
*) ppp - mppe encryption together with mrru locked the router;
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
Rudios
Forum Veteran
Forum Veteran
Posts: 966
Joined: Mon Mar 11, 2013 12:58 pm
Location: The Netherlands

Re: Known issues and bugs - a list

Sun Mar 16, 2014 3:51 pm

Please don't ignore the ticket, though, even though this issue is fixed...I reported a second issue in the same ticket, where you can hard-crash an x86 RouterOS box running PPTP or L2TP server if the incoming request negotiates both MPPE encryption and MLPPP MRRU, if you are using the SMP/multicore kernel.

-- Nathan
That is fixed in 6.11 as well:

From 6.11 RC devel log:

What's new in 6.11 (2014-Mar-14 10:13):
*) ppp - mppe encryption together with mrru locked the router;
How come I can not find ROS 6.11 on the official download page?
Testing setup with: 2 x RB750UP | 2 x RB750GL | 1 x RB951G-2HnD | 1 x RB2011UiAS-IN
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Sun Mar 16, 2014 3:53 pm

How come I can not find ROS 6.11 on the official download page?
The excerpt was from the 6.11 release candidate development page.

6.11 is not officially released yet.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
nz_monkey
Forum Guru
Forum Guru
Posts: 1821
Joined: Mon Jan 14, 2008 1:53 pm
Location: Straya
Contact:

Re: Known issues and bugs - a list

Mon Mar 17, 2014 3:57 am

nz_monkey is not responding either, nz_monkey, if you are reading this, please contact me :)
Sorry tomaskir had work overload the last few weeks.

I will do some more testing on this tonight and try to determine if it is a general fault or something specific to my configuration.
http://thebrotherswisp.com/ | Mikrotik MTCNA, MTCRE, MTCINE | Fortinet FTCNA, FCNSP, FCT | Extreme Networks ENA
 
Rudios
Forum Veteran
Forum Veteran
Posts: 966
Joined: Mon Mar 11, 2013 12:58 pm
Location: The Netherlands

Re: Known issues and bugs - a list

Fri Mar 21, 2014 12:21 pm

4) DHCP over BCP does not work
- viewtopic.php?f=2&t=78816&p=407146#p407146
fixed in 6.11
I can confirm that the bug is solved. Just tested it!
Testing setup with: 2 x RB750UP | 2 x RB750GL | 1 x RB951G-2HnD | 1 x RB2011UiAS-IN
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Tue Mar 25, 2014 5:22 pm

All issues re-tested on v6.11 release. The list is now current for v6.11
2 out of 7 bugs on the list at the release of v6.11 were fixed.

The following issues from the list have been fixed in 6.11:
4) DHCP over BCP does not work
- http://forum.mikrotik.com/viewtopic.php ... 46#p407146
6) Export of BGP VRF configuration does not include the "instance" entries
- http://forum.mikrotik.com/viewtopic.php ... 50#p409634
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Wed Mar 26, 2014 7:09 pm

Issue:
Queue type default-small not exported with export compact

Description:
When doing a "export compact" changes to queue type default-small are not exported

Versions affected:
6.x and 5.x

How to reproduce:
Simply put this into console to see it not export:

ros code

/queue type print where name=default-small
# Notice the default pfifo-limit=10
/queue type set [/queue type find name=default-small] pfifo-limit=50
# Now we change that to 50
/queue type export compact
# Our changes are not in export compact
/queue type print where name=default-small
# Notice the pfifo-limit=50
Notes:
After 15 (?) versions, export compact is still missing things.
Wonder how many more settings are still not exported correctly...

Support TicketID:
[Ticket#2014032666000958]
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
asmozre
just joined
Posts: 7
Joined: Sun Jan 22, 2012 1:40 am

Re: Known issues and bugs - a list

Wed Mar 26, 2014 8:12 pm

Unable to change or add any telnet interfaces into mac-server

Model: CCR1036-12G-4S

ROS Version 6.11
/tool mac-server
remove 0
failure: can not remove the default entry
add interface=ether2
failure: interface unsupported
I have 6.10 on another device that is not a CCR and am able to use these commands with no issue.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8318
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: Known issues and bugs - a list

Wed Mar 26, 2014 10:52 pm

Description:
When doing a "export compact" changes to queue type default-small are not exported
for me (v6.11, x86) it's exported, but in strange manner: "set 16 pfifo-limit=20". I don't think that default-small has index 16 on every system :)
Unable to change or add any telnet interfaces into mac-server

Model: CCR1036-12G-4S

ROS Version 6.11
/tool mac-server
remove 0
failure: can not remove the default entry
add interface=ether2
failure: interface unsupported
I have 6.10 on another device that is not a CCR and am able to use these commands with no issue.
have you tried v6.10 on CCR? adding works for me both in 6.10 CCR and 6.11 x86
also, removing should not work on any device, just because it's default entry. you should be able only disable it, not remove
Russian-speaking forum: https://forum.mikrotik.by/. Welcome!

For every complex problem, there is a solution that is simple, neat, and wrong.

MikroTik. Your life. Your routing.
 
asmozre
just joined
Posts: 7
Joined: Sun Jan 22, 2012 1:40 am

Re: Known issues and bugs - a list

Wed Mar 26, 2014 11:05 pm

Description:
When doing a "export compact" changes to queue type default-small are not exported
for me (v6.11, x86) it's exported, but in strange manner: "set 16 pfifo-limit=20". I don't think that default-small has index 16 on every system :)
Unable to change or add any telnet interfaces into mac-server

Model: CCR1036-12G-4S

ROS Version 6.11
/tool mac-server
remove 0
failure: can not remove the default entry
add interface=ether2
failure: interface unsupported
I have 6.10 on another device that is not a CCR and am able to use these commands with no issue.
have you tried v6.10 on CCR? adding works for me both in 6.10 CCR and 6.11 x86
also, removing should not work on any device, just because it's default entry. you should be able only disable it, not remove

I'll try to downgrade my ccr at home tonight when I get in and see. I know that on 6.10 on a 750gl I had laying around I was able to remove the default entry via command line and not disable it as I usually do.

Here is the print off the 750gl with 6.10 showing the all default entry removed via command line.
/tool mac-server> print
Flags: X - disabled, * - default 
 #    INTERFACE                                                                  
 0  * ether2                                                                     
 1    ether3                                                                     
 2    ether4                                                                     
 3    ether5                     
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8318
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: Known issues and bugs - a list

Wed Mar 26, 2014 11:23 pm

Here is the print off the 750gl with 6.10 showing the all default entry removed via command line.
/tool mac-server> print
Flags: X - disabled, * - default 
 #    INTERFACE                                                                  
 0  * ether2                                                                     
 1    ether3                                                                     
 2    ether4                                                                     
 3    ether5                     
as you can see, you DO have default entry (marked by "*")
yep, you can do "set 0 interface=ether2" to change default entry from 'all' to some specific interface :) but you cannot remove it completely =)
Russian-speaking forum: https://forum.mikrotik.by/. Welcome!

For every complex problem, there is a solution that is simple, neat, and wrong.

MikroTik. Your life. Your routing.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Thu Mar 27, 2014 1:11 pm

Description:
When doing a "export compact" changes to queue type default-small are not exported
for me (v6.11, x86) it's exported, but in strange manner: "set 16 pfifo-limit=20". I don't think that default-small has index 16 on every system :)
Can you test on a RouterBoard?

I tested on powerpc and mipsbe, on those its not exported.
Here is the print off the 750gl with 6.10 showing the all default entry removed via command line.
/tool mac-server> print
Flags: X - disabled, * - default 
 #    INTERFACE                                                                  
 0  * ether2                                                                     
 1    ether3                                                                     
 2    ether4                                                                     
 3    ether5                     
As said before, you can set the default to a different value then "all", or you can disable it, but it can not be removed.

Regarding 6.11 and adding a mac-server interface, I dont have a CCR to test on, can someone test please?
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8318
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: Known issues and bugs - a list

Thu Mar 27, 2014 2:23 pm

Can you test on a RouterBoard?

I tested on powerpc and mipsbe, on those its not exported.
Here's the result from my RB951-2n (mipsbe):
[admin@MikroTik] /queue type> ex
# jan/05/1970 00:18:03 by RouterOS 6.11
#
[admin@MikroTik] /queue type> set default-small pfifo-limit=20
[admin@MikroTik] /queue type> ex                              
# jan/05/1970 00:18:07 by RouterOS 6.11
#
/queue type
set 9 pfifo-limit=20
[admin@MikroTik] /queue type> 
so seems like the only thing to be fixed is using type names instead of indices, which are different from system to system
Russian-speaking forum: https://forum.mikrotik.by/. Welcome!

For every complex problem, there is a solution that is simple, neat, and wrong.

MikroTik. Your life. Your routing.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Thu Mar 27, 2014 2:58 pm

Here's the result from my RB951-2n (mipsbe):
[admin@MikroTik] /queue type> ex
# jan/05/1970 00:18:03 by RouterOS 6.11
#
[admin@MikroTik] /queue type> set default-small pfifo-limit=20
[admin@MikroTik] /queue type> ex                              
# jan/05/1970 00:18:07 by RouterOS 6.11
#
/queue type
set 9 pfifo-limit=20
[admin@MikroTik] /queue type> 
so seems like the only thing to be fixed is using type names instead of indices, which are different from system to system
Here is how it looks for me on a 750GL:
[admin@C1] > /queue type print where name=default-small
Flags: * - default 
 0 * name="default-small" kind=pfifo pfifo-limit=10 
[admin@C1] > # Notice the default pfifo-limit=10
[admin@C1] > /queue type set [/queue type find name=default-small] pfifo-limit=50
[admin@C1] > # Now we change that to 50
[admin@C1] > /queue type export compact
# jan/03/1970 21:33:02 by RouterOS 6.11
# software id = 3VYV-V1LD
#
[admin@C1] > # Our changes are not in export compact
[admin@C1] > /queue type print where name=default-small
Flags: * - default 
 0 * name="default-small" kind=pfifo pfifo-limit=50 
[admin@C1] > # Notice the pfifo-limit=50
So we are experiencing different behaviour, interesting...
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8318
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: Known issues and bugs - a list

Thu Mar 27, 2014 3:15 pm

what does "export verbose" show?..
Russian-speaking forum: https://forum.mikrotik.by/. Welcome!

For every complex problem, there is a solution that is simple, neat, and wrong.

MikroTik. Your life. Your routing.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Thu Mar 27, 2014 3:20 pm

what does "export verbose" show?..
[admin@C1] /queue type> exp ver
# jan/02/1970 00:08:00 by RouterOS 6.11
# software id = 3VYV-V1LD
#
/queue type
set 0 kind=pfifo name=default pfifo-limit=50
set 1 kind=pfifo name=ethernet-default pfifo-limit=50
set 2 kind=sfq name=wireless-default sfq-allot=1514 sfq-perturb=5
set 3 kind=red name=synchronous-default red-avg-packet=1000 red-burst=20 red-limit=60 red-max-threshold=50 red-min-threshold=10
set 4 kind=sfq name=hotspot-default sfq-allot=1514 sfq-perturb=5
set 5 kind=pcq name=pcq-upload-default pcq-burst-rate=0 pcq-burst-threshold=0 pcq-burst-time=10s pcq-classifier=src-address pcq-dst-address-mask=32 pcq-dst-address6-mask=128 pcq-limit=50 pcq-rate=0 pcq-src-address-mask=32 pcq-src-address6-mask=128 pcq-total-limit=2000
set 6 kind=pcq name=pcq-download-default pcq-burst-rate=0 pcq-burst-threshold=0 pcq-burst-time=10s pcq-classifier=dst-address pcq-dst-address-mask=32 pcq-dst-address6-mask=128 pcq-limit=50 pcq-rate=0 pcq-src-address-mask=32 pcq-src-address6-mask=128 pcq-total-limit=2000
set 7 kind=none name=only-hardware-queue
set 8 kind=mq-pfifo mq-pfifo-limit=50 name=multi-queue-ethernet-default
set 9 kind=pfifo name=default-small pfifo-limit=50
[admin@C1] /queue type> exp com
# jan/02/1970 00:08:38 by RouterOS 6.11
# software id = 3VYV-V1LD
#
[admin@C1] /queue type> 
So as you can see, default-small is at 50.

I tested on a 750GL and 1100AH, any chance you got one of those you can test on?
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
asmozre
just joined
Posts: 7
Joined: Sun Jan 22, 2012 1:40 am

Re: Known issues and bugs - a list

Thu Mar 27, 2014 3:58 pm

As said before, you can set the default to a different value then "all", or you can disable it, but it can not be removed.

Regarding 6.11 and adding a mac-server interface, I dont have a CCR to test on, can someone test please?
Actually, on that particular 750GL w/ ros 6.10 I can remove the interface completely and not just change it. When adding a new interface back into the mac-server the first one added becomes to default. I can not remove it via winbox however I can remove it via cli.

On the CCR1036-12G-4S w/ ros 6.10 I also can not add an interface other than the all, nor can I modify the all entry to another interface.
 
metabaron
just joined
Posts: 10
Joined: Fri Mar 28, 2014 4:56 am

Re: Known issues and bugs - a list

Fri Mar 28, 2014 5:09 am

Hello all, first post here, I just created my account and reported the bug:

Issue:
Super slow index page for the administration interface once you log on

Description:
Once you log on the administration interface, the loading time of the page is like almost 30 seconds

Versions affected:
Latest 6.11 version

How to reproduce:
Install 6.11

Notes:
Was perfect before I moved to the new 6.11. Update down through the web interface. Router reboot and stopped/started since then, several times.
 
andriys
Forum Guru
Forum Guru
Posts: 1187
Joined: Thu Nov 24, 2011 1:59 pm
Location: Kharkiv, Ukraine

Re: Known issues and bugs - a list

Fri Mar 28, 2014 12:42 pm

Issue:
Super slow index page for the administration interface once you log on

Description:
Once you log on the administration interface, the loading time of the page is like almost 30 seconds
Was perfect before I moved to the new 6.11.
Chances are this is a browser cache issue. Have you tried cleaning your browser cache?
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Fri Mar 28, 2014 1:00 pm

Issue:
Super slow index page for the administration interface once you log on

Description:
Once you log on the administration interface, the loading time of the page is like almost 30 seconds
Was perfect before I moved to the new 6.11.
Chances are this is a browser cache issue. Have you tried cleaning your browser cache?
I have many devices on 6.11, webfix is fine everywhere.

As said before, clean your cache and cookies and please let us know if its working.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
reinerotto
Member
Member
Posts: 437
Joined: Thu Dec 04, 2008 2:35 am

Re: Known issues and bugs - a list

Sun Mar 30, 2014 9:15 am

New issue regarding NAT during close of connection: Pls, refere to this thread.
http://forum.mikrotik.com/viewtopic.php ... 34#p418434
 
chadd
Member
Member
Posts: 347
Joined: Fri Dec 31, 2004 2:40 am

Re: Known issues and bugs - a list

Tue Apr 01, 2014 8:32 am

Normis,

On the RB951Ui units I have you cant access the POE settings menu. How do you check and upgrade the POE firmware on these units?
RB951Ui from MUM - RouterOS 6.5, connected to internet and then...
/system package update upgrade
router rebooted, all is ok but PoE firmware = 0.0 ;)
Checked in the day of MUM on two routers, same effect...
what is the output of these two commands?

/interface ethernet poe settings print
/interface ethernet poe settings upgrade
 
elmer
newbie
Posts: 40
Joined: Mon Jun 18, 2012 4:02 pm

Re: Known issues and bugs - a list

Sun Apr 06, 2014 12:46 am

RB951Ui from MUM - RouterOS 6.5, connected to internet and then...
/system package update upgrade
router rebooted, all is ok but PoE firmware = 0.0 ;)
Checked in the day of MUM on two routers, same effect...
what is the output of these two commands?

/interface ethernet poe settings print
/interface ethernet poe settings upgrade
v6.11 on router in this time shows:
bad command name settings (line 1 column 25)
there is poe upgrade command in v.6xx?
 
Majklik
newbie
Posts: 35
Joined: Fri Dec 23, 2011 10:20 pm

Re: Known issues and bugs - a list

Sun Apr 06, 2014 6:59 pm

5) L2TP Server bug - replies from wrong IP address
- http://forum.mikrotik.com/viewtopic.php ... 19#p398319
new ppp package invalidates this
It looks that this bug is still there? I tested this now with 6.11 and 6.12rc1 (Apr/04/2014 13:30:46).
By the way, is there any progress with a similar problem where multihop BFD (with BGP) uses too bad source IP of the outgoing interface and not loopback address ( [Ticket#2013110666000642] )?
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Sun Apr 06, 2014 9:37 pm

It looks that this bug is still there? I tested this now with 6.11 and 6.12rc1 (Apr/04/2014 13:30:46).
By the way, is there any progress with a similar problem where multihop BFD (with BGP) uses too bad source IP of the outgoing interface and not loopback address ( [Ticket#2013110666000642] )?
The bug is still there, its on the first post's list, which is up to date with 6.11

Any chance you want to do a bug report in here with that multihop BFD bad source IP?
Would be nice to be able to include it here with full replication instructions.

Thanks!
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
g0didit
just joined
Posts: 5
Joined: Wed Apr 16, 2014 10:32 am

Re: Known issues and bugs - a list

Wed Apr 16, 2014 10:52 am

Hi... I got some problems. Im using miktrotik for few years now and never face something like this.
I got one x86 pppoe concentrator with EoIP tunnels to other routers. (24 EoIP tunnels).

Recently updated RoS from 4.16 -> 5.26 -> 6.11. After update i need to add few more EoIP tunnels, added and seems all OK for few seconds until first PPPoE user try to connect to any other PPPoE server, still no PPPoE server on new tunnell and EoIP tunnel was "overwriten" by that PPPoE connection. Newely created tunnell is no longer exist. I delete PPPoE connection sometime router hungs, I try to add again same EoIP and winbox say "interface exist" i cant find that tunnel in winbox or terminal. Need HELP. Thanx.
You do not have the required permissions to view the files attached to this post.
 
ddt
just joined
Posts: 19
Joined: Thu Apr 17, 2014 3:18 am

Re: Known issues and bugs - a list

Mon Apr 21, 2014 9:18 pm

On my CRS running 6.12, if I enter this code:
/interface ethernet switch ingress-vlan-translation
add ports=ether2 customer-vid=0 new-customer-vid=8 sa-learning=yes

/interface ethernet switch egress-vlan-translation
add customer-vid=8 new-customer-vid=0 ports=ether2
The ether2 port will correctly work as it did in 6.11 and before, until I restart the router. Then it freezes at boot up at the "Starting services" readout.

I've tried removing the egress-vlan-translation as well, and just having the first 2 lines. It still freezes at startup.

As I said, this works correctly in 6.11 and before, and I isolated the freezing to just this area of my working config.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Thu Apr 24, 2014 2:50 pm

All issues re-tested on v6.12 release. The list is now current for v6.12
0 out of 6 bugs on the list at the release of v6.12 were fixed.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Thu Apr 24, 2014 2:58 pm

Issue:
"RouterOS Default Configuration" windows shows when it should not

Description:
The "Default Configuration" window appears even when the router does NOT have a default configuration.

Versions affected:
6.12, not tested rest

How to reproduce:
1) Reset a router to default config with:
/system reset-configuration
2) Do NOT login with winbox or SSH!
Login with API and issue:
/system/reset-configuration
=no-defaults=yes
3) After reset, login with MAC winbox.
The router has no config, but the "RouterOS Default Configuration" window will still show, and offers to run the "Remove config" script.

Notes:
It seems that when you reset to no-default config using the API, the flags telling the router it doesnt have default config anymore dont get set.
See attached a console screenshot showing that the router still thinks its got a default config, when in fact there is no config present.

Support TicketID:
[Ticket#2014042466000576]
You do not have the required permissions to view the files attached to this post.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
acung
just joined
Posts: 19
Joined: Thu Nov 26, 2009 5:57 pm
Location: Jakarta

Re: Known issues and bugs - a list

Thu May 01, 2014 5:35 am

Issue:
CRS125-24G-1S-RM: Configuration elements missing from the Web interface: Switch and LCD
Issue:
CRS125-24G-1S-RM: Switch setting bridge-type=customer-vlan-bridge is not retained after reboot.
I dont have a CRS to test with, could anyone please confirm these?
Yes I have two of my CRS125-24G-1S-RM have missing switch and LCD menu from the Web interface.

ROS Version: 6.12
 
Pebu
just joined
Posts: 4
Joined: Sat Nov 10, 2012 5:05 pm

Re: Known issues and bugs - a list

Fri May 02, 2014 2:26 pm

On my CRS running 6.12, if I enter this code:
/interface ethernet switch ingress-vlan-translation
add ports=ether2 customer-vid=0 new-customer-vid=8 sa-learning=yes

/interface ethernet switch egress-vlan-translation
add customer-vid=8 new-customer-vid=0 ports=ether2
The ether2 port will correctly work as it did in 6.11 and before, until I restart the router. Then it freezes at boot up at the "Starting services" readout.
I've tried removing the egress-vlan-translation as well, and just having the first 2 lines. It still freezes at startup.
As I said, this works correctly in 6.11 and before, and I isolated the freezing to just this area of my working config.
+1, I can confirm this happens to my CRS @ 6.12 as well in exactly the same situation. Only solution is to reset the config using the reset switch, as the router never proceeds past 'Starting services'. I'm down to 6.11 now.
The CSR works fine using the mentioned config as long as you don't reboot it.
 
User avatar
falestiny
Frequent Visitor
Frequent Visitor
Posts: 51
Joined: Fri Sep 10, 2010 3:11 pm
Location: everywhere
Contact:

Re: Known issues and bugs - a list

Fri May 02, 2014 2:53 pm

also there is a bug with encrypted VPN connections since OS version 6.8 and not fixed until this moment.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Fri May 02, 2014 4:05 pm

also there is a bug with encrypted VPN connections since OS version 6.8 and not fixed until this moment.
Please be more specific. Ideally, follow the template in post2.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
Rudios
Forum Veteran
Forum Veteran
Posts: 966
Joined: Mon Mar 11, 2013 12:58 pm
Location: The Netherlands

Re: Known issues and bugs - a list

Tue May 06, 2014 8:42 am

Issue:
Queue graphs always available for viewing

Description:
Regardless of the settings in /tool graphing queue, a queue graph is always available
Eg.
Internal devices use default subnet 192.168.88.0/24
In /tools graphing all three options (interfaces, resources and queue) are set to be allowed from 10.10.10.0/24.
Then neither resource and interface graphs are available, as I suspect because of the allowed subnet.
But the queue graph is available for viewing.

Versions affected:
RouterOS 6.5 and 6.12
Did not test versions in between

How to reproduce:
Create a /tool graphing queue for a non-used subnet/IP address and see http://ip-address/graphs
See example in description.

Support TicketID:
Ticket#2014050666000189
Testing setup with: 2 x RB750UP | 2 x RB750GL | 1 x RB951G-2HnD | 1 x RB2011UiAS-IN
 
User avatar
dohmniq
Frequent Visitor
Frequent Visitor
Posts: 78
Joined: Sat Nov 17, 2012 12:17 pm

Re: Known issues and bugs - a list

Tue May 06, 2014 1:04 pm

Issue:
Can't list or delete files with overly long filenames

Description:
I wrote a script that used /tool fetch mode="http" host="domain.name" address=1.2.3.4 port=8080 src-path="/API/report\?query" where the query-string in src-path contained non-alphanumeric characters (some URL-escaped) but well over 255 characters long (more like 2000). I forgot to add keep-result=no to the command (it defaults to yes) so it saved an output file.

A typical URL might look like:
http://domain.name/API/report?software_id=ABCD-1234&report=registered%20connections&content=%5b%20%20{%20%20%22.id%22:%20%22*17%22, [... and so on ...]
When I do /system resource print there's a massive loss of hdd disk space:
[admin@MikroTik] /> /sys resource pr
                   uptime: 8w6d15h19m2s
                  version: 6.10
               build-time: Feb/12/2014 13:46:18
              free-memory: 6.7MiB
             total-memory: 32.0MiB
                      cpu: MIPS 74Kc V4.12
                cpu-count: 1
            cpu-frequency: 600MHz
                 cpu-load: 5%
           free-hdd-space: 552.0KiB
          total-hdd-space: 128.0MiB
  write-sect-since-reboot: 1170438
         write-sect-total: 1187250
               bad-blocks: 0%
        architecture-name: mipsbe
               board-name: RB911G-5HPnD
                 platform: MikroTik
But when I do /file print (which takes AGES) there are only a few files that don't explain the disk usage:
[admin@MikroTik] /system scheduler> /file pr
 # NAME                                                                               TYPE                                                                                    SIZE CREATION-TIME
 0 post-6.10.rsc                                                                      script                                                                                  2695 mar/02/2014 18:34:14
 1 ABCD-1234.key                                                                      .key file                                                                                204 jan/01/2002 01:19:04
 2 um-before-migration.tar                                                            .tar file                                                                            17.5KiB jan/02/1970 00:00:35
 3 5MB.zip                                                                            .zip file                                                                             5.0MiB mar/06/2014 08:56:33
 4 pub                                                                                directory                                                                                    mar/02/2014 18:31:28
 5 post-mesh.rsc                                                                      script                                                                                  2267 mar/05/2014 14:06:04
 6 20MB.zip                                                                           .zip file                                                                            20.0MiB mar/18/2014 18:23:18
 7 pre-6.10.rsc                                                                       script                                                                                  2694 mar/02/2014 18:31:31
 8 skins                                                                              directory                                                                                    jan/01/1970 00:00:40
 9 script-functions.rsc                                                               script                                                                                  1574 apr/28/2014 09:58:53
no such item (4)
However, if I FTP to the RouterBOARD then the files appear. However, I can't delete any of them - I get "550 No such file or directory" errors.

Files do not appear on webfig either.

Versions affected:
at least 6.9 and 6.10

How to reproduce:
[admin@MikroTik2] /system resource> /tool fetch mode=http host="www.mikrotik.com" address=159.148.147.196 port=80 src-path="\?query&%*{:981293819381938192381983198312319283918239183987321498172498712349871234981274981273498213479218437921843721983472193847219348712349872134912873491283471293487219348712349872134981274391283472193487129348712349871234981273491283471293487123948712349871234981273491283472193487213948712391874192387421934871239487123987"
  status: finished

[admin@MikroTik2] /system resource> /file pr
 # NAME                                                                               TYPE                                                                                    SIZE CREATION-TIME
 0 Working-latest.rsc                                                                 script                                                                                6.7KiB jan/02/2014 13:31:21
 1 log.0.txt                                                                          .txt file                                                                            50.2KiB may/06/2014 10:52:26
 2 pre-6.10.rsc                                                                       script                                                                                7.7KiB jan/01/2002 03:04:16
 3 skins                                                                              directory                                                                                    jan/01/1970 01:00:17
 4 webproxy                                                                           directory                                                                                    sep/19/2013 13:56:24
 5 webproxy/error.html                                                                .html file                                                                          163.7KiB dec/29/2013 21:24:00
 6 pub                                                                                directory                                                                                    jan/01/2002 02:08:25
 7 log.1.txt                                                                          .txt file                                                                            68.3KiB apr/12/2014 10:53:24
 8 with-uSD                                                                           file                                                                                293.7KiB jan/01/2002 02:00:10
 9 micro-sd                                                                           disk                                                                                         apr/15/2014 09:21:54
10 WORKING.rsc                                                                        script                                                                                5.6KiB jan/01/2002 03:55:00
11 micro-sd/lost+found                                                                directory                                                                                    jan/02/1970 01:03:02
12 micro-sd/web-proxy1                                                                web-proxy store                                                                              mar/12/2014 15:23:42
13 micro-sd/web-proxy2                                                                web-proxy store                                                                              jan/01/2002 02:01:17
[admin@MikroTik2] /system resource>

[admin@server ~]$ ftp mikrotik2
Connected to mikrotik2.
220 MikroTik2 FTP server (MikroTik 6.10) ready
Name (mikrotik2:admin):
331 Password required for admin
Password:
230 User admin logged in
Remote system type is UNIX.
ftp> dir
229 Entering Extended Passive Mode (|||42036|)
150 Opening data connection
drwxrwx---   1 root     root         2048 Jan  1 01:00 ?query&%*{:9812938193819381923819831983123192839182391839873214981724987123498712349812749812734982134792184379218437219834721938472193487123498721349128734912834712934872193487123498721349812743912834721934871293487123498712349812734912834712934871239487
drwxrwx---   5 root     root         4096 Jan  1 02:00 micro-sd
-rw-rw----   1 root     root        51541 May  6 10:56 log.0.txt
-rw-rw----   1 root     root        69899 Apr 12 10:53 log.1.txt
drwxrwx---   1 root     root         2048 Jan  1 02:08 pub
drwxrwx---   1 root     root         2048 Sep 19 13:56 webproxy
-rw-rw----   1 root     root       300776 Jan  1 02:00 with-uSD
drwxrwx---   1 root     root         2048 Jan  1 01:00 skins
-rw-rw----   1 root     root         6853 Jan  2 13:31 Working-latest.rsc
-rw-rw----   1 root     root         5688 Jan  1 03:55 WORKING.rsc
-rw-rw----   1 root     root         7838 Jan  1 03:04 pre-6.10.rsc
226 Transfer complete
ftp> mdelete *query*
mdelete ?query&%*{:9812938193819381923819831983123192839182391839873214981724987123498712349812749812734982134792184379218437219834721938472193487123498721349128734912834712934872193487123498721349812743912834721934871293487123498712349812734912834712934871239487 [anpqy?]? y
550 ?query&%*{:9812938193819381923819831983123192839182391839873214981724987123498712349812749812734982134792184379218437219834721938472193487123498721349128734912834712934872193487123498721349812743912834721934871293487123498712349812734912834712934871239487: No such file or directory
ftp> cd "?query&%*{:9812938193819381923819831983123192839182391839873214981724987123498712349812749812734982134792184379218437219834721938472193487123498721349128734912834712934872193487123498721349812743912834721934871293487123498712349812734912834712934871239487"
550 ?query&%*{:9812938193819381923819831983123192839182391839873214981724987123498712349812749812734982134792184379218437219834721938472193487123498721349128734912834712934872193487123498721349812743912834721934871293487123498712349812734912834712934871239487: No such file or directory
ftp>
Notes:
If you have scheduled scripts that use /tool fetch then maybe check to see if you need to add keep-result=no !!!

Support TicketID:
Ticket#2014050666000367
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Tue May 06, 2014 1:49 pm

Issue:
Queue graphs always available for viewing
Thanks for the report, added!
Issue:
Can't list or delete files with overly long filenames
Very nice report, thank you!

Added to the list as well.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
dohmniq
Frequent Visitor
Frequent Visitor
Posts: 78
Joined: Sat Nov 17, 2012 12:17 pm

Re: Known issues and bugs - a list

Tue May 06, 2014 10:45 pm

Just to follow up from my bug post about invisible/immortal files with super-long filenames...

If your RouterBOARD hasn't already run out of hdd space then you can apply this workaround:
  • NOTE: all files on your routerboard will be wiped but you will keep your configuration!
  • download netinstall and the corresponding routerOS npk
  • using webfig / CLI / etc. set routerboard settings to boot "try-ethernet-once-then-nand"
  • fire up netinstall on your windows PC (sadly doesn't seem to work under Wine on unix)
  • configure netinstall for netbooting - tick "Boot server enabled" box, etc.
  • browse (in netinstall) to your routerOS package
  • reboot routerboard
  • routerboard should appear in netinstall devices/routers list
  • click on routerboard in list, make sure "keep old configuration" is ticked and "apply default config" is unticked
  • click install
  • click reboot
This will repartition and reformat your routerboard, getting rid of any files you can't see or delete and reclaiming your hdd space.
As far as I can tell, the routerboard boot settings go back to "nand-if-fail-then-ethernet"
You will keep your licence and config.

IF you let your hdd space get to zero then you will very likely need physical access to your routerboard's reset button!
 
sasha
just joined
Posts: 1
Joined: Wed May 07, 2014 12:56 pm

Re: Known issues and bugs - a list

Wed May 07, 2014 1:23 pm

Issue:
SMB shares disappear at random times

Description:
External HD is attached and folder on it SMB shared but router intermittently dis/re-connects HD. As a result HD device is enumerated as /usb1 or /usb2 without a rule or switched between /usb1 and /usb2 at random times or completely lost from Stores -> Disks. SMB shares get lost and shares users are pissed off. Unstable SMB render this feature useless and it was one of the reasons we opted for RB2011UiAS-2HnD-IN.

Log looks like
Image

In WebFig disk disappears and sometimes it can not be enumerated again without reconnecting usb cable. This external HD previously worked and had folders shared on much cheaper router without a glitch. It would be good if RouterOS could use FAT32 for fs of attached HD too.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Fri May 09, 2014 12:10 pm

Issue:
SMB shares disappear at random times
This sounds like the same problem described here: http://forum.mikrotik.com/viewtopic.php?f=13&t=84744

Its not actually a SMB share problem, but an underlying problem with USB storage dismounting/re-mounting causing SMB problems.

Please contact official MikroTik support at support@mikrotik.com with a supout file.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
QCTIK
just joined
Posts: 3
Joined: Sun May 11, 2014 11:02 pm

Re: Known issues and bugs - a list

Mon May 12, 2014 3:29 pm

SEVERE BUG I followed the wiki example as of 14 april 2014

like the example ive created a group of switched port, put some port with ingress translation for customer vid , after that created a port with a tag for the already created vlan.

everything went fine until...

i tried to put a tagged port outside the initial group to use the switch native vlan for that port.

packet stopped stop to flow. Restarted the switch it did'nt boot up

stopped to 'starting services'

replicated the incident three time on that switch then tried another one to make sure

same again....

could you check that please.
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Tue May 13, 2014 9:33 am

3) L2TP Server bug - replies from wrong IP address
- viewtopic.php?f=2&t=78816&p=398319#p398319
fixed in v6.13
6) Queue type default-small not exported with export compact
- viewtopic.php?f=2&t=78816&p=417649#p417649
compact only exports changed values. default-small is the default value, so it will not be exported. not a bug
No answer to your question? How to write posts
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Tue May 13, 2014 11:15 am

6) Queue type default-small not exported with export compact
- viewtopic.php?f=2&t=78816&p=417649#p417649
compact only exports changed values. default-small is the default value, so it will not be exported. not a bug
The default value is changed, and the change to the default value is not exported.

Other changes to default values are exported, for example:
[tomas@router] /queue type> exp
# may/13/2014 10:09:06 by RouterOS 6.12
# software id = FR5N-MA9W
#
[tomas@router] /queue type> set [find name=default-small] pfifo-limit=50
[tomas@router] /queue type> exp
# may/13/2014 10:09:13 by RouterOS 6.12
# software id = FR5N-MA9W
#
[tomas@router] /queue type> set [find name=pcq-download-default] pcq-rate=1024
[tomas@router] /queue type> exp
# may/13/2014 10:09:59 by RouterOS 6.12
# software id = FR5N-MA9W
#
/queue type
set 6 pcq-rate=1024
[tomas@router] /queue type> 
This is inconsistent.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Tue May 13, 2014 12:24 pm

Now I get it. We checked in v6.13 and it worked for us, but it looks like v6.12 has this issue. Seems it's fixed.
No answer to your question? How to write posts
 
lorsungcu
Frequent Visitor
Frequent Visitor
Posts: 80
Joined: Sat Jul 09, 2011 11:11 pm

Re: Known issues and bugs - a list

Wed May 14, 2014 5:14 pm

Issue:
IPSEC will not connect from 6.12 to 5.26 ROS

Description:
Using 6.12 on a router and 5.26 on another, unable to initiate a tunnel. Tested on two different devices. Works fine if downgraded to 5.26, or 6.9.

Versions affected:
6.12

How to reproduce:
Build functioning IPSec/L2TP tunnels in 5.26 between routers. Upgrade one to 6.12.

Notes:
L2TP will connect fine on it's own, issue seems to be with IPSec. No response from Mikrotik after they asked for access to routers. I sent them VPN info as well as 3+ follow up emails. I can only assume this is a bug until I hear back from them.

Support TicketID:
2014020566000758
 
polppol
just joined
Posts: 1
Joined: Thu May 15, 2014 12:31 pm

Re: Known issues and bugs - a list

Thu May 15, 2014 12:47 pm

Issue:
Winbox doesn't unlock upload files after upload whole folder via Winbox > Files menu

Description:
When upload whole folder (with multiple files in that folder) to Mikrotik via Winbox
Winbox doesn't release uploaded files in that folder even if those files are upload 100% complete.
2014-04-03_15-40-12.png

Versions affected:

6.12

How to reproduce:
1. Create "TEST_FOLDER" on your Desktop
2. Create(or copy anything) to "TEST_FOLDER" that you just created
3. Start Winbox > Login > and goto Files menu
4. drag "TEST_FOLDER" from your desktop to "Files" windows
5. wait until all file are uploaded
6. now try to move/delete/edit any file in "TEST_FOLDER" on your Desktop
you should get message that WinBox.exe still use those file

Notes:
workaround: close WinBox.exe and re-open it / upload via ftp

Support TicketID:
2014040366000338
You do not have the required permissions to view the files attached to this post.
 
dzoleg
just joined
Posts: 3
Joined: Thu Oct 03, 2013 10:28 am

Re: Known issues and bugs - a list

Sat May 17, 2014 2:47 pm

ROS 6.13
In webfig can create backup, but can't restore new encrypted config.
 
User avatar
luqasz
Member Candidate
Member Candidate
Posts: 101
Joined: Thu Aug 16, 2007 9:53 pm
Location: Poland

Re: Known issues and bugs - a list

Sun May 25, 2014 11:04 pm

Issue:
Wrongly calculated and selected routes.
Description:
http://forum.mikrotik.com/viewtopic.php?f=2&t=84461
Version affected:
Tested on 6.12. I would not be suprised if all 6.x are affected.
How to reproduce:
http://forum.mikrotik.com/viewtopic.php?f=2&t=84461
Support TicketID:
2014042866000685
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Tue Jun 03, 2014 2:03 pm

I have been swamped with work and other issues last weeks, I will update the list for 6.13 and include all reports in the next few days.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
MadriSX
just joined
Posts: 4
Joined: Tue May 20, 2014 5:56 pm

Re: Known issues and bugs - a list

Wed Jun 11, 2014 5:48 pm

Hi there,

I´ve detected a simple issue when I upgraded to 6.14 and I think many people will suffer this.

I have some mangle rules for balancing traffice per type and I use "balanceo" (8 characters) as routing mark but surprisily the new RouterOS version is limited to 7 characters so my static balancing route was inactive after upgrading.

It´s simple to solve I think :-)
 
Cliff
just joined
Posts: 9
Joined: Fri Jul 05, 2013 1:57 am

Re: Known issues and bugs - a list

Mon Jun 16, 2014 3:04 am

smb does not work since 6.14. Error 1208 after entering username and password.
Downgrade to 6.13 helps.
 
basisbit
just joined
Posts: 4
Joined: Wed Feb 08, 2012 9:22 pm

Re: Known issues and bugs - a list

Tue Jun 17, 2014 3:56 pm

also there is a bug with encrypted VPN connections since OS version 6.8 and not fixed until this moment.
I can confirm that. It causes connection drops. For example you are able to connect with WinBox over VPN, but after a few seconds it disconnects. Also opening Webfig or loading the graphing-images fairs after loading some data.
I tried various things, recreated the nat-masquerade, changed MCS packet sizes and so on, deactivated all firewall rules, tried secured winbox (this works for a few seconds but then the connection drops again).
Only affects connections to the router (web, winbox, ftp,...), the vpn connection stays stable and everything else works fine (ping, youtube over the vpn, tcp and udp connections over the vpn to the local network or internet are unaffected.
SMB doesn't work at all even from local since that problem started.
Thankfully, DNS seems to be unaffected because of short connection time. IPv6 is not activated and connection tracking settings of the ipv4 firewall are all set to auto/standard values.
Newest RouterOS version installed and newest bootloader. Hardware is a 2 years old Mikrotik RB751g-2hnd.
Any Idea what could be wrong?

PS: all my other mikrotik devices are unaffected.
 
zlativ
just joined
Posts: 1
Joined: Tue Jul 01, 2014 11:16 pm

Re: Known issues and bugs - a list

Tue Jul 01, 2014 11:34 pm

3) L2TP Server bug - replies from wrong IP address
- viewtopic.php?f=2&t=78816&p=398319#p398319
fixed in v6.13
It's really work fine now for mipsbe architecture (checked on RB951G-2HnD, ROS v6.13 and v6.15), but at the same time bug still appear for tile architecture (checked on CCR1036-8G-2S+, ROS v6.13 and v6.15).
 
michl
just joined
Posts: 9
Joined: Mon Jul 07, 2014 5:05 pm

Re: Known issues and bugs - a list

Wed Jul 09, 2014 3:57 pm

mkt_bp.jpg
I could not restore configuration with no-password backup file. Tried several files, not only 1.
If I put password when backup the file, I can restore the config.

v6.15
RB951Ui-2HnD
You do not have the required permissions to view the files attached to this post.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Fri Jul 18, 2014 1:48 pm

All issues re-tested on v6.16 release. The list is now current for v6.16
2 out of 9 bugs on the list at the release of v6.16 were fixed.

The following issues from the list have been fixed from 6.12 to 6.16:
3) L2TP Server bug - replies from wrong IP address
- http://forum.mikrotik.com/viewtopic.php ... 19#p398319
8) Queue graphs always available for viewing
- http://forum.mikrotik.com/viewtopic.php ... 73#p424539
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Fri Jul 18, 2014 3:01 pm

Now I get it. We checked in v6.13 and it worked for us, but it looks like v6.12 has this issue. Seems it's fixed.
Normis: Just an update, this is still NOT fixed for me in 6.16/6.17 on a RB 750GL.

This was regarding to this post: http://forum.mikrotik.com/viewtopic.php ... 53#p425766
To replicate, just follow the steps in http://forum.mikrotik.com/viewtopic.php ... 49#p417649 :)
Last edited by tomaskir on Fri Jul 18, 2014 6:54 pm, edited 1 time in total.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Fri Jul 18, 2014 3:04 pm

Issue:
Winbox doesn't unlock upload files after upload whole folder via Winbox > Files menu
This is more a Winbox issue, but confirmed, and added to the list.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Fri Jul 18, 2014 3:11 pm

I could not restore configuration with no-password backup file. Tried several files, not only 1.
If I put password when backup the file, I can restore the config.

v6.15
RB951Ui-2HnD
I could not replicate this in 6.17.
Since this seems to be working in 6.17, can you please verify and let us know if you still have this issue.
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
denisun
Frequent Visitor
Frequent Visitor
Posts: 65
Joined: Wed Jul 16, 2014 6:38 pm
Location: Greece

Re: Known issues and bugs - a list

Fri Jul 18, 2014 8:34 pm

I have this bug:
http://forum.mikrotik.com/viewtopic.php?f=2&t=87082

Description:
I have IPv6 enable over PPPoE.
When ether1 stop then PPPoE drop and can't connect for some minutes.
It take many, many, many conection/disconnection every second for about 4-5 minutes and sometimes 10minutes.
I must wait this time or stop and start PPPoE.
The problem appears if yet i have only enable IPv6 support in my PPPoE without any other IPv6 configuration like DHCPv6 client etc.
Every time my ISP make changes in Brass, the PPPoE client connection drop and ether1 drop normally, and i have this problem.

I tested in 6.15, 6.16 and 6.17 with same result.
I tested in many RB.
"What one programmer can do in one month, two programmers can do in two months."
Fred Brooks...
 
User avatar
denisun
Frequent Visitor
Frequent Visitor
Posts: 65
Joined: Wed Jul 16, 2014 6:38 pm
Location: Greece

Re: Known issues and bugs - a list

Fri Jul 18, 2014 8:37 pm

I have this bug:
http://forum.mikrotik.com/viewtopic.php?f=2&t=87082

Description:
I have IPv6 enable over PPPoE.
When ether1 stop then PPPoE drop and can't connect for some minutes.
It take many, many, many conection/disconnection every second for about 4-5 minutes and sometimes 10minutes.
I must wait this time or stop and start PPPoE.
The problem appears if yet i have only enable IPv6 support in my PPPoE without any other IPv6 configuration like DHCPv6 client etc.
Every time my ISP make changes in Brass, the PPPoE client connection drop and ether1 drop normally, and i have this problem.

I tested in 6.15, 6.16 and 6.17 with same result.
I tested in many RB.
"What one programmer can do in one month, two programmers can do in two months."
Fred Brooks...
 
dannnic
just joined
Posts: 4
Joined: Mon Nov 18, 2013 8:23 am

Re: Known issues and bugs - a list

Sat Jul 19, 2014 11:26 am

Issue :

Successful "/tool fetch" execute will add a log to Log Memory. This is NOT Working from v6.15 onwards... not fixed in v6.16 as well.

Description:
This was working since the feature introduced in v5.x and up to v6.14, but it was NOT working since v6.15 onwards ....

Versions affected:
v6.15, v6.16

How to reproduce:
tool fetch dst-path=<ftp-server-file-path> address=<ftp-server-ip> mode=ftp upload=yes src-path=<file-name-in-router-files-list> user=<username> password=<password>

Support TicketID:
Ticket#2014071966000151
 
michl
just joined
Posts: 9
Joined: Mon Jul 07, 2014 5:05 pm

Re: Known issues and bugs - a list

Wed Jul 23, 2014 2:05 pm

I could not replicate this in 6.17.
Since this seems to be working in 6.17, can you please verify and let us know if you still have this issue.
Sorry, I could not let the router reboot for this moment (if successful), I will update later.

------------

Another bug:

IPSec dynamic policy stucks after disconnect, cause unable to reconnect again. Tested on Rb951 and Rb751. Previously didnt happen on v6.12/v6.15 (couldnt remember).
http://forum.mikrotik.com/viewtopic.php?f=2&t=87306
ipsec_dynamic_policy.jpg
You do not have the required permissions to view the files attached to this post.
 
pedropilla
just joined
Posts: 4
Joined: Tue Jun 14, 2011 10:40 pm

Re: Known issues and bugs - a list

Wed Jul 23, 2014 3:14 pm

Hi guys, i'm having trouble collecting data from simple queues on 6.17, i'm using cacti as nms.

Apparently the OID's of simple queues have changed, i'm trying to reproduce manually the situation making a snmpwalk on a device from OID ".1.3.6.1.4.1.14988.1.1.2" and the first OID taht came is ".1.3.6.1.4.1.14988.1.1.3.9.0". Is anyone having issues with collecting data trough snmp on 6.17?

Thanks and sorry for the bad english.
 
pedropilla
just joined
Posts: 4
Joined: Tue Jun 14, 2011 10:40 pm

Re: Known issues and bugs - a list

Wed Jul 23, 2014 3:21 pm

A simple reboot worked for me... ¬¬
Hi guys, i'm having trouble collecting data from simple queues on 6.17, i'm using cacti as nms.

Apparently the OID's of simple queues have changed, i'm trying to reproduce manually the situation making a snmpwalk on a device from OID ".1.3.6.1.4.1.14988.1.1.2" and the first OID taht came is ".1.3.6.1.4.1.14988.1.1.3.9.0". Is anyone having issues with collecting data trough snmp on 6.17?

Thanks and sorry for the bad english.
 
Rudios
Forum Veteran
Forum Veteran
Posts: 966
Joined: Mon Mar 11, 2013 12:58 pm
Location: The Netherlands

Re: Known issues and bugs - a list

Thu Jul 24, 2014 12:40 pm

Issue:
Queue graphs always available for viewing

Description:
Regardless of the settings in /tool graphing queue, a queue graph is always available
Eg.
Internal devices use default subnet 192.168.88.0/24
In /tools graphing all three options (interfaces, resources and queue) are set to be allowed from 10.10.10.0/24.
Then neither resource and interface graphs are available, as I suspect because of the allowed subnet.
But the queue graph is available for viewing.

Versions affected:
RouterOS 6.5 and 6.12
Did not test versions in between

How to reproduce:
Create a /tool graphing queue for a non-used subnet/IP address and see http://ip-address/graphs
See example in description.

Support TicketID:
Ticket#2014050666000189
How about this bug.
Have not read anything about it, also not heard anything from Mikrotik itself.
I have just tested it and the but is still present on version 6.17!!!
Testing setup with: 2 x RB750UP | 2 x RB750GL | 1 x RB951G-2HnD | 1 x RB2011UiAS-IN
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Thu Jul 24, 2014 12:55 pm

How about this bug.
Have not read anything about it, also not heard anything from Mikrotik itself.
I have just tested it and the but is still present on version 6.17!!!
I tested it on 6.17 and could not replicate... so I removed it from the list.

Can you give exact step-by-step to replicate pls?
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
Rudios
Forum Veteran
Forum Veteran
Posts: 966
Joined: Mon Mar 11, 2013 12:58 pm
Location: The Netherlands

Re: Known issues and bugs - a list

Thu Jul 24, 2014 2:08 pm

How about this bug.
Have not read anything about it, also not heard anything from Mikrotik itself.
I have just tested it and the but is still present on version 6.17!!!
I tested it on 6.17 and could not replicate... so I removed it from the list.

Can you give exact step-by-step to replicate pls?
It is quite easy.
Create a simple queue

ros code

/queue simple
add name=queue1 target=""
and allow any unused IP address to view the graphs of the queue

ros code

/tool graphing queue
add allow-address=1.1.1.1/32
If you now browse to the IP address of the router and look at the graphs, the queue graph is still available for viewing!
Testing setup with: 2 x RB750UP | 2 x RB750GL | 1 x RB951G-2HnD | 1 x RB2011UiAS-IN
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8318
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: Known issues and bugs - a list

Thu Jul 24, 2014 3:41 pm

by default, 'allow-target' is enabled, so if your rule catches anything ('target=""'), then anyone should be able to see that queue on graphs page, I think

so recheck with

ros code

/tool graphing queue add allow-address=1.1.1.1/32 allow-target=no
Russian-speaking forum: https://forum.mikrotik.by/. Welcome!

For every complex problem, there is a solution that is simple, neat, and wrong.

MikroTik. Your life. Your routing.
 
Rudios
Forum Veteran
Forum Veteran
Posts: 966
Joined: Mon Mar 11, 2013 12:58 pm
Location: The Netherlands

Re: Known issues and bugs - a list

Thu Jul 24, 2014 4:41 pm

by default, 'allow-target' is enabled, so if your rule catches anything ('target=""'), then anyone should be able to see that queue on graphs page, I think

so recheck with

ros code

/tool graphing queue add allow-address=1.1.1.1/32 allow-target=no
Sounds like that can make a difference, but in the end it doesn't
I did as you said, and put the allow-target to no. The queue is still available on the graphs page.
Additionally I changed the target itself to be my loopback-bridge (I let the allow-target to no).
Still it is available on graphing with the allow-address still to be defined as 1.1.1.1/32

[edit]
I also played around with assigning it to the created queue itself rather than to all queues, but still no differences.
Testing setup with: 2 x RB750UP | 2 x RB750GL | 1 x RB951G-2HnD | 1 x RB2011UiAS-IN
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8318
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: Known issues and bugs - a list

Thu Jul 24, 2014 5:06 pm

I checked that, and there are actually two bugs:

1. in Terminal, you can create simple queue with target="" - after that WinBox shows "Target" in red; if you create such entry in WinBox, it says "Error in Target - at least one entry expected!"

2. if 'target' contains at least one entry that is not an IP address (like interface or empty target created via bug #1), Graphing always shows that queue via web, in spite of 'allow-*' settings
Russian-speaking forum: https://forum.mikrotik.by/. Welcome!

For every complex problem, there is a solution that is simple, neat, and wrong.

MikroTik. Your life. Your routing.
 
User avatar
tomaskir
Trainer
Trainer
Topic Author
Posts: 1120
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: Known issues and bugs - a list

Thu Jul 24, 2014 5:28 pm

I checked that, and there are actually two bugs:

1. in Terminal, you can create simple queue with target="" - after that WinBox shows "Target" in red; if you create such entry in WinBox, it says "Error in Target - at least one entry expected!"

2. if 'target' contains at least one entry that is not an IP address (like interface or empty target created via bug #1), Graphing always shows that queue via web, in spite of 'allow-*' settings
Very nice job pinning it down!

Want to put it into a proper bug-report format and submit to MikroTik and this thread, or should I?
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
denisun
Frequent Visitor
Frequent Visitor
Posts: 65
Joined: Wed Jul 16, 2014 6:38 pm
Location: Greece

Re: Known issues and bugs - a list

Thu Jul 24, 2014 10:51 pm

I have this bug:
http://forum.mikrotik.com/viewtopic.php?f=2&t=87082

Description:
I have IPv6 enable over PPPoE.
When ether1 stop then PPPoE drop and can't connect for some minutes.
It take many, many, many conection/disconnection every second for about 4-5 minutes and sometimes 10minutes.
I must wait this time or stop and start PPPoE.
The problem appears if yet i have only enable IPv6 support in my PPPoE without any other IPv6 configuration like DHCPv6 client etc.
Every time my ISP make changes in Brass, the PPPoE client connection drop and ether1 drop normally, and i have this problem.

I tested in 6.15, 6.16 and 6.17 with same result.
I tested in many RB.
And here it is my logs:
http://forum.mikrotik.com/viewtopic.php ... 09#p438609
"What one programmer can do in one month, two programmers can do in two months."
Fred Brooks...
 
Rudios
Forum Veteran
Forum Veteran
Posts: 966
Joined: Mon Mar 11, 2013 12:58 pm
Location: The Netherlands

Re: Known issues and bugs - a list

Fri Jul 25, 2014 12:07 am

I checked that, and there are actually two bugs:

1. in Terminal, you can create simple queue with target="" - after that WinBox shows "Target" in red; if you create such entry in WinBox, it says "Error in Target - at least one entry expected!"

2. if 'target' contains at least one entry that is not an IP address (like interface or empty target created via bug #1), Graphing always shows that queue via web, in spite of 'allow-*' settings
Very nice job pinning it down!

Want to put it into a proper bug-report format and submit to MikroTik and this thread, or should I?
I did send a bug report to support couple of months ago, number is mentioned in the post I wrote earlier.
But I think it wouldn't harm if some one else reported it too.
Testing setup with: 2 x RB750UP | 2 x RB750GL | 1 x RB951G-2HnD | 1 x RB2011UiAS-IN
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8318
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: Known issues and bugs - a list

Fri Jul 25, 2014 1:12 am

or should I?
yep, it would be nice =) I'm a bit overloaded with current work...
Russian-speaking forum: https://forum.mikrotik.by/. Welcome!

For every complex problem, there is a solution that is simple, neat, and wrong.

MikroTik. Your life. Your routing.
 
dsobin
Member Candidate
Member Candidate
Posts: 160
Joined: Mon Jun 04, 2007 3:58 am
Location: New Jersey, USA

Re: Known issues and bugs - a list

Sat Jul 26, 2014 7:46 am

Issue:
DHCP over BCP via PPTP fails.

Description:
DHCP over BCP via PPTP fails.
This was reported as a bug previously in this thread, then reported as fixed. I am reporting that it is still broken.
Bridges on each of two routers are connected together via a PPTP tunnel. DHCP server on one bridge, DHCP client on the other bridge. The DHCP client will never get an IP address.

Per the Wiki entry, one should configure IP addresses for the PPTP tunnel endpoints, usually entered in
PPP->Secrets. However, if you do this, DHCP will fail.

If I delete the IP addresses for the PPTP tunnel endpoints, DHCP will work.

If BCP between bridges is all that is required, not including PPTP tunnel endpoint addresses is a work-around.
If you need to also route packets over the PPTP tunnel, then this work-around cannot be used.

It used to work both ways in 5.26. If the new configuration, post 6.x, requires one to delete the IP addresses on the tunnel endpoints, this should be carefully documented and the Wiki updated to reflect this fact.

I think it's just a bug, but maybe Mikrotik wants to call it an undocumented new feature.

If the Mikrotik response is that it's working correctly now (i.e. tunnel endpoint IP addresses MUST be omitted for BCP), then I will update the Wiki page. The Wiki page currently says local/remote addresses must be included, although the example given does not include them.

Versions affected:
This fails consistently in 6.17. It works consistently in 5.24. I don't know where in the 6.x chain it failed.

How to reproduce:
Following is my very simple two router setup. Details are at the end.

Each router is connected via ether1 to my workbench LAN, as 192.168.1.133 and .134.
I'll call them 'left' and 'right'.

Both have a bridge called bridge-tunnel, with no ports. Admin MAC set to 02:AA:AA:AA:AA:AA on the right and 02:BB:BB:BB:BB:BB on the left.

Both bridges are connected via BCP using PPTP.
Left bridge is statically assigned 192.168.40.5/24.
Right bridge is statically assigned 192.168.40.1/24
DHCP server is created on right bridge with pool 192.168.40.100-192.168.40.200.
DHCP client is created on left bridge.

Testing
------
1) Ping from left router to 192.168.40.1
2)Ping from right router to 192.168.40.5
3)Look for left bridge DHCP client to get IP address from right bridge DHCP server.

Results
====
ROS 6.17 Tests 1&2 pass, Test 3 fails
ROS 5.26 Tests 1,2 & 3 always pass.

The configuration was not changed in any way between ROS versions. I tested 6.17, downgraded to 5.24, tested, upgraded to 6.17 again and re-tested.


Notes:
Here are the detailed configurations for the left and right routers.

Left Router:
# jul/25/2014 15:32:08 by RouterOS 6.17
# software id = 4RFY-E9RX
#
/interface bridge
add admin-mac=02:BB:BB:BB:BB:BB auto-mac=no name=bridge-tunnel
/ppp profile
add bridge=bridge-tunnel name=profile-tunnel
/interface pptp-client
add add-default-route=no allow=pap,chap,mschap1,mschap2 connect-to=\
    192.168.1.133 dial-on-demand=no disabled=no keepalive-timeout=60 max-mru=\
    1450 max-mtu=1450 mrru=1600 name=pptp-tunnel password=tunneltest profile=\
    profile-tunnel user=tt
/ip address
add address=192.168.40.5/24 interface=bridge-tunnel network=192.168.40.0
/ip dhcp-client
add default-route-distance=0 dhcp-options=hostname,clientid disabled=no \
    interface=ether1
add default-route-distance=0 dhcp-options=hostname,clientid disabled=no \
    interface=bridge-tunnel use-peer-dns=no use-peer-ntp=no
Right Router:
# jan/02/1970 00:21:04 by RouterOS 6.17
# software id = 8J2K-5ZUR
#
/interface bridge
add admin-mac=02:AA:AA:AA:AA:AA auto-mac=no name=bridge-tunnel priority=0x4000
/ip pool
add name=pool1 ranges=192.168.40.100-192.168.40.200
/ip dhcp-server
add address-pool=pool1 authoritative=yes disabled=no interface=bridge-tunnel \
    name=server1
/ppp profile
add bridge=bridge-tunnel name=profile-tunnel
/interface pptp-server server
set default-profile=profile-tunnel enabled=yes mrru=1600
/ip address
add address=192.168.40.1/24 interface=bridge-tunnel network=192.168.40.0
/ip dhcp-client
add dhcp-options=hostname,clientid disabled=no interface=ether1
/ip dhcp-server network
add address=192.168.40.0/24 gateway=192.168.40.1
/ppp secret
add local-address=192.168.80.1 name=tt password=tunneltest profile=\
    profile-tunnel remote-address=192.168.80.2
Support TicketID:
[Ticket#2014072666000101] RE: DHCP fails over PPTP [...]
Last edited by dsobin on Sat Jul 26, 2014 9:57 pm, edited 2 times in total.
Remember to give karma to all those who help you - Click the "+" box to the left, under "Karma"
 
User avatar
juanvi
Member Candidate
Member Candidate
Posts: 164
Joined: Mon May 05, 2014 6:55 pm
Location: SPAIN

Re: Known issues and bugs - a list

Sat Jul 26, 2014 12:46 pm

User manager minor BUG. I'm running 6.17 user-manager in a RB1100


When i add a sub-admin customer (A customer) and I make his own profiles Works well. I can use its own ("shown as ownner: customer A").


When i make a second (B customer) sub-admin customer all own created profiles are shown as "owner; A customer". BUG!


It seems Works good in each sign-up page but in the user manager is displayed wrong.


The "LIMITATIONS owner field" for the proifiles are displayed well for both cusmomers.


Can you solve it? it wowld be qa headache for ous customers seeing that.


Thanks for a grat product mikrotik.
¡vʞvdnX puv ···SOɹǝʇnoɹ ʞıʇoɹʞıW oʇ sʞuvHʇ
 
User avatar
denisun
Frequent Visitor
Frequent Visitor
Posts: 65
Joined: Wed Jul 16, 2014 6:38 pm
Location: Greece

Re: Known issues and bugs - a list

Tue Jul 29, 2014 6:39 pm

Issue:
Many connection/disconnection of pppoe client when ipv6 is enable and the ether1 (the ether where modem is connecting)

Description:
I have a MikrotikRB951G2HnD. I have a pppoe client and work correctly with ipv4. The ipv6 work correctly but when the ether1 drop (at ether1 i have connect the modem) i have many connection and disconnection for a long time. I noticed the problem when my ISP make changes to DSLAM and ether1 drop. When ipv6 pppoe client is connected i do this test: I change my ether1 speed (in ether1 is connected the modem) (manually drop ether1). Here i have the logs:
http://forum.mikrotik.com/viewtopic.php ... 82#p438609

Versions affected:
ROS 6.15, 6.16, 6.17

How to reproduce:
ISP <=> Modem <=> MT <=> PCs
MT made pppoe client connection with ipv6 enable.
When the connection established, change the speed of ether1.
The ether1 drop and up and the pppoe client connection disconnect and connect again.
But this situation repeated for many times.

Notes:
I made the test with ipv6 setup for my ISP but also with only ipv6 packet enabled and nothing else from my ISP setup enable (eg DHCPv6 client enabled, nd enabled etc).
I have made this test with only ipv4 enabled and i have no problem. The pppoe client disconnect and connect only one time.

Support TicketID:
[Ticket#2014072966000641] RE: PPPoE client problem [...]
"What one programmer can do in one month, two programmers can do in two months."
Fred Brooks...
 
pedropilla
just joined
Posts: 4
Joined: Tue Jun 14, 2011 10:40 pm

Re: Known issues and bugs - a list

Wed Jul 30, 2014 4:08 pm

I'm having same problem about collecting data from simple queues in RB750, and the reboot not worked, apparently the MIB doesnt have the queue OID's:
pedro@pedro-Aspire-E1-572:~/agenda_reboot$ snmpwalk -v2c -cxxxx x.x.x.x
iso.3.6.1.2.1.1.1.0 = STRING: "RouterOS RB750"
iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.14988.1
iso.3.6.1.2.1.1.3.0 = Timeticks: (16616100) 1 day, 22:09:21.00
iso.3.6.1.2.1.1.4.0 = STRING: "NOC"
iso.3.6.1.2.1.1.5.0 = STRING: "Frank Peluffo"
iso.3.6.1.2.1.1.6.0 = STRING: "RIOGRANDE"
iso.3.6.1.2.1.1.7.0 = INTEGER: 78
iso.3.6.1.2.1.2.1.0 = INTEGER: 0
iso.3.6.1.2.1.4.1.0 = INTEGER: 1
iso.3.6.1.2.1.4.2.0 = INTEGER: 255
iso.3.6.1.2.1.4.24.3.0 = Gauge32: 4
iso.3.6.1.2.1.17.2.1.0 = INTEGER: 3
iso.3.6.1.2.1.25.1.1.0 = Timeticks: (16616100) 1 day, 22:09:21.00
iso.3.6.1.2.1.25.1.2.0 = Hex-STRING: 07 DE 07 1E 0A 00 30 00 2D 03 00
iso.3.6.1.2.1.25.2.2.0 = INTEGER: 32768
iso.3.6.1.2.1.25.2.3.1.1.65536 = INTEGER: 65536
iso.3.6.1.2.1.25.2.3.1.1.131073 = INTEGER: 131073
iso.3.6.1.2.1.25.2.3.1.2.65536 = OID: iso.3.6.1.2.1.25.2.1.1
iso.3.6.1.2.1.25.2.3.1.2.131073 = OID: iso.3.6.1.2.1.25.2.1.4
iso.3.6.1.2.1.25.2.3.1.3.65536 = STRING: "main memory"
iso.3.6.1.2.1.25.2.3.1.3.131073 = STRING: "disk: system"
iso.3.6.1.2.1.25.2.3.1.4.65536 = INTEGER: 1024
iso.3.6.1.2.1.25.2.3.1.4.131073 = INTEGER: 1024
iso.3.6.1.2.1.25.2.3.1.5.65536 = INTEGER: 32768
iso.3.6.1.2.1.25.2.3.1.5.131073 = INTEGER: 61440
iso.3.6.1.2.1.25.2.3.1.6.65536 = INTEGER: 22176
iso.3.6.1.2.1.25.2.3.1.6.131073 = INTEGER: 10764
iso.3.6.1.2.1.25.2.3.1.7.65536 = Counter32: 0
iso.3.6.1.2.1.25.2.3.1.7.131073 = Counter32: 0
iso.3.6.1.2.1.25.3.2.1.1.1 = INTEGER: 1
iso.3.6.1.2.1.25.3.2.1.2.1 = OID: iso.3.6.1.2.1.25.3.1.3
iso.3.6.1.2.1.25.3.3.1.1.1 = OID: ccitt.0
iso.3.6.1.2.1.25.3.3.1.2.1 = INTEGER: 100
iso.3.6.1.2.1.47.1.1.1.1.1.65536 = INTEGER: 65536
iso.3.6.1.2.1.47.1.1.1.1.1.262145 = INTEGER: 262145
iso.3.6.1.2.1.47.1.1.1.1.2.65536 = STRING: "RouterOS 6.17 on RB750"
iso.3.6.1.2.1.47.1.1.1.1.2.262145 = STRING: "Linux 3.3.5 ehci_hcd RB400 EHCI"
iso.3.6.1.2.1.47.1.1.1.1.3.65536 = OID: ccitt.0
iso.3.6.1.2.1.47.1.1.1.1.3.262145 = OID: ccitt.0
iso.3.6.1.2.1.47.1.1.1.1.4.65536 = INTEGER: 0
iso.3.6.1.2.1.47.1.1.1.1.4.262145 = INTEGER: 65536
iso.3.6.1.2.1.47.1.1.1.1.5.65536 = INTEGER: 3
iso.3.6.1.2.1.47.1.1.1.1.5.262145 = INTEGER: 2
iso.3.6.1.2.1.47.1.1.1.1.6.65536 = INTEGER: -1
iso.3.6.1.2.1.47.1.1.1.1.6.262145 = INTEGER: -1
iso.3.6.1.2.1.47.1.1.1.1.7.65536 = STRING: "MIPS 24Kc V7.4"
iso.3.6.1.2.1.47.1.1.1.1.7.262145 = STRING: "1:1"
iso.3.6.1.2.1.47.1.1.1.1.8.65536 = ""
iso.3.6.1.2.1.47.1.1.1.1.8.262145 = ""
iso.3.6.1.2.1.47.1.1.1.1.9.65536 = ""
iso.3.6.1.2.1.47.1.1.1.1.9.262145 = ""
iso.3.6.1.2.1.47.1.1.1.1.10.65536 = ""
iso.3.6.1.2.1.47.1.1.1.1.10.262145 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.65536 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.262145 = STRING: "rb400_usb"
iso.3.6.1.2.1.47.1.1.1.1.12.65536 = ""
iso.3.6.1.2.1.47.1.1.1.1.12.262145 = STRING: "0x1d6b"
iso.3.6.1.2.1.47.1.1.1.1.13.65536 = ""
iso.3.6.1.2.1.47.1.1.1.1.13.262145 = STRING: "0x0002"
iso.3.6.1.2.1.47.1.1.1.1.14.65536 = ""
iso.3.6.1.2.1.47.1.1.1.1.14.262145 = ""
iso.3.6.1.2.1.47.1.1.1.1.15.65536 = ""
iso.3.6.1.2.1.47.1.1.1.1.15.262145 = ""
iso.3.6.1.2.1.47.1.1.1.1.16.65536 = INTEGER: 2
iso.3.6.1.2.1.47.1.1.1.1.16.262145 = INTEGER: 2
iso.3.6.1.2.1.9999.1.1.1.1.0 = STRING: "MikroTik DHCP server"
iso.3.6.1.2.1.9999.1.1.1.2.0 = OID: iso.3.6.1.4.1.14988.1
iso.3.6.1.2.1.9999.1.1.6.4.1.4.192.168.1.100 = INTEGER: 2
iso.3.6.1.2.1.9999.1.1.6.4.1.4.192.168.1.101 = INTEGER: 2
iso.3.6.1.2.1.9999.1.1.6.4.1.4.192.168.1.102 = INTEGER: 2
iso.3.6.1.2.1.9999.1.1.6.4.1.4.192.168.1.103 = INTEGER: 2
iso.3.6.1.2.1.9999.1.1.6.4.1.4.192.168.1.105 = INTEGER: 2
iso.3.6.1.2.1.9999.1.1.6.4.1.4.192.168.1.106 = INTEGER: 2
iso.3.6.1.2.1.9999.1.1.6.4.1.4.192.168.1.108 = INTEGER: 2
iso.3.6.1.2.1.9999.1.1.6.4.1.5.192.168.1.100 = Gauge32: 186706
iso.3.6.1.2.1.9999.1.1.6.4.1.5.192.168.1.101 = Gauge32: 231869
iso.3.6.1.2.1.9999.1.1.6.4.1.5.192.168.1.102 = Gauge32: 258959
iso.3.6.1.2.1.9999.1.1.6.4.1.5.192.168.1.103 = Gauge32: 256089
iso.3.6.1.2.1.9999.1.1.6.4.1.5.192.168.1.105 = Gauge32: 254832
iso.3.6.1.2.1.9999.1.1.6.4.1.5.192.168.1.106 = Gauge32: 204265
iso.3.6.1.2.1.9999.1.1.6.4.1.5.192.168.1.108 = Gauge32: 254738
iso.3.6.1.2.1.9999.1.1.6.4.1.7.192.168.1.100 = INTEGER: 3
iso.3.6.1.2.1.9999.1.1.6.4.1.7.192.168.1.101 = INTEGER: 3
iso.3.6.1.2.1.9999.1.1.6.4.1.7.192.168.1.102 = INTEGER: 3
iso.3.6.1.2.1.9999.1.1.6.4.1.7.192.168.1.103 = INTEGER: 3
iso.3.6.1.2.1.9999.1.1.6.4.1.7.192.168.1.105 = INTEGER: 3
iso.3.6.1.2.1.9999.1.1.6.4.1.7.192.168.1.106 = INTEGER: 3
iso.3.6.1.2.1.9999.1.1.6.4.1.7.192.168.1.108 = INTEGER: 3
iso.3.6.1.2.1.9999.1.1.6.4.1.8.192.168.1.100 = Hex-STRING: 00 25 AB 01 B3 5F
iso.3.6.1.2.1.9999.1.1.6.4.1.8.192.168.1.101 = Hex-STRING: 9C 20 7B D9 6D A1
iso.3.6.1.2.1.9999.1.1.6.4.1.8.192.168.1.102 = Hex-STRING: 18 34 51 21 2D 92
iso.3.6.1.2.1.9999.1.1.6.4.1.8.192.168.1.103 = Hex-STRING: 48 5D 60 4B 86 7B
iso.3.6.1.2.1.9999.1.1.6.4.1.8.192.168.1.105 = Hex-STRING: E0 B9 A5 F3 38 BC
iso.3.6.1.2.1.9999.1.1.6.4.1.8.192.168.1.106 = Hex-STRING: 14 99 E2 7A 2F 12
iso.3.6.1.2.1.9999.1.1.6.4.1.8.192.168.1.108 = Hex-STRING: F0 C1 F1 97 D2 D9
 
dsobin
Member Candidate
Member Candidate
Posts: 160
Joined: Mon Jun 04, 2007 3:58 am
Location: New Jersey, USA

Re: Known issues and bugs - a list

Thu Jul 31, 2014 8:18 pm

Issue:
DHCP over BCP via PPTP fails.

Description:
DHCP over BCP via PPTP fails.
This was reported as a bug previously in this thread, then reported as fixed. I am reporting that it is still broken.
Bridges on each of two routers are connected together via a PPTP tunnel. DHCP server on one bridge, DHCP client on the other bridge. The DHCP client will never get an IP address.

Per the Wiki entry, one should configure IP addresses for the PPTP tunnel endpoints, usually entered in
PPP->Secrets. However, if you do this, DHCP will fail.

If I delete the IP addresses for the PPTP tunnel endpoints, DHCP will work.

If BCP between bridges is all that is required, not including PPTP tunnel endpoint addresses is a work-around.
If you need to also route packets over the PPTP tunnel, then this work-around cannot be used.

It used to work both ways in 5.26. If the new configuration, post 6.x, requires one to delete the IP addresses on the tunnel endpoints, this should be carefully documented and the Wiki updated to reflect this fact.

I think it's just a bug, but maybe Mikrotik wants to call it an undocumented new feature.

If the Mikrotik response is that it's working correctly now (i.e. tunnel endpoint IP addresses MUST be omitted for BCP), then I will update the Wiki page. The Wiki page currently says local/remote addresses must be included, although the example given does not include them.
Mikrotik responded to my ticket by saying it's a feature. A PPTP tunnel can be used either for routing traffic or for bridging, but not both.

If used for bridging, the local and remote IP addresses assigned to the tunnel endpoints, usually in in the "Secrets" tab, must NOT be entered.
This is a change from the way it worked in v5.x.

The Wiki for BCP says to always enter IP addresses for the tunnel endpoints, even for bridging. This is wrong, and if followed, the tunnel will not work properly for bridging.

I am willing to update the BCP wiki, but my wiki user ID doesn't have the privilege to do that.

MIkrotik: If you allow it, I'll update the Wiki. Otherwise, I hope you will update it. I responded this way via the ticket.

Since Mikrotik says this is working properly, I guess it's not a bug in the software - It's a bug in the documentation.
Remember to give karma to all those who help you - Click the "+" box to the left, under "Karma"
 
Dudshl
just joined
Posts: 2
Joined: Wed Apr 02, 2014 5:27 am

Re: Known issues and bugs - a list

Mon Aug 11, 2014 11:29 am

Issue:
RouterBoard with 4G modem crashes when I try to start Metarouter with OpenWRT image.

Description:
Step 1: Import openwrt image to metarouter (I got in from official wiki http://www.mikrotik.com/download/metaro ... rootfs.tgz and tried to compile it manually).
It starts and works correctly.
Step 2: Connect 4G modem (ZTE MF823, YOTA, Huawei E3272) -> system crashes and rebooting while modem connected.
When I disconnect modem - system boots correctly
Step 3: Disable Metarouter.
System works correctly.
Step 4: Connect 4G modem.
System works correctly.
Step 5: Enable Metarouter (or import new one) -> system crashes and rebooting while modem connected.

Same thing happens if I create Metarouter without any images. Just clean metarouter with routeros.

PS1: I tried to use to use Huawei e3272 with mode AT^SETPORT="A1;10,12,13,14,16" (all com ports without CD and SD)
In this configuration it works correctly.4G + metarouter = success.

PS2: ZTE MF823 in diagnostic mode (http://192.168.0.1/goform/goform_proces ... md=FACTORY) detects and works correctly with metarouter. But there is no way to make connection with internet using this mode.
ZTE MF823 in diagnostic mode + metarouter = success

There is only "System rebooted because of kernel failure" string in logs.

Versions affected:
RB2011UAS-IN, RB951Ui-2HnD
6.17,6.18

Ticket#2014081166000486
 
Majklik
newbie
Posts: 35
Joined: Fri Dec 23, 2011 10:20 pm

Re: Known issues and bugs - a list

Mon Oct 06, 2014 11:41 am

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.
There is workaround for this problem. You can define the bond with manual mtu size 1508 bytes and then maybe this will works with PPPoE.
A definition like:
/interface bonding
add lacp-rate=1sec mode=802.3ad name="lacp1 - ether4, ether5" slaves="ether4 - to swch,ether5 - to swch" mtu=1508
But you must use this bond only for PPPoE, if you assign IP to it then you'll have a problem with this manual MTU.
There is similar problem if is defined VLANs on top of the bond. So I use mtu=1504 to bypass this (or mtu=1508 if is used QinQ on top of the bonding interface.
 
FabioT
just joined
Posts: 2
Joined: Wed Sep 17, 2014 10:23 am

Re: Known issues and bugs - a list

Mon Oct 06, 2014 4:49 pm

Issue:
GPS menù item is not displayed in web configuration page

Description:
CSR109-8G-2HnD-IN Cloud Router Switch.
The Router OS is upgraded to version 6.20
GPS Package installed (ver. 6.20)

Using WinBox or Router configuration webpage:
In the left menu: System the GPS menù item is not displayed.

The GPS driver seem to be configurable using 'Terminal' utility.
 
Majklik
newbie
Posts: 35
Joined: Fri Dec 23, 2011 10:20 pm

Re: Known issues and bugs - a list

Mon Oct 06, 2014 6:33 pm

Issue:
The multihop BFD do not works.

Description:
If is configured multihop BGP connection with BFD support then it do not works. The problem is that is not used correct source IP address of the BFD packets (as is defined with update-source=X) but IP address of the outgoing interface.

Versions affected:
Detected with ROS6.6, now checked with 6.20.

How to reproduce:
Two routers connected with ether1 interface together.
Both routers have defined bridge-loopback and multihop BGP session with BFD support between them. There is too used OSPF for route distribution which uses link BFD too.

R1:
/system identity  set name=R1
/interface bridge
add admin-mac=02:00:00:00:00:01 auto-mac=no mtu=1500 name=bridge-loopback protocol-mode=none
/ip address
add address=192.168.1.1/24 interface=ether1 network=192.168.1.0
add address=192.168.0.1/32 interface=bridge-loopback network=192.168.0.1
/routing bfd interface
set [ find default=yes ] interval=2s min-rx=2s
add interface=ether1
/routing ospf instance
set [ find default=yes ] router-id=192.168.0.1
/routing ospf interface
add cost=1 interface=bridge-loopback network-type=point-to-point passive=yes
add interface=ether1 network-type=point-to-point use-bfd=yes
/routing ospf network
add area=backbone network=192.168.0.0/16
/routing bgp instance
set default client-to-client-reflection=no router-id=192.168.0.1
/routing bgp network
add network=192.168.2.0/24 synchronize=no
/routing bgp peer
add multihop=yes name=R1-R2 remote-address=192.168.0.2 remote-as=65530 ttl=\
    default update-source=192.168.0.1 use-bfd=yes
R2:
/system identity set name=R2
/interface bridge
add admin-mac=02:00:00:00:00:01 auto-mac=no mtu=1500 name=bridge-loopback protocol-mode=none
/ip address
add address=192.168.1.2/24 interface=ether1 network=192.168.1.0
add address=192.168.0.2/32 interface=bridge-loopback network=192.168.0.2
/routing bfd interface
set [ find default=yes ] interval=2s min-rx=2s
add interface=ether1
/routing ospf instance
set [ find default=yes ] router-id=192.168.0.2
/routing ospf interface
add cost=1 interface=bridge-loopback network-type=point-to-point passive=yes
add interface=ether1 network-type=point-to-point use-bfd=yes
/routing ospf network
add area=backbone network=192.168.0.0/16
/routing bgp instance
set default client-to-client-reflection=no router-id=192.168.0.2
/routing bgp network
add network=192.168.3.0/24 synchronize=no
/routing bgp peer
add multihop=yes name=R1-R2 remote-address=192.168.0.1 remote-as=65530 ttl=\
    default update-source=192.168.0.2 use-bfd=yes

Notes:
This problem have workaround for IPv4 with SRCNAT:
R1:
/ip firewall nat
add action=src-nat chain=srcnat dst-address=192.168.0.2 dst-port=4784 \
    protocol=udp to-addresses=192.168.0.1
R2:
/ip firewall nat
add action=src-nat chain=srcnat dst-address=192.168.0.1 dst-port=4784 \
    protocol=udp to-addresses=192.168.0.2
Second method is to set prefered source IP with filters if is used OSPF in conjunction with BGP.
The same problem have IPv6 multihop BFD if there is configured global IPv6 address on the ether1.
Different way for fast link break detection is to change hold/keepalive timers of the BGP peer.

When is activated multihop BFD without workaround then it breaks link BFD for OSPF too in this configuration. So BFD status looks like:
[admin@R1] > /routing bfd neighbor print 
Flags: U - up 
 #   INTERFACE                      ADDRESS          PROTOCOLS  MULTIHOP STATE 
[admin@R1] >

[admin@R2] > /routing bfd neighbor print 
Flags: U - up 
 #   INTERFACE                      ADDRESS          PROTOCOLS  MULTIHOP STATE 
 0   ether1                         192.168.1.1      ospf       no       down  
 1   unspecified                    192.168.0.1      bgp        yes      down  
[admin@R2] > 
When is workaround applied then this output shows:
[admin@R1] > /routing bfd neighbor print 
Flags: U - up 
 #   INTERFACE                        ADDRESS          PROTOCOLS  MULTIHOP STATE 
 0 U ether1                           192.168.1.2      ospf       no       up    
 1 U unspecified                      192.168.0.2      bgp        yes      up    
[admin@R1] > 

[admin@R2] > /routing bfd neighbor print 
Flags: U - up 
 #   INTERFACE                        ADDRESS          PROTOCOLS  MULTIHOP STATE 
 0 U ether1                           192.168.1.1      ospf       no       up    
 1 U unspecified                      192.168.0.1      bgp        yes      up    
[admin@R2] > 
Support TicketID:
[Ticket#2013110666000642]
Mikrotik answer: There are bugs and currently it doe snot work properly, avoid using multihop BFD.
 
meetriks2
newbie
Posts: 25
Joined: Wed May 07, 2014 12:18 am

Re: Known issues and bugs - a list

Wed Oct 08, 2014 10:06 am

Issue:
Can't add any DHCP options with v6.x

Description:
I need DHCP options to tell Thinclients where to find the FTP server with the thinclient configurartion file.

Versions affected:
At least 6.12,6.13,6.15,6.20
Works on v5.26

How to reproduce:

ros code

[admin@xxxx] > system resource print
                   uptime: 5d20h41m50s
                  version: 6.20
               build-time: Oct/01/2014 10:06:12
              free-memory: 70.0MiB
             total-memory: 122.9MiB
                      cpu: Intel(R)
                cpu-count: 1
            cpu-frequency: 2128MHz
                 cpu-load: 1%
           free-hdd-space: 9.7GiB
          total-hdd-space: 9.8GiB
  write-sect-since-reboot: 23676
         write-sect-total: 23676
        architecture-name: x86
               board-name: x86
                 platform: MikroTik
[admin@xxxx] > ip dhcp-server option add name=OPTION1 value=192.168.1.1 code=161
failure: Unknown data type!
[admin@xxxx] > ip dhcp-server option add name=OPTION1 value=username code=184           
failure: Unknown data type!
Notes:
Example on V5.26

ros code

[admin@xxxx] > /system resource print
                   uptime: 35w6d10h16m48s
                  version: 5.26
              free-memory: 6872KiB
             total-memory: 28284KiB
                      cpu: Intel(R)
                cpu-count: 1
            cpu-frequency: 3059MHz
                 cpu-load: 1%
           free-hdd-space: 10122156KiB
          total-hdd-space: 10310772KiB
  write-sect-since-reboot: 2562062
         write-sect-total: 2562062
        architecture-name: x86
               board-name: x86
                 platform: MikroTik
[admin@xxx] > ip dhcp-server option add name=OPTION1 value=192.168.1.1 code=161
[admin@xxx] > ip dhcp-server option add name=OPTION2 value=username code=184

Support TicketID:
will update when i got a ticketid.
 
DLNoah
Member Candidate
Member Candidate
Posts: 144
Joined: Fri Nov 12, 2010 5:33 pm

Re: Known issues and bugs - a list

Wed Oct 08, 2014 11:43 am

Issue:
Can't add any DHCP options with v6.x
The issue is mostly your configuration -- as of v6, the DHCP server is more picky about types matching what the DHCP Option is "supposed" to have.

In the case of a string-literal option like the TFTP boot option 161, you need to put the option in double quotes outside of single quotes...

So, basically:
ip dhcp-server option add name=OPTION1 value="'192.168.1.1'" code=161
The outer double-quotes is to tell ROS to take what you're putting in the quotes literally, and the inner single-quotes is to use a string value.

If you use the Winbox GUI to add the option, you only need the single-quotes -- you don't need the outer double-quotes from the GUI.
 
User avatar
janisk
MikroTik Support
MikroTik Support
Posts: 6283
Joined: Tue Feb 14, 2006 9:46 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Thu Oct 09, 2014 12:32 pm

it seems that in this particular case value has to be s'192.168.1.1' as previously string was blindly taken apart and each character replaced by its ASCII number.

now string is correctly entered in single quotes, however there is the special case when quotes have ipv4 address in those,. Then this is recognized as an ip address and correct hex representation of ip address is used instead.

IMO it is well described in the manual.

Also, it is always possible to use proper notation for 5.x in 6.x configuration value=0xHEXNUMBER
 
Zeitkind
just joined
Posts: 5
Joined: Sat Jul 05, 2014 1:36 pm

Re: Known issues and bugs - a list

Thu Oct 23, 2014 10:08 am

Issue:
Kernel panic when using AFP-connections over VPN/L2TP.

Description:
A client, usually a machine with Mac OS X, connects to a RB2011 via ipsec/L2TP. Then mounts a remote AFP-share (AFP = Apple Filing Protocol over TCP/IP) and copies several MB. Usually after ~20-100MB of data the RB panics and resets.
No problems when using SMB.

Version affected:
Up to 6.19; didn't test 6.20 yet

How to reproduce:
see above

Support TicketID:
#2014070766000209

Was a kinda DoS-situation, because some users tried to transfer some files over and over again and several RBs kept crashing & rebooting. Replaced all RBs for now and stopped to deploy more. Mikrotik support unwilling to fix, because AFP is said to be deprecated.
 
arxont
just joined
Posts: 9
Joined: Fri Nov 02, 2012 11:45 am

Re: Known issues and bugs - a list

Sun Oct 26, 2014 5:09 am

pls update timezones :D
 
madmax
just joined
Posts: 6
Joined: Thu Apr 24, 2014 2:20 pm

Re: Known issues and bugs - a list

Tue Oct 28, 2014 1:13 pm

Hi all,
this bug affected my CCR1016-12G , I tryed all routerOS and all firmware, the last used is rOS 6.20 and fw 3.19

My configuration is very simple only 2 ethernet ports enable, pptp server ,only one profile with a rate limit

4 Mbits download and 512 Kbits upload, I notice that if the user costantly reach the limit (download or uplad)

after some hours broke the limit , the only way to fix this bug is to reboot the ccr.
 
moneron
Trainer
Trainer
Posts: 3
Joined: Wed Oct 29, 2014 2:16 pm

Re: Known issues and bugs - a list

Wed Oct 29, 2014 2:24 pm

Hi, support! I found a little bug. When i configure dhcp-client and set "Add default route" to "special-classles", the "default route distance" textbox goes to inactive. But using terminal set 0 add-default-route=special-classless default-route-distance=20 works properly. RouterOS 6.20. Can you solve the problem in next version?
 
moneron
Trainer
Trainer
Posts: 3
Joined: Wed Oct 29, 2014 2:16 pm

Re: Known issues and bugs - a list

Wed Oct 29, 2014 2:26 pm

Hi, support! I found a little bug. When i configure dhcp-client and set "Add default route" to "special-classles", the "default route distance" textbox goes to inactive. But using terminal set 0 add-default-route=special-classless default-route-distance=20 works properly. RouterOS 6.20. Can you solve the problem in next version?
 
urosg
just joined
Posts: 21
Joined: Mon Nov 21, 2011 2:27 pm

Re: Known issues and bugs - a list

Thu Oct 30, 2014 2:30 pm

Issue:
Router crashes and reboots after setting NTP client with dns names without internet connection or DNS servers set

Versions:
6.18+ (tested on CCR1009 and RB2011)

Description:
A router installation without DNS servers set or without an active internet connection and while issuing command:
/system ntp client set enabled=yes server-dns-names=si.pool.ntp.org
the router hangs and reboots.
The same happens if you set this with a working internet connection so that it saves the config and if the router loses power and after it initialized and the internet connection is not active yet the router will loop hang/reboot.
When using a fixed IP address for the NTP Client this problem doesn't appear.
 
hmoghani
just joined
Posts: 6
Joined: Thu Oct 30, 2014 9:39 pm

Re: Known issues and bugs - a list

Fri Oct 31, 2014 4:22 pm

I'm trying to use Mikrotik routerboard as a L2TP client to a l2tp server. But I haven't been able to connect to it. when I add the L2TP client and the IPSEC config, it says "connecting..." but it doesn't even check for username password.... I had similar issue when I wanted to use windows as a L2TP client, but it got fixed with a registry tweak I found at Microsoft.com . So with the same Internet connection I can connect to the VPN with windows, but can't connect to it when I use my Mikrotik routerboard (RB751U).

I attached the logs
You do not have the required permissions to view the files attached to this post.
 
gloriatorios
just joined
Posts: 2
Joined: Tue Dec 09, 2014 9:14 am
Contact:

Re: Known issues and bugs - a list

Tue Dec 09, 2014 9:33 am

is it known bugs?
1. x86.when moving vlan from ethernet interface which is in bonging to bonding interface router freazes? - It can be repeated on any x86 box with defaut config.Cant generate supout file because router freezes.
How to repeat:
/interface vlan add name=vlan1 vlan-id=1 interface=eth1
/interface vlan add name=vlan2 vlan-id=2 interface=eth1
 
sdugoten
Frequent Visitor
Frequent Visitor
Posts: 63
Joined: Wed Aug 04, 2010 7:55 pm

Re: Known issues and bugs - a list

Thu Dec 25, 2014 12:19 pm

PPTP VPN connection issue:

Ticket Number:
[Ticket#2014122566000139]

Post reference:
http://forum.mikrotik.com/viewtopic.php?f=2&t=92459

Description:
PPTP client VPN connection throw "LCP received ProtRej for unsupported protocol" error message after 30 minutes connection

RouterOS version:
v6.23.1 on X86

How to reproduce:
Create a PPTP client VPN connection and connect to *any* paid PPTP VPN service. After seeing any video online continuously for around 30 minutes, the video will stop, Winbox Interface window will show no activity on the PPTP client connection, but it is still in connected status.

Log will show this:

Image


I can reproduce this on every single paid VPN service provider that offer PPTP connection. It seems it will only happen when you use the VPN for watching video or large data download continuously for more than 30 mins.
 
User avatar
drixter
newbie
Posts: 26
Joined: Mon May 19, 2008 10:10 pm
Location: Warsaw, PL
Contact:

Re: Known issues and bugs - a list

Thu Dec 25, 2014 4:54 pm

Issue:
Route cache overflow (x86/any)

Description:
When you have a 6to4, ipsec, gre or sstp tunnels your route will oveflow and stops IPv4 traffic. Reboot is only resolution. More information on the "How to reproduce" part.

Versions affected:
6+ till 6.25rc7

How to reproduce:
http://forum.mikrotik.com/viewtopic.php ... 6&p=461024

Notes:
Fixed in 6.25rc7.

Support TicketID:
[Ticket#2014101766000756]
Last edited by drixter on Thu Jan 15, 2015 8:47 pm, edited 1 time in total.
--
Marcin Gondek / Drixter
http://drixter.e-utp.net
 
AlAraf
just joined
Posts: 10
Joined: Sun Dec 01, 2013 8:13 pm

Re: Known issues and bugs - a list

Mon Jan 12, 2015 9:34 pm

Issue:
Email Start TLS checbox not saved.

Description:
Every time I set e-mail configuration via WinBox in Tools / Email Settings and tick “Start TLS” checkbox, then exit from WinBox and open it again checkbox next to “Start TLS” is not ticked.
I tested it on several RouterBoards and result is the same.

Versions affected:
MikroTik RouterOS 6.24

How to reproduce:
1) Login to WinBox.
2) Go to Tools / Email Settings .
3) Configure all settings (Server, port, from, user, password).
4) Tick "Start TLS" checkbox , press OK button and exit winBox.
5) Open WinBox again, go to Go to Tools / Email Settings and see that "Start TLS" checkbox is not ticked.

Notes:
None.

Support TicketID:
Not yet available.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8318
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: Known issues and bugs - a list

Tue Jan 13, 2015 1:38 pm

Every time I set e-mail configuration via WinBox in Tools / Email Settings and tick “Start TLS” checkbox, then exit from WinBox and open it again checkbox next to “Start TLS” is not ticked.
seems like it's because 'start-tls' has three values: "no", "tls-only", "yes" - and Winbox supports only checkbox currently :)
Russian-speaking forum: https://forum.mikrotik.by/. Welcome!

For every complex problem, there is a solution that is simple, neat, and wrong.

MikroTik. Your life. Your routing.
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24266
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Known issues and bugs - a list

Tue Jan 13, 2015 2:13 pm

tls winbox issue already fixed in new RC
No answer to your question? How to write posts
 
AlAraf
just joined
Posts: 10
Joined: Sun Dec 01, 2013 8:13 pm

Re: Known issues and bugs - a list

Tue Jan 13, 2015 3:04 pm

tls winbox issue already fixed in new RC
Are you talking about new RouterOS 6.25 RC or new WinBox 3 RC?

When will it be available for download?
 
mitry
just joined
Posts: 22
Joined: Tue Jun 26, 2012 10:06 pm

Re: Known issues and bugs - a list

Tue Jan 13, 2015 3:46 pm

Very stupid bugs which reducing functionality of router, Mikrotik disappointing more and more..
I found something like this almost every month and support always says something like 'We will fix in future'.
When this 'future' finaly happens??

http://forum.mikrotik.com/viewtopic.php?f=2&t=92996
http://forum.mikrotik.com/viewtopic.php?f=2&t=92590
 
User avatar
giallone
just joined
Posts: 23
Joined: Mon Mar 24, 2014 12:21 am

Re: Known issues and bugs - a list

Wed Jan 14, 2015 1:01 am

Hi all,
I am trying to dinamically assign IP ADDRESS by DHCP to a interface to use as gateway in some ROUTES.
In /ip routes add gateway, if the name of the interface is a PPP one the IP address is retrieved in a right way, when the interface is any ethernet I absolutely need to write the right IP address, while the interface name will not work as gateway.

Is this a known issue, or amI wrong with some configuration?

This topic explains better my needs:

http://wiki.mikrotik.com/wiki/Routing_v ... ed_gateway
Regards.

Luca
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8318
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: Known issues and bugs - a list

Wed Jan 14, 2015 4:36 am

Is this a known issue, or amI wrong with some configuration?
you are wrong. when you set gateway=interface, packet is sent from the interface directly to the connected network. if it's p2p tunnel, packet has only one way - the remote peer. but in case of broadcast interfaces (like Ethernet), router needs to know the MAC address of target (gateway MAC address).

the only workaround is to enable ARP Proxy on the gateway, but correct way is to set gateway IP address in /ip route
Russian-speaking forum: https://forum.mikrotik.by/. Welcome!

For every complex problem, there is a solution that is simple, neat, and wrong.

MikroTik. Your life. Your routing.
 
User avatar
agrisvv
just joined
Posts: 18
Joined: Sun Oct 14, 2012 6:36 pm
Location: LATVIA

Re: Known issues and bugs - a list

Wed Jan 21, 2015 9:01 pm

i want to write one bug, I upgrade to 6.25.
Ater upgrade cant connect to sstp vpn.
In attach are debug image.
IN windows 8.1 show something about "remote port closed"

Test mikrotik to mikrotik sstp - all work fine.
So i downgrade to 6.24.
no mater powerpc or mipsbe.
You do not have the required permissions to view the files attached to this post.
 
hechz
just joined
Posts: 16
Joined: Fri Jan 23, 2015 1:36 pm

Re: Known issues and bugs - a list

Fri Jan 23, 2015 1:52 pm

Issue: WiFI Throughput is reduced by 1/6th unless logged into webfig. Any thoughts on what could possibly cause this would be appreciated.
RouterBoard Details:
routerboard: yes
model: 951Ui-2HnD
serial-number: «redacted»
current-firmware: 3.19
upgrade-firmware: 3.19
current-version: 6.25
latest-version: 6.25
status: System is already up to date
uptime: 18m41s
version: 6.25
build-time: Jan/19/2015 10:11:08
free-memory: 100.8MiB
total-memory: 128.0MiB
cpu: MIPS 74Kc V4.12
cpu-count: 1
cpu-frequency: 600MHz
cpu-load: 3%
free-hdd-space: 109.7MiB
total-hdd-space: 128.0MiB
write-sect-since-reboot: 619
write-sect-total: 1656604
bad-blocks: 0%
architecture-name: mipsbe
board-name: RB951Ui-2HnD
platform: MikroTik

Speet Test results while unauthentucated:
Download Speed: 8433 kbps (1054.1 KB/sec transfer rate)
Upload Speed: 5737 kbps (717.1 KB/sec transfer rate)
Latency: 7 ms
Jitter: 11 ms

Speed Test results while Authenticated:
Download Speed: 50785 kbps (6348.1 KB/sec transfer rate)
Upload Speed: 5793 kbps (724.1 KB/sec transfer rate)
Latency: 10 ms
Jitter: 8 ms
 
dnyl
Frequent Visitor
Frequent Visitor
Posts: 55
Joined: Thu Jan 07, 2010 2:57 am
Location: Budapest, Hungary
Contact:

Re: Known issues and bugs - a list

Fri Feb 13, 2015 12:18 am

Is there a way to install a Mikrotik to a brand new server which include ssd?

We bought a brand new ASUS RS100-X7/PI2 server, but impossible mission to install a Mikrotik to this server. This is our second server, which unusable with Mikrotik.

This server contains a 30 GB SSD, but the install hangs on hard drive search option.
We try lot of option: AHCI mode, IDE mode, RAID mode, Netinstall to server, Netinstall to a SSD drive through windows7 docking station, usb boot. Nothing can work.

Is the a way to use modern 3rd party hardware to use mikrotik, or we need to buy an unstable CCR?

We want a quick reply, because we spent a lot of money to modern hardwares, but RouterOS can't support new systems.

:evil: :evil: :evil:
 
dnyl
Frequent Visitor
Frequent Visitor
Posts: 55
Joined: Thu Jan 07, 2010 2:57 am
Location: Budapest, Hungary
Contact:

Re: Known issues and bugs - a list

Mon Feb 16, 2015 5:36 pm

Is there a way to install a Mikrotik to a brand new server which include ssd?

We bought a brand new ASUS RS100-X7/PI2 server, but impossible mission to install a Mikrotik to this server. This is our second server, which unusable with Mikrotik.

This server contains a 30 GB SSD, but the install hangs on hard drive search option.
We try lot of option: AHCI mode, IDE mode, RAID mode, Netinstall to server, Netinstall to a SSD drive through windows7 docking station, usb boot. Nothing can work.

Is the a way to use modern 3rd party hardware to use mikrotik, or we need to buy an unstable CCR?

We want a quick reply, because we spent a lot of money to modern hardwares, but RouterOS can't support new systems.

:evil: :evil: :evil:
What about this?
We sent a mail to support: Ticket#2015021666000351
 
leroylim
just joined
Posts: 21
Joined: Tue Aug 07, 2012 7:57 am

Re: Known issues and bugs - a list

Sat Mar 14, 2015 6:18 am

Issue:
Commenting BGP peer when BGP session is established causes BGP to reconnect.

Description:
When I have a BGP peer that is established. And I put a comment in BGP peer. BGP session with peers reconnects.

Versions affected:
MikroTik RouterOS 6.27, 6.28rc11

How to reproduce:
1) Login to WinBox.
2) Have a established BGP peer.
3) Go to Routing -> BGP -> Peers
4) Put in a comment / change the peer's comment via Ctrl C.
5) Peer state immediately goes to active.

Notes:
None.

Support TicketID:
Not yet available.
 
kburzyns
just joined
Posts: 14
Joined: Mon Mar 09, 2015 8:50 am

Re: Known issues and bugs - a list

Wed Mar 18, 2015 12:45 pm

 
Smurv
just joined
Posts: 1
Joined: Wed Apr 29, 2015 12:06 pm

INPUT connection terminate trough IPSEC NAT tunnel [SOLVED]

Wed Apr 29, 2015 12:42 pm

Issue:
INPUT connection terminate trough IPSEC NAT tunnel - [SOLVED] - see end of the post

Description:
I have 2 Mikrotik routers connected trough IPSEC tunnel with one side behind NAT. IPSEC tunnel is working properly - I can ping both routers, I can ping machines behind routers, I can connect to machines behind routers (by SSH for example). But one thing doesn't work - I can't connect "internally" trough IPSEC tunnel to router behind NAT. For example Winbox - connection is established (I can see "user logged in from x.x.x.x. via winbox"), but then is terminated - everything in Winbox is empty and after a few seconds I get "router disconnected" message.

I can see the connection in firewall tracking on both sides as "established" at start, but then it just ends (after "router disconnected" message from Winbox).

I have 6 Mikrotik routers - two of them are behind NAT. They both do the same thing, other four get connected without problem by Winbox ("internally" trough IPSEC tunnel) .

Here is my setup
Location 1:
Mikrotik router externally accessible - external IP 80.80.80.1, internal IP 192.168.1.1

Location 2 :
Cisco router (I don't have access to settings) - external IP 80.80.80.2, internal IP 10.0.2.1
--- PORT FORWARDING - 80, 500, 4500 and IPSEC protocol to IP 10.0.2.2
Mikrotik router behind NAT - "external" IP 10.0.2.2 (to Cisco router), internal IP 192.168.2.1

IPSEC tunnel from 192.168.1.0/24 to 192.168.2.0/24 - connect internal networks behind routers.

Working communication
PING from 192.168.1.x to 192.168.2.x (I can ping routers and machines on both sides)
Connection from 192.168.1.x to 192.168.2.2-255 (for example I can connect from 192.168.1.50 to 192.168.2.50 by SSH)
Webfig connection to "external" IP of NATed router - connection from 192.168.1.1 (masquerade) to 80.80.80.2

Not working communication
Winbox connection from 192.168.1.x to 192.168.2.1
Webfig connection from 192.168.1.x to 192.168.2.1

Versions affected:
6.27 (both routers have same version)

SOLUTION:
I have found solution for my problem in this post - http://forum.mikrotik.com/viewtopic.php?t=65733. I set up mangle with "New TCP MMS" to 1390. This number I get with trial and error, I'm not sure why this number is the biggest working.

I would really appreciate, if someone could provide me more deep info about "why" this worked.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 5942
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: Known issues and bugs - a list

Wed May 06, 2015 5:49 pm

Winbox doesn't work because winbox uses Max sized pacekts, typically 1500bytes.
Your tunnel is unable to forward 1500byte packets without fragmentation, that is why setting lower MSS fixes the problem.

Ypu can verify Max packet size over the tunnel by running ping with 'do-not-fragment' flag and by setting packet size.
 
sam1275
Member Candidate
Member Candidate
Posts: 110
Joined: Thu May 21, 2015 2:46 pm

Re: Known issues and bugs - a list

Fri Jun 12, 2015 1:31 pm

Issue:
PPPoE Bug?-"terminating" Forever

Description:
PPPoE dial-out won't reconnect automatically after failing when "dial on demand" is enabled.

Versions affected:
Metal 2SHPn with OS 6.28, RB2011UiAS-2HnD-IN with OS 6.29.1

How to reproduce:
First factory reset to default, then setup to "Home AP" mode in quick setup, choose PPPoE for WAN, then setup a few WLAN and admin password if you like. You can tweak some other settings, they wont affect this.
Now go to the PPP and open your PPPoE interface, in "dial out" tick "dial on demand", keep other PPP settings default. If everything is OK, the PPPoE should in "connected" status, and you can surf the internet now; but, if you try anything to interrupt the connection to your ISP, such as unplug the WAN cable, unplug the Fiber/RJ11 on your modem, or power cycle the modem, the internet will never come back automatically. If you open the quick setup page, it will show "terminating" for PPPoE, and keep hang forever, until you smash the "reconnect" button, everything will be OK in a second.

Notes:
Now I find if I disable "dial on demand", it will reconnect well automatically, but is this a bug?

Support TicketID:
Ticket#2015061266000388
 
xt22
Frequent Visitor
Frequent Visitor
Posts: 52
Joined: Tue Jul 14, 2015 1:16 pm

Re: Known issues and bugs - a list

Tue Jul 14, 2015 1:57 pm

Issue:
LTE interface - when anything is entered in modem-init, it cannot be set to empty/unset

Description:
tested on: RB912UAG-2HPnD + Huawei ME909s-120

Versions affected:
6.30 (tested on this)

How to reproduce:
on factory resetted system, with lte1 in interfaces:
- enter anything to modem-init (even space), apply and save it
- then, it is not possible to delete it, or to unset with the black triangle; after clicking
apply or ok, the previously entered value is back there; It is possible to change
modem-init value to any other value except empty

- this happens even if the lte interface is disabled
- and the same result via terminal ( interface lte set modem-init="" )
 
prozak
newbie
Posts: 26
Joined: Sat Jan 16, 2010 4:01 am

941-2nd speed problem?

Tue Jul 14, 2015 8:50 pm

Hi.
I recently got myself a RB941-2nD (rOS 6.29.1) and i noticed the following.

I run a PPPoE interface dialing my aDsL connection from my ISP router.

After 2-3 days of uptime router starts perfomance degradation in internet.

While link is 15down/1up it turns into an unstable 2mbit max down and 0.2up(ISP is fine)
Plus this speed is stuttering like packets flow every second.

no filter rules nor anything. rb is acting as an internet gateway only.

On resources tab when the incident occurs its shows a min of 21% to 45% cpu usage while nothing is going on.

After a clean reboot everything comes back normal plus cpu usage drops to a reasonable value of 1%-5%.

Problem was confirmed after 3 times.
Last edited by prozak on Tue Jul 14, 2015 9:19 pm, edited 1 time in total.
 
User avatar
Cha0s
Forum Veteran
Forum Veteran
Posts: 907
Joined: Tue Oct 11, 2005 4:53 pm

Re: 941-2nd speed problem?

Tue Jul 14, 2015 9:19 pm

Probably you need to set up some basic firewall http://wiki.mikrotik.com/wiki/Securing_your_router

If you have no filters at all and you have configured the DNS server of Mikrotik to 'Allow remote requests' then it's probably being used by bots and stuff filling up your gateway bandwidth and/or causing high cpu usage.

Everytime you reboot your router I assume you get a new IP so it's ok for a while until the bots find the new IP (they scan all the time all the internet) and start all over again.
 
prozak
newbie
Posts: 26
Joined: Sat Jan 16, 2010 4:01 am

Re: 941-2nd speed problem?

Tue Jul 14, 2015 9:21 pm

Probably you need to set up some basic firewall http://wiki.mikrotik.com/wiki/Securing_your_router

If you have no filters at all and you have configured the DNS server of Mikrotik to 'Allow remote requests' then it's probably being used by bots and stuff filling up your gateway bandwidth and/or causing high cpu usage.

Everytime you reboot your router I assume you get a new IP so it's ok for a while until the bots find the new IP (they scan all the time all the internet) and start all over again.
Thanks ill give it a shot.
 
cigamit
just joined
Posts: 8
Joined: Thu Jul 17, 2008 12:17 am

Re: 941-2nd speed problem?

Mon Jul 20, 2015 6:32 am

Hi.
I recently got myself a RB941-2nD (rOS 6.29.1) and i noticed the following.

I run a PPPoE interface dialing my aDsL connection from my ISP router.

After 2-3 days of uptime router starts perfomance degradation in internet.

While link is 15down/1up it turns into an unstable 2mbit max down and 0.2up(ISP is fine)
Plus this speed is stuttering like packets flow every second.

no filter rules nor anything. rb is acting as an internet gateway only.

On resources tab when the incident occurs its shows a min of 21% to 45% cpu usage while nothing is going on.

After a clean reboot everything comes back normal plus cpu usage drops to a reasonable value of 1%-5%.

Problem was confirmed after 3 times.
I am noticing the same thing on a RB750 for the last few months. Currently using v6.29.1, I tried downgrading to v6.27 and still had the same issue. The Mikrotik has all the proper firewall rules to protect it from the internet and torch even shows that there is almost no traffic going through it at the time.

eth1 is to the internet (isp modem), eth2 goes out to my sector (RB912), eth3 is an IP camera watching the room with the RB750 (not currently streaming, requires you to manually connect).
What I notice when this happens, even though eth5 is disabled (to stop someone from plugging in, its in a remote building) it will show traffic (RX/TX) on eth5 that mirrors traffic on eth2. eth2-5 belong to the same bridge. I believe I have tried it before while using master/slave ports also (originally moved to a bridge to see if it cured this issue).

Nothing in the log when it happens, and rebooting causes it to go back to normal for a few days. Traffic on eth5 goes back down to 0. Rebooting the RB750 has no affect on my external IP since that is all handled by the modem. I will work on sanitizing my /export, then I can upload it.

EDIT: Just updated to v6.30.1, will see if anything in there fixes the issue.
 
prozak
newbie
Posts: 26
Joined: Sat Jan 16, 2010 4:01 am

Re: 941-2nd speed problem?

Tue Jul 21, 2015 8:11 pm

Hi.
I recently got myself a RB941-2nD (rOS 6.29.1) and i noticed the following.

I run a PPPoE interface dialing my aDsL connection from my ISP router.

After 2-3 days of uptime router starts perfomance degradation in internet.

While link is 15down/1up it turns into an unstable 2mbit max down and 0.2up(ISP is fine)
Plus this speed is stuttering like packets flow every second.

no filter rules nor anything. rb is acting as an internet gateway only.

On resources tab when the incident occurs its shows a min of 21% to 45% cpu usage while nothing is going on.

After a clean reboot everything comes back normal plus cpu usage drops to a reasonable value of 1%-5%.

Problem was confirmed after 3 times.
I am noticing the same thing on a RB750 for the last few months. Currently using v6.29.1, I tried downgrading to v6.27 and still had the same issue. The Mikrotik has all the proper firewall rules to protect it from the internet and torch even shows that there is almost no traffic going through it at the time.

eth1 is to the internet (isp modem), eth2 goes out to my sector (RB912), eth3 is an IP camera watching the room with the RB750 (not currently streaming, requires you to manually connect).
What I notice when this happens, even though eth5 is disabled (to stop someone from plugging in, its in a remote building) it will show traffic (RX/TX) on eth5 that mirrors traffic on eth2. eth2-5 belong to the same bridge. I believe I have tried it before while using master/slave ports also (originally moved to a bridge to see if it cured this issue).

Nothing in the log when it happens, and rebooting causes it to go back to normal for a few days. Traffic on eth5 goes back down to 0. Rebooting the RB750 has no affect on my external IP since that is all handled by the modem. I will work on sanitizing my /export, then I can upload it.

EDIT: Just updated to v6.30.1, will see if anything in there fixes the issue.
Hi mate.
Just to inform that in my case adding some basic firewall rules (possibly the outside DNS block) seems it solved my issue. Uptime is 5d and still working without issues. still monitoring
 
kristaps
Member Candidate
Member Candidate
Posts: 272
Joined: Mon Jan 27, 2014 1:37 pm

Re: Known issues and bugs - a list

Wed Jul 29, 2015 10:40 am

Issue:
LTE interface - when anything is entered in modem-init, it cannot be set to empty/unset

Description:
tested on: RB912UAG-2HPnD + Huawei ME909s-120

Versions affected:
6.30 (tested on this)

How to reproduce:
on factory resetted system, with lte1 in interfaces:
- enter anything to modem-init (even space), apply and save it
- then, it is not possible to delete it, or to unset with the black triangle; after clicking
apply or ok, the previously entered value is back there; It is possible to change
modem-init value to any other value except empty

- this happens even if the lte interface is disabled
- and the same result via terminal ( interface lte set modem-init="" )

Thanks for reporting
this is fixed 6.31rc11 version
 
User avatar
vipermx2
newbie
Posts: 27
Joined: Sat Jul 28, 2007 5:51 pm
Location: Kansas USA

Re: Known issues and bugs - a list

Fri Jul 31, 2015 5:43 am

New issue: RB2011UAS-2HnD Interface counters (Tx,Rx, TxPackets,RxPackets...) reset every second. only started happening after upgrading from 6.29 to 6.30.2

Any suggestions or Ideas?
Life is like a Jar of Jalapeños....
...What you do today might burn your ass tomorrow.
 
trace323
Frequent Visitor
Frequent Visitor
Posts: 53
Joined: Thu May 07, 2015 5:52 pm

Re: Known issues and bugs - a list

Sun Aug 09, 2015 4:12 pm

DHCP Bug with Mikrotiks..

Hello Everyone.. Hopefully Mikrotik staff reads this as well..

I have over 100+ Mikrotiks deployed and I have issues with the majority of them. After carefully going through each Mikrotik and looking at them Mikrotik has a HUGE/SEVERE Bug in the DHCP.


I have a CCR 1009

ETH1- WAN
ETH8-LAN Goes to a GS728TP Switch. I have APS here. There is no VLANS.

I am running on a 192.168.8.0/21 NETWORK. I've received over 400+ plus calls of USERS not getting valid Adddress from the DHCP when having Windows Vista, Windows 7 Enterprise. This is a MAJOR Problem...

I can remove the CCR1009 for 1 day and put a SIMPLE BASIC Router like CISCO RV042 Router and Windows Vista and Windows 7 Enterprise issues are gone. All the users can get a VALID IP address with no issues.

I have several Mikrotiks all over the U.S and I know it has to be a Mikortik BUG... I need this to get fix.. My end users get upset that I need to setup a static on there PC so they can get online on my network.

Can someone help me on this??


THANKS!!
 
User avatar
Cha0s
Forum Veteran
Forum Veteran
Posts: 907
Joined: Tue Oct 11, 2005 4:53 pm

Re: Known issues and bugs - a list

Sun Aug 09, 2015 4:25 pm

I use DHCP extensively with all kinds of OSes and all kinds of Routerboards and I have no issue at all.
Windows 7 - works perfect
Windows 8 - works perfect
Windows 10 - works perfect
Windows XP - works perfect
Linux (Ubuntu, Debian, CentOS, RHEL) all work perfect.

What you describe sounds like a user's general report of a problem. What does 'users don't get a valid address' mean exactly?

No technical details, no configuration post, no nothing.

I can only assume that your configuration is the problem.
 
trace323
Frequent Visitor
Frequent Visitor
Posts: 53
Joined: Thu May 07, 2015 5:52 pm

Re: Known issues and bugs - a list

Sun Aug 09, 2015 4:39 pm

How can it be my configuration? If i can simply remove the Mikrotik and put a basic router and they get a valid IP address from my DHCP Server? I have over 50+ Mikrotiks deployed and when users come to the property and they're running on Windows Vista and Windows7 Enterprise they cannot obtain an IP address from my DHCP on the Mikrotik..



My CCR is pretty much basic..
ETH1-WAN
ETH8- LAN Goes to a SIMPLE Switch with NO VLANS.. GS728TP

Sorry for being vague on my previous comment..

I need to setup a static on the end users PC so they can see my TOS (Terms Of Service) page and than they can get online..

I've turned off my TOS Page, turned off the hotspot and same scenario.

I removed the Mikrotik and put a basic router any user with Windows Vista and Windows7 Enterprise can obtain an IP address from the CiscoRV042 without any issues..

Ive exported my simple basic config here..


/ip address
add address=x.x.x.x/29 comment=WAN interface="ether1 - WAN" network=x.x.x.x
add address=192.168.10.1/21 comment="Guest Hotspot" interface="Guest Bridge" network=192.168.8.0
add address=192.168.0.1/24 comment=Managment interface="ether8 - LAN" network=192.168.0.0

/ip dhcp-server
add add-arp=yes address-pool="Guest Pool" disabled=no interface="Guest Bridge" lease-time=1d name=dhcp1
/ip dhcp-server lease
add address=192.168.10.66 client-id=1:b8:ac:6f:e2:2a:1a mac-address=B8:AC:6F:E2:2A:1A server=dhcp1
/ip dhcp-server network
add address=192.168.8.0/21 comment="hotspot network" dns-server=192.168.10.1,8.8.8.8,8.8.4.4 gateway=192.168.10.1


I have no rules or anything. I know its not a config issue because even when having a default config on the Router OS I still have major issues..

I do have a hotspot running but same thing without a hotspot not running..
 
User avatar
Cha0s
Forum Veteran
Forum Veteran
Posts: 907
Joined: Tue Oct 11, 2005 4:53 pm

Re: Known issues and bugs - a list

Sun Aug 09, 2015 5:07 pm

How can it be your configuration? I wouldn't know since you haven't posted your full configuration so that anyone can reproduce your problem.
If you don't post a complete procedure of replicating the problem then there is no problem as far as mikrotik or anyone else is concerned :P

I know it's boring stuff, but that's how you report bugs. You don't expect others to guess how to replicate your problem!

Contact mikrotik with a full supout.rif to figure it out.

By simply trying with different hardware (cisco) does not confirm or deny anything.

If you have an error in your configuration cisco would still work. Does that prove a bug? No.
If there is actually a bug in dhcp-server, cisco would still work. Would you be able to know this way if it was a bug or a config problem? No.

It's just not a robust test to come up with any conclusions other than there is some problem with Mikrotik (either configuration or bug)

You also say that windows don't get a 'valid ip'.
What does that mean? What IP they get EXACTLY, that is not valid?

When reporting problems (or bugs) you should write everything about the issue. I mean absolutely everything.
You can't assume that the readers will have the slightest idea what you are talking about.

Sorry for being skeptical about your report, it's just that dhcp-server is used widely by most mikrotik users (myself included).
If there was a legitimate problem with it, I am sure there would be numerous reports by now.
Without your full configuration no one can know for sure if you found a specific bug triggered by the rest of your configuration, or if it's just bad configuration on your side.

Btw you should create a new thread about this (if you don't want to contact Mikrotik support). This thread is for 'confirmed' (by multiple users apparently) bugs so that Mikrotik can have a comprehensive list and fix them eventually.
 
trace323
Frequent Visitor
Frequent Visitor
Posts: 53
Joined: Thu May 07, 2015 5:52 pm

Re: Known issues and bugs - a list

Sun Aug 09, 2015 5:36 pm

I understand now, my apologies.

When I mean they don't get a valid IP address , I mean they get a self-assigned IP address of 169.254.X.X . This is consider a self-assigned IP address and not receiving a proper IP address from the DHCP for example :
192.168.10.40
255.255.248.0.
192.168.10.1

They should be getting this VALID IP addresses but they don't. I have opened a new thread but haven't gotten really any help with it.


THis is the same config I have on the rest of my Mikrotiks.
Heres my config. I removed ofcourse the critical information.


[admin@sample] > export compact
# aug/09/2015 14:25:50 by RouterOS 6.30.2

/interface bridge
add mtu=1500 name="Guest Bridge" protocol-mode=none
/interface ethernet
set [ find default-name=ether5 ] l2mtu=1588 name="ether1 - WAN"
set [ find default-name=ether6 ] l2mtu=1588 name=ether2
set [ find default-name=ether7 ] l2mtu=1588 name=ether3
set [ find default-name=ether8 ] l2mtu=1588 name=ether4
set [ find default-name=ether1 ] l2mtu=1590 name=ether5
set [ find default-name=ether2 ] l2mtu=1590 name=ether6
set [ find default-name=ether3 ] l2mtu=1590 name=ether7
set [ find default-name=ether4 ] l2mtu=1590 name="ether8 - LAN-GS728TP"
set [ find default-name=sfp1 ] l2mtu=1590 mac-address=
/ip hotspot profile
set [ find default=yes ] login-by=cookie,http-chap,http-pap
add hotspot-address=192.168.10.1 login-by=cookie,http-chap,http-pap name=hsprof1
/ip hotspot user profile
set [ find default=yes ] idle-timeout=1d keepalive-timeout=1d rate-limit=5M/5M session-timeout=1d shared-users=unlimited
/ip pool
add name="Guest Pool" ranges=192.168.10.2-192.168.15.254
/ip dhcp-server
add add-arp=yes address-pool="Guest Pool" disabled=no interface="Guest Bridge" lease-time=1d name=dhcp1
/ip hotspot
add address-pool="Guest Pool" disabled=no idle-timeout=1d interface="Guest Bridge" keepalive-timeout=1d name=hotspot1 profile=hsprof1
/interface bridge port
add bridge="Guest Bridge" interface="ether8 - LAN"
add bridge="Guest Bridge" interface=ether7
add bridge="Guest Bridge" interface=ether4
/ip address
add address=X.X.X.X/29 comment=WAN interface="ether1 - WAN" network=X.X.X.X
add address=192.168.10.1/21 comment="Guest Hotspot" interface="Guest Bridge" network=192.168.8.0
add address=192.168.0.1/24 comment=Managment interface="ether8 - LAN" network=192.168.0.0
/ip dhcp-server lease
add address=192.168.10.66 client-id=1:b8:ac:6f:e2:2a:1a mac-address=B8:AC:6F:E2:2A:1A server=dhcp1
add address=192.168.10.79 always-broadcast=yes client-id=1:70:f1:a1:e9:c:a9 mac-address=70:F1:A1:E9:0C:A9 server=dhcp1
add address=192.168.10.3 client-id=1:1c:3e:84:29:c4:45 mac-address=1C:3E:84:29:C4:45 server=dhcp1
add address=192.168.12.87 client-id=1:70:11:24:c0:9f:69 mac-address=70:11:24:C0:9F:69 server=dhcp1
/ip dhcp-server network
add address=192.168.8.0/21 comment="hotspot network" dns-server=192.168.10.1,8.8.8.8,8.8.4.4 gateway=192.168.10.1
/ip dns
set servers=75.75.75.75,75.75.76.76
/ip firewall filter
add action=passthrough chain=unused-hs-chain comment="place hotspot rules here" disabled=yes
/ip firewall nat
add action=passthrough chain=unused-hs-chain comment="place hotspot rules here" disabled=yes
add action=masquerade chain=srcnat comment="masquerade hotspot network" src-address=192.168.8.0/21
add action=masquerade chain=srcnat comment="masquerade MGMT network" src-address=192.168.0.0/24
/ip firewall service-port
set ftp disabled=yes
set tftp disabled=yes
set irc disabled=yes
set h323 disabled=yes
set sip disabled=yes
set pptp disabled=yes
/ip hotspot ip-binding
add address=192.168.0.0/24 type=bypassed
add mac-address=F0:4F:7C:EE:4C:F2 type=bypassed
add mac-address=00:23:14:81:3D:B0 type=bypassed
add mac-address=00:26:5E:32:47:C7 type=bypassed
add mac-address=00:E0:4C:A6:5D:FA type=bypassed
add mac-address=00:24:D7:86:C8:6C type=bypassed
add mac-address=44:2A:60:60:B4:C9 type=bypassed
add mac-address=EC:55:F9:C5:E5:37 type=bypassed
add mac-address=00:23:15:9D:8A:14 type=bypassed
add mac-address=00:22:43:45:07:B2 type=bypassed
add mac-address=00:1C:BF:AD:B7:FC type=bypassed
add mac-address=00:19:D2:73:B7:48 type=bypassed
add mac-address=00:08:CA:C3:C3:68 type=bypassed
add mac-address=70:5A:B6:41:AD:A6 type=bypassed
add mac-address=B4:82:FE:8F:D5:01 type=bypassed
add mac-address=00:22:5F:FE:4E:87 type=bypassed
add mac-address=00:16:CB:8D:B0:09 type=bypassed
add mac-address=68:5D:43:F2:B7:F5 type=bypassed
add mac-address=94:39:E5:57:E2:E5 type=bypassed
add mac-address=E0:CA:94:82:DB:58 type=bypassed
add mac-address=A0:6C:EC:73:CD:85 type=bypassed
add mac-address=18:03:73:00:F9:E2 type=bypassed
add mac-address=70:56:81:C1:CF:93 type=bypassed
add mac-address=F0:4F:7C:06:B3:37 type=bypassed
add mac-address=E0:CB:1D:F8:4E:45 type=bypassed
add mac-address=4C:ED:DE:AC:5D:93 type=bypassed
/ip hotspot user
add name=guest password=guest
/ip hotspot walled-garden
add comment="place hotspot rules here" disabled=yes
add dst-host=www.sample.com server=hotspot1
/ip hotspot walled-garden ip
add action=accept disabled=no protocol=icmp server=hotspot1
add action=accept disabled=no dst-port=53 server=hotspot1
/ip proxy
set cache-path=web-proxy1
/ip route
add check-gateway=ping distance=1 gateway=X.X.X.X
/ip service
set telnet disabled=yes
set ftp disabled=yes
set ssh address=x.x.x.x
set api disabled=yes
set api-ssl disabled=yes
/snmp
set enabled=yes trap-version=2
/system clock
set time-zone-autodetect=no
/system ntp client
set primary-ntp=24.56.178.140
/system resource irq rps
set sfp1 disabled=yes
set ether5 disabled=yes
set ether6 disabled=yes
set ether7 disabled=yes
set "ether8 - LAN" disabled=yes
/system routerboard settings
set cpu-frequency=1200MHz memory-frequency=1066DDR
 
User avatar
Cha0s
Forum Veteran
Forum Veteran
Posts: 907
Joined: Tue Oct 11, 2005 4:53 pm

Re: Known issues and bugs - a list

Sun Aug 09, 2015 6:34 pm

At first glance there seems to be an issue with DHCP when running on a bridge.

When an interface is slave to a bridge it seems that it doesn't respond to DHCP client requests.

What's really weird is that I have numerous installations with bridges and DHCP server running on them without a problem whatsoever!

But trying your configuration (or even a new one from scratch) I cannot get an IP from DHCP when on bridge.
When I put the dhcp server on the interface directly and disable the bridge then it works right away!

It may be an issue with the latest versions of Mikrotik when creating new DHCP servers and/or bridges (but not if those were created on older versions?)
The working installations that I have have been set up many versions ago and I was just upgrading them.
I haven't set up a bridge/dhcp in the last stable version of mikrotik (6.30.2).

So, at first glance it seems that there's an issue with DHCP when running on a bridge.
Can anyone else confirm that?
 
User avatar
Cha0s
Forum Veteran
Forum Veteran
Posts: 907
Joined: Tue Oct 11, 2005 4:53 pm

Re: Known issues and bugs - a list

Sun Aug 09, 2015 6:35 pm

I don't know your topology, but a quick workaround would be to disable the bridge and re-assign the dhcp server and the IP address to ether8 directly.

It should work after that.
 
trace323
Frequent Visitor
Frequent Visitor
Posts: 53
Joined: Thu May 07, 2015 5:52 pm

Re: Known issues and bugs - a list

Sun Aug 09, 2015 6:51 pm

Maybe you're missing something when creating the bridge..

So this is the way I have it..

ETH-1 WAN
ETH8-LAN goes to a GS728TP Switch. I have 10 APS here, no VLANS.

I go to bridge > add bridge > create the Guest Bridge > Than go to IP > Addresses > add new > 192.168.8.0/21 for the IP and the interface will be Guest Bridge..

Also under Bridge > Ports I have ETH8-LAN pointing towards Guest Bridge..

THan I go to IP> DHCP > DHCP Setup > The DHCP Server Interface will be the Guest Bridge.

I think that's what you're missing..

But yes my network topology is very basic and simple..


I have already disabled the guest bridge and point re-create my dhcp and pointed directly into ETH8 and still have issues.

I have started from scratch and still have issues, not sure why. Other OS works fine..



I just upgraded the RouterOS last night. It not the firmware. Looking up very OLD google Mikrotik Vista issues there has been issue reported as well..


Just ask me anything, I will help you out.. I'm just trying to get this fix overall.

Please and thank you.
 
User avatar
Cha0s
Forum Veteran
Forum Veteran
Posts: 907
Joined: Tue Oct 11, 2005 4:53 pm

Re: Known issues and bugs - a list

Sun Aug 09, 2015 7:12 pm

Maybe you're missing something when creating the bridge..
I copied your export verbatim. And I created my own configuration from scratch with a completely config-reset router JUST in case.
I didn't miss anything. As a matter of fact when I created my own configuration I simply created the most basic stuff (bridge and dhcp-server and nothing else) just to make sure that the problem is not caused by something else.
ETH-1 WAN
ETH8-LAN goes to a GS728TP Switch. I have 10 APS here, no VLANS.
Why use a bridge then? With what you have described so far you do not need a bridge.
Just ditch it and work with ether8 directly. DHCP server DOES work directly on the ethernet interface.
I just tested it myself (your exact configuration) on a lab with windows 8 and windows 10 as clients and both got an IP right away.
I have already disabled the guest bridge and point re-create my dhcp and pointed directly into ETH8 and still have issues.
Did you move the IP to ether8 after disabling the bridge?
You don't really need to recreate the dhcp server. Just change the interface to ether8.
 
trace323
Frequent Visitor
Frequent Visitor
Posts: 53
Joined: Thu May 07, 2015 5:52 pm

Re: Known issues and bugs - a list

Sun Aug 09, 2015 7:25 pm

I have ditched the guest bridge and same thing. I am running into the same thing with and without the Guest Bridge.

The reason why I have a guest bridge it's very easy to manage things well in my aspect. It should work fine with the Guest Bridge, this shouldn't affect the DHCP.

Since I do have a hotspot running on my Mikrotiks.

I know the DHCP works fine with several devices.. I am just running into a big issues with Windows Vista( specifically) and Windows 7 (Enterprise Edition). My network is very basic , nothing to complicated.


For example > When a guest is calling in from a property saying, hes unable to get online. We ask right away if he has Vista. They say yes right away and once we confirm they do have it. We have the check the settings on the nic card and stuff. There is nothing wrong that we can see. They get a 169.254 ( Self-assigned) IP address instead of pulling one from the DHCP Server.

So than we give them a static of 192.168.9.40/255.255.248.0/192.168.10.1 This is within the range. Once we give them a valid IP from the DHCP server, they can pull up my TOS page and get online....

This is the only issues where I am with Mikrotik overall.. I am not sure what else to try...
 
trace323
Frequent Visitor
Frequent Visitor
Posts: 53
Joined: Thu May 07, 2015 5:52 pm

Re: Known issues and bugs - a list

Mon Aug 10, 2015 3:59 pm

I really think Mikrotik staff needs to get involve with this... I seriously think it's an issue with Mikrotik itself, not a config issue.

I have tried several things and still had no success..


Anyone else trying to mimic the same thing? Anyone has any input on this?

Thanks..
 
User avatar
Cha0s
Forum Veteran
Forum Veteran
Posts: 907
Joined: Tue Oct 11, 2005 4:53 pm

Re: Known issues and bugs - a list

Tue Aug 11, 2015 3:58 pm

At first glance there seems to be an issue with DHCP when running on a bridge.

When an interface is slave to a bridge it seems that it doesn't respond to DHCP client requests.

What's really weird is that I have numerous installations with bridges and DHCP server running on them without a problem whatsoever!

But trying your configuration (or even a new one from scratch) I cannot get an IP from DHCP when on bridge.
When I put the dhcp server on the interface directly and disable the bridge then it works right away!

It may be an issue with the latest versions of Mikrotik when creating new DHCP servers and/or bridges (but not if those were created on older versions?)
The working installations that I have have been set up many versions ago and I was just upgrading them.
I haven't set up a bridge/dhcp in the last stable version of mikrotik (6.30.2).

So, at first glance it seems that there's an issue with DHCP when running on a bridge.
Can anyone else confirm that?
It turns out that the issue with the bridge and DHCP affects the x64 mode of CHR (on which I tried the configuration above).

Disabling x64 restores the dhcp-server functionality on a bridge.

http://forum.mikrotik.com/viewtopic.php ... 15#p494315
 
trace323
Frequent Visitor
Frequent Visitor
Posts: 53
Joined: Thu May 07, 2015 5:52 pm

Re: Known issues and bugs - a list

Wed Aug 12, 2015 2:28 am

How would I disable that?

Thanks
 
trace323
Frequent Visitor
Frequent Visitor
Posts: 53
Joined: Thu May 07, 2015 5:52 pm

Re: Known issues and bugs - a list

Wed Aug 12, 2015 3:03 am

I really don't think it's that. I will be doing more trials this week on several Vista PC's. I will trying without a bridge, with a bridge, without a hotspot. with one. I will also try just trying a default config and see how that goes..

I will post the results..


I know it's something with the Mikrotik or something when having a hotspot doesn't work.


I wish a Mikrotik staff would look into this. Im sure they will see something as well.


I will let you know how it goes.


Thanks
 
trace323
Frequent Visitor
Frequent Visitor
Posts: 53
Joined: Thu May 07, 2015 5:52 pm

Re: Known issues and bugs - a list

Wed Aug 12, 2015 7:22 am

At first glance there seems to be an issue with DHCP when running on a bridge.

When an interface is slave to a bridge it seems that it doesn't respond to DHCP client requests.

What's really weird is that I have numerous installations with bridges and DHCP server running on them without a problem whatsoever!

But trying your configuration (or even a new one from scratch) I cannot get an IP from DHCP when on bridge.
When I put the dhcp server on the interface directly and disable the bridge then it works right away!

It may be an issue with the latest versions of Mikrotik when creating new DHCP servers and/or bridges (but not if those were created on older versions?)
The working installations that I have have been set up many versions ago and I was just upgrading them.
I haven't set up a bridge/dhcp in the last stable version of mikrotik (6.30.2).

So, at first glance it seems that there's an issue with DHCP when running on a bridge.
Can anyone else confirm that?
It turns out that the issue with the bridge and DHCP affects the x64 mode of CHR (on which I tried the configuration above).

Disabling x64 restores the dhcp-server functionality on a bridge.

http://forum.mikrotik.com/viewtopic.php ... 15#p494315



CHa0s:

Have you read this? http://forum.mikrotik.com/viewtopic.php?t=37978



I am not the only one experiencing this. I wonder why hasn't Mikrotik done anything about this?
 
User avatar
Cha0s
Forum Veteran
Forum Veteran
Posts: 907
Joined: Tue Oct 11, 2005 4:53 pm

Re: Known issues and bugs - a list

Wed Aug 12, 2015 5:29 pm

My report was specific to CHR not to any Mikrotik device or installation.

I am not sure what the problem is with your configuration.
I have DHCP servers on bridges without any problem whatsoever.

I set up my lab to test your configuration with CHR (Cloud hosted router) which is stil in RC so the specific bug I mention shouldn't exist on previous versions since I do run 6.30.2 on many installations with dhcp server on a bridge without an issue.

However I just tried your configuration on a 6.30.2 installation and it works perfectly.

The thread you mention is from 2009. Not really something to count on.

Just contact mikrotik support with full supout.rif files etc since your situation is very specific and cannot be easily reproduced (apparently)
Don't expect to receive any official support on these user forums.
 
digitexwireless
newbie
Posts: 40
Joined: Thu Mar 01, 2007 5:10 am

Re: Known issues and bugs - a list

Sat Aug 15, 2015 4:28 pm

Reset Counters button seems to have no affect on any RB750UP's on the network. We are seeing a tremendous amount of Link Downs on these routers too after upgrading to 6.3x.x.
 
SvZol
just joined
Posts: 24
Joined: Tue Dec 09, 2014 10:06 am
Location: VRN
Contact:

Re: Known issues and bugs - a list

Fri Aug 21, 2015 2:06 pm

Is it bug or feature of FTP-server? ROS 6.31 http://forum.mikrotik.com/viewtopic.php ... 41#p495941

MikroTik's FTP does not understand the command appe
 
Robinson
Frequent Visitor
Frequent Visitor
Posts: 81
Joined: Tue Nov 10, 2009 7:30 pm

Re: Known issues and bugs - a list

Sat Sep 05, 2015 4:35 pm

After upgrading to version 6.30 I noticed max L2MTU on ethernet port ether1 is 1520?
This is in accordance with the table at http://wiki.mikrotik.com/wiki/Manual:Ma ... uterBoards.
But in previous versions of ROS RB433GL reports L2MTU on Ether1 1524.
What is happening now, we have a problem with MPLS links whose MPLS Interface MTU is 1524.
If L2MTU was incorrectly shown in previous versions of ROS, how is it that we only now experiencing problems with MPLS?
 
vortex
Forum Veteran
Forum Veteran
Posts: 714
Joined: Sat Feb 16, 2013 6:10 pm

Re: Known issues and bugs - a list

Sat Sep 05, 2015 4:57 pm

Bridge between switches severely but not perfectly constantly affects routing performance on RB2011.
 
vortex
Forum Veteran
Forum Veteran
Posts: 714
Joined: Sat Feb 16, 2013 6:10 pm

Re: Known issues and bugs - a list

Sat Sep 05, 2015 4:59 pm

I think NAT performance has to be improved.
 
vortex
Forum Veteran
Forum Veteran
Posts: 714
Joined: Sat Feb 16, 2013 6:10 pm

Re: Known issues and bugs - a list

Sat Sep 05, 2015 5:03 pm

Support hardware acceleration of all encryption schemes.
 
vortex
Forum Veteran
Forum Veteran
Posts: 714
Joined: Sat Feb 16, 2013 6:10 pm

Re: Known issues and bugs - a list

Sat Sep 05, 2015 5:04 pm

Improve PPPoE performance.
 
samsung172
Forum Guru
Forum Guru
Posts: 1186
Joined: Sat Apr 04, 2009 3:45 am
Location: Østfold - Norway
Contact:

Re: Known issues and bugs - a list

Fri Oct 09, 2015 10:39 pm

Possible BUG - Not tested more.


Today i had a CCR1036 running MPLS, ospf,bgp. It was struggeling and had 100% CPU usage. I booted it - still CPU usage in about 95 to 100%. I see in profile - that "networing" was using all "resorces" and started to do a researc. I found a dissabled src-nat masqurade rule in router - but it was dissabled and Not in function. I still deleted it - and wolla. Router was at 6-7% CPU.

Since it is in production - i dont want to test it more- maybe someone else could do? - in my mind/opinion- it should not go crasy by a dissabled nat rule? -

it has connection tracking in auto - but still run tracking after rule dissabled (it was what i might beleve was the problem)

router have about 30.000entris in connections , 1211 routes - bgp (vrf) and ospf (MPLS) combined. and about 700mb/s TX and 200RX in main port.

about 336 vlans to NNI's - and no full routingtables - 2 instance of BGP session - vrf (internal with MPLS and confederation) and "main". (default route to the global bgp table)
 
UsernameMT
Frequent Visitor
Frequent Visitor
Posts: 55
Joined: Mon Nov 02, 2015 1:42 pm

Re: Known issues and bugs - a list

Tue Nov 17, 2015 3:13 pm

:D
Hi
Sorry, but, this is a bug or a feature ROS?:
/ip service set www address=ХХХ.ХХХ.ХХХ.0/24 port=6665
and
/ip service set www address=ХХХ.ХХХ.ХХХ.0/24 port=6000
At various recent versions of ROS:
it is not connected to the WEB-interface on port 6665 and 6000... (maybe, there are other ports, but not tried all :) )

Best regards.
sorry for my English
 
magnavox
Member
Member
Posts: 339
Joined: Thu Jun 14, 2007 1:03 pm

Re: Known issues and bugs - a list

Thu Nov 26, 2015 3:49 pm

Scripts using execute command, can stop...

ROS 6.33.1 x86 (same as ROS 6.27)
:execute command have only a option
script


ROS 6.33.1 tile
:execute command have tow option:
file script

So need to modifidy code from
:execute name_script
to like
:excute script="name_script"

Mikrotik, please check this...
Best Regards...
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 5942
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: Known issues and bugs - a list

Thu Nov 26, 2015 5:24 pm

Old syntax also works for backward compatibility
:execute "script_name"  
 
magnavox
Member
Member
Posts: 339
Joined: Thu Jun 14, 2007 1:03 pm

Re: Known issues and bugs - a list

Thu Nov 26, 2015 8:56 pm

Old syntax also works for backward compatibility
:execute "script_name"  
1) Updating from 6.27 to 6.33.1 (on CCR), script stop working.ì, so any backward compatibilty...
2) Updating from 6.27 to 6.33.1 (on x86 VM), script work fine.

Syntax for same versione 6.33.1 are different for Tile and x86 code!
Best Regards...
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 5942
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: Known issues and bugs - a list

Fri Nov 27, 2015 12:24 pm

Works on both platforms the same.
Script names, strings etc should always be used in quotes.
 
magnavox
Member
Member
Posts: 339
Joined: Thu Jun 14, 2007 1:03 pm

Re: Known issues and bugs - a list

Fri Nov 27, 2015 5:34 pm

Script names, strings etc should always be used in quotes.
My scritp work fine in 6,27 whitout quotes
Ok in future I will use quotes.
Works on both platforms the same.
6.33.1 x86 platform provide only one option, Tile platform two options. why?

My script work fine under x86 6.33.1 without quotes
Best Regards...
 
pe1chl
Forum Guru
Forum Guru
Posts: 5917
Joined: Mon Jun 08, 2015 12:09 pm

Re: Known issues and bugs - a list

Sun Dec 13, 2015 5:57 pm

In the log messages logged by the BGP router, the AS numbers in the 32-bit range are still printed in the deprecated
ASDOT notation instead of the ASPLAIN notation used in the user interface.

16:13:13 route,bgp,error Invalid remote AS, expected 64691
16:13:13 route,bgp,error RemoteAddress=44.137.60.9
16:13:13 route,bgp,error RemoteAs=64398.18672

It should have logged RemoteAs=4220406000
 
flameproof
Frequent Visitor
Frequent Visitor
Posts: 75
Joined: Tue Sep 01, 2015 3:17 pm

Re: Known issues and bugs - a list

Thu Dec 31, 2015 4:24 am

There seems to be a bug in 6.33.3 (haven't checked older versions) with RADIUS-based user login (AAA). Upon login by a non-local user, the following is logged on the MT router:
03:16:54 radius,debug new request 0d:01 code=Access-Request service=login
03:16:54 radius,debug sending 0d:01 to x.x.x.x:1812
03:16:54 radius,debug,packet sending Access-Request with id 5 to x.x.x.x:1812
03:16:54 radius,debug,packet     Signature = 0x3fca657862be8355a291bf32522c7be6
03:16:54 radius,debug,packet     Service-Type = 1
03:16:54 radius,debug,packet     User-Name = "xxxx"
03:16:54 radius,debug,packet     MS-CHAP-Challenge = 0xb9a374da514667be08e1b20d8cfa64ca
03:16:54 radius,debug,packet     MS-CHAP2-Response = 0x000021402324255e262a28295f2b3a33
03:16:54 radius,debug,packet       7c7e000000000000000053f2a38fb731
03:16:54 radius,debug,packet       4b9054306d76e615c45c02f6b04bf03a
03:16:54 radius,debug,packet       44a6
03:16:54 radius,debug,packet     Calling-Station-Id = "10.20.0.100"
03:16:54 radius,debug,packet     NAS-Identifier = "AC0001"
03:16:54 radius,debug,packet     NAS-IP-Address = 10.20.0.2
03:16:54 radius,debug,packet received Access-Accept with id 5 from x.x.x.x:1812
03:16:54 radius,debug,packet     Signature = 0xcc112ac0c094bc2a0ad010f0a0559bdf
03:16:54 radius,debug,packet     MS-CHAP2-Success = 0x00533d36343936424233454546343336
03:16:54 radius,debug,packet       35354638443631453330434544373544
03:16:54 radius,debug,packet       3541394231413943303433
03:16:54 radius,debug,packet     MT-Group = "full"
03:16:54 radius,debug received reply for 0d:01
03:16:54 system,info,account user xxxx logged in from 10.20.0.100 via web
03:16:54 system,info,account user xxxx logged out from 10.20.0.100 via web
On the browser, WebFig hangs in the "loading" animation, and does not progress. It seems to get hanged after doing a POST to jsproxy. I can reproduce this on a RB750 and a RB912.

It seems curious that the reply group is shown on the RADIUS server as Group = "full" vs. MT-Group = "full" on the RBs.
 
port9nka
just joined
Posts: 17
Joined: Tue May 20, 2014 1:48 am

Re: Known issues and bugs - a list

Sat Jan 02, 2016 9:56 pm

Caught a bug after 6.33.3 update. rb912uag-2hpnd has a 1G link with rb250GS (swos 1.9). After rb912 updating link began flapping. Cable is fine, tested with dlink 1G switch. no tx/rx errors. 25 link flaps in hour! Not able to downgrade  I’ve “Solved” problem by linking via 100M - disabled 1000M half/1000M full on eth1 of rb912G.
 
vdrahos
just joined
Posts: 3
Joined: Wed Nov 25, 2015 3:25 pm

Re: Known issues and bugs - a list

Mon Jan 04, 2016 4:42 pm

Hi all,

I react to the issue Router looks in the main routing table and not in a VRF for ICMP TTL exceeded (type 11) described by tomaskir http://forum.mikrotik.com/viewtopic.php ... 00#p414018 .

I've found out that the issue is not related to ICMP TTL exceeded only. I've noticed the exactly same issue with ICMP Fragmentation Needed (Type 3, Code 4) message.

It's probably connected to treating all ICMP responses created by router.
 
User avatar
NiK
Trainer
Trainer
Posts: 21
Joined: Mon Apr 06, 2015 12:38 pm

Re: Known issues and bugs - a list

Sat Jan 09, 2016 11:51 pm

Hello!

We have two offices connected via Internet by GRE tunnels. Each office has only one public IP-address.
GRE tunnel established between these public IP.
Both offices have LAN with different private IP/subnet. NAT is used to access office users to the Internet.
Some users from office #1 LAN, needs special access to recources in office #2 LAN using windows-based pptp-client.

After upgrading RouterOS in office #1 to version 6.33.3 we have:
1) users from office #1 FAILS to connect pptp service on public IP of office #2 WHILE GRE TUNNEL IS UP ;
2) users from office #1 CAN sucessfull connect to pptp service on public IP of office #2 WHILE GRE TUNNEL IS DOWN ;
3) users from office #1 can sucessfull connect to pptp service on any OTHER public IP, independ on GRE tunnel state ;

Additional picture attached.

I think, problem is in processing GRE packets from several connections to the SAME target IP (server)
( 1.Gre-tunnel from WAN , 2. NATed pptp from LAN)

This problem disappears, when DOWNGRADING RouterOS to v6.27
You do not have the required permissions to view the files attached to this post.
 
User avatar
NiK
Trainer
Trainer
Posts: 21
Joined: Mon Apr 06, 2015 12:38 pm

Re: Known issues and bugs - a list

Sat Jan 09, 2016 11:55 pm

Hello!

Problem:
We have 2 offices connected via Internet by GRE tunnels. Each office has only one public IP-address.
GRE tunnel established between these public IP.
Both offices have LAN with different private IP/subnet. NAT is used to access office users to the Internet.
Some users from office #1 LAN, needs special access to recources in office #2 LAN using windows-based pptp-client.

After upgrading RouterOS in office #1 to version 6.33.3 we have:
1) users from office #1 FAILS to connect pptp service on public IP of office #2 WHILE GRE TUNNEL IS UP ;
2) users from office #1 CAN sucessfull connect to pptp service on public IP of office #2 WHILE GRE TUNNEL IS DOWN ;
3) users from office #1 can sucessfull connect to pptp service on any OTHER public IP, independ on GRE tunnel state ;

Additional picture attached.

I think, problem is in processing GRE packets from several connections to the SAME target IP (server)
( 1.Gre-tunnel from WAN , 2. NATed pptp from LAN)

This problem disappears, when DOWNGRADING RouterOS to v6.27
 
africantech
just joined
Posts: 5
Joined: Mon Jan 11, 2016 11:03 am

Re: Known issues and bugs - a list

Mon Jan 11, 2016 11:15 am

Hello, I'm not sure if this is the correct thread, so if not, can a mod please move it.

I recently upgraded to RouterOS 6.33.3 (Hardware - 2011UIAS-2HnD) from an older 6.xx version (I can't remember what version it was :oops: ) but have noticed that I now get very slow response when accessing via Winbox (version 3)

When I connect via Winbox and click on Terminal, it takes about 3 minutes for the Terminal Window to reach the command prompt. In addition, I notice that the Date and Time clock takes ages to reflect the correct time. Basically, any function (eg list files, DHCP lists, etc) that I launch takes an absolute age to launch.

I would appreciate it if anyone has experienced similar and which version you recommend I roll back to.

PS: I did an 'auto-upgrade' in order to preserve all my existing rules and configurations - would it help to reset and then reload from a backup?
 
IlCarletto
newbie
Posts: 30
Joined: Mon May 10, 2010 3:09 pm
Location: Milan
Contact:

Re: Known issues and bugs - a list

Wed Feb 17, 2016 10:19 am

Problem oh DH Groups from Wimbox to Web

Setting 1536 on winbox I see on Web 1024
But it's the right choose if I Set from the Web my right DH group (1536).I see on WImbox 1024
You do not have the required permissions to view the files attached to this post.
RB433 / R52n + R52n-M - 6.10rc
 
suntelSean
newbie
Posts: 48
Joined: Sat Oct 11, 2014 12:41 am

Re: Known issues and bugs - a list

Tue Feb 23, 2016 6:10 am

on 6.34x

On RB2011, firmware shows 3.18 (even though I know I've updated to 3.24 before).
Tried to update again, and console shows firmware updated, but Winbox and console show 3.18 after reboot.
 
mcgregor808
just joined
Posts: 2
Joined: Tue Mar 01, 2016 1:24 am

Re: Known issues and bugs - a list

Tue Mar 01, 2016 8:21 pm

Hello, perhaps this isn't the correct thread but I'm a bit desperate.

My RB750 mini router started some weird behavior after upgrading from V5.26 to V6.34.1

System->Clock->Time went back to Jan 1, 1970 and won't reset via System->clock (timeout)
I'm in Hawaii, (GMT -10:00). Hawaii or Honolulu doesn't showing up in the timezone list. Autodetect selected but not working.
System->Resources shows all Zeros
System->Reboot doesn't do anything
Winbox takes a very long time to connect and then gets disconnected every few minutes.


Managed to up-upgrade to V6.34.2 which seems more stable but still having the same problems after I set the time.

If I do a configuration reset via the reset button (hold while powered off until flashing lights) the initial login takes me back to what looks like "normal", i.e. speedy response and I see the CPU and memory correctly. But the date/time is back to Jan 1, 1970

Try to set the clock and it all goes south again.
Here's what I get from the terminal window:
[admin@mikrotik] /system clock set time 08:13:00
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)

I don't know how to generate a "supout file" - Thanks for any help you can provide.
 
mcgregor808
just joined
Posts: 2
Joined: Tue Mar 01, 2016 1:24 am

Re: Known issues and bugs - a list

Tue Mar 01, 2016 8:25 pm

I'm having similar issues - did you find a fix or work-around?
Hello, I'm not sure if this is the correct thread, so if not, can a mod please move it.

I recently upgraded to RouterOS 6.33.3 (Hardware - 2011UIAS-2HnD) from an older 6.xx version (I can't remember what version it was :oops: ) but have noticed that I now get very slow response when accessing via Winbox (version 3)

When I connect via Winbox and click on Terminal, it takes about 3 minutes for the Terminal Window to reach the command prompt. In addition, I notice that the Date and Time clock takes ages to reflect the correct time. Basically, any function (eg list files, DHCP lists, etc) that I launch takes an absolute age to launch.

I would appreciate it if anyone has experienced similar and which version you recommend I roll back to.

PS: I did an 'auto-upgrade' in order to preserve all my existing rules and configurations - would it help to reset and then reload from a backup?
 
midenok
newbie
Posts: 39
Joined: Fri Dec 27, 2013 5:34 pm

Re: Known issues and bugs - a list

Wed Mar 23, 2016 5:54 pm

RouterOS 6.34
 
africantech
just joined
Posts: 5
Joined: Mon Jan 11, 2016 11:03 am

Re: Known issues and bugs - a list

Sun Apr 10, 2016 2:24 pm

I'm having similar issues - did you find a fix or work-around?
Hello, I'm not sure if this is the correct thread, so if not, can a mod please move it.

I recently upgraded to RouterOS 6.33.3 (Hardware - 2011UIAS-2HnD) from an older 6.xx version (I can't remember what version it was :oops: ) but have noticed that I now get very slow response when accessing via Winbox (version 3)

When I connect via Winbox and click on Terminal, it takes about 3 minutes for the Terminal Window to reach the command prompt. In addition, I notice that the Date and Time clock takes ages to reflect the correct time. Basically, any function (eg list files, DHCP lists, etc) that I launch takes an absolute age to launch.

I would appreciate it if anyone has experienced similar and which version you recommend I roll back to.

PS: I did an 'auto-upgrade' in order to preserve all my existing rules and configurations - would it help to reset and then reload from a backup?
Hi, Upgrading Winbox to 3.4 appears to have helped.
 
derr12
Member
Member
Posts: 411
Joined: Fri May 01, 2009 11:32 pm

Re: Known issues and bugs - a list

Fri Apr 15, 2016 1:52 am

RB922UAGS-5HPacD 5ghz radio transmits @ 17dbi when controlled by capsman. In capsman tx power can be set auto or manually, doesn't matter. TX power at radio is always 17dbi.

Oddly if you shove a 2.4ghz miniPCI radio in there, it plays nice with caps man.

Bug is present in latest RC build.

Who is online

Users browsing this forum: No registered users and 139 guests