Known issues and bugs - a list

RouterOS General
61

EDIT: Verified, cant change the name in Winbox, only in Console.

Added to the list.

62

How about the RB1100AH(x2) packet loss problem with queue/queuetree ?

http://forum.mikrotik.com/t/feature-extension-suggestion-graphing-in-2-9/782/1
http://forum.mikrotik.com/t/feature-extension-suggestion-graphing-in-2-9/782/1
http://forum.mikrotik.com/t/feature-extension-suggestion-graphing-in-2-9/782/1

63

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.

64

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
/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=pptpPPTP-client config
/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.0Notes:
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

65

Excellent bug report, thank you!

Added to the list.

66

Issue:
Web-proxy redirect-to

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

Versions affected:
6.7

How to reproduce:/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]

67

2) > SMS receiving stops working and cant be re-enabled

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.

Should be fixed

4) > PPTP/SSTP - could not add bridge port - BCP not working

fixed

5) > L2TP Server bug - replies from wrong IP address

new ppp package invalidates this

6) > Duplicate address-list entries (same list name and same address or address range) are causing a crash.

fixed

7) > Certificates can’t be renamed via Winbox.

fixed

68

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

69

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/t/how-initialized-a-variable-by-sms/53857/1

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

70

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

71

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!

72

There is an issue where routeros can not talk to sshd servers that have challenge/response turned on.

73

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.
  1. Duplicate address-list entries (same list name and same address or address range) are causing a crash.
  1. Certificates can’t be renamed via Winbox.
  1. PPTP/SSTP - could not add bridge port - BCP not working
74

This is a repost of an issue submitted by Rudios: http://forum.mikrotik.com/t/known-issues-and-bugs-a-list/71473/65
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:
/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=testPPTP-client config:
/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=testDHCP client config:
/ip dhcp-client
add default-route-distance=0 dhcp-options=hostname,clientid disabled=no interface=ether4Notes:
MikroTik confirmed this to be a bug that will be solved in a later version.

Support TicketID:
Ticket#2013120266000175
Ticket#2014020466000625

75

I tested this on 6.9 and it seems to work, can you please provide more detail how to reproduce on 6.9?

Added to the list, thanks!

The support response got lost in all my emails, sorry, my fault :slight_smile:
Will update the ticket asap with the requested info on 6.9

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!

76

This was fixed in v6.8 as well. if anyone can repeat it, email support with full access, description and supout.rif file

77

I will email support asap, can reproduce it with the steps in this post:
http://forum.mikrotik.com/viewtopic.php?f=2&t=78816&start=50#p407146

Edit: sent with [Ticket#2014020466000625]

78

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:
/routing bgp instance vrf exportThe 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

79

Thanks for the report! Added to the list.

80

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 :frowning:
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.