MikroTik-Fail - Revision history

N4VX: /* 4 byte ASN */

2026-09-28T01:37:03Z

4 byte ASN

N4VX: /* IS-IS Support */

2026-09-28T01:25:43Z

IS-IS Support

N4VX: /* RFC3021 /31 links */

2025-10-25T15:35:05Z

RFC3021 /31 links

Bryan at 06:22, 29 November 2024

2024-11-29T06:22:11Z

N4VX: /* IS-IS Support */

2024-01-24T18:56:17Z

IS-IS Support

Bryan at 17:01, 11 August 2022

2022-08-11T17:01:31Z

Bryan at 04:35, 26 March 2022

2022-03-26T04:35:53Z

Bryan at 04:24, 26 March 2022

2022-03-26T04:24:26Z

Bryan: MikroTik

2022-03-26T04:07:10Z

MikroTik

New page

This is a list of basic failures that I've found MikroTik Routers to have. This is by no means exhaustive.

← Older revision		Revision as of 01:37, 28 September 2026
Line 110:		Line 110:
	= 4 byte ASN =		= 4 byte ASN =

−	Per [https://mailman.nanog.org/pipermail/nanog/2022-August/220138.html this message] on NANOG, they can't do 4 byte ASN's	+	<s>Per [https://mailman.nanog.org/pipermail/nanog/2022-August/220138.html this message] on NANOG, they can't do 4 byte ASN's</s>
		+
		+	BGP AS4 (4-byte / 32-bit ASN) capability negotiation is defined in RFC 6793 is supported in modern Mikrotik RouterOS versions.
		+	[https://manual.mikrotik.com/docs/user-guides/routing-and-networking-protocols/unicast/bgp/understanding-bgp#supported-standards https://manual.mikrotik.com/docs/user-guides/routing-and-networking-protocols/unicast/bgp/understanding-bgp#supported-standards]

@@ Line 13: / Line 13: @@
 * [https://discord.com/channels/936294190948687922/1108700927365500978/1199781869470883861 https://discord.com/channels/936294190948687922/1108700927365500978/1199781869470883861]
 * [https://mikrotik.com/download/changelogs#show-tab-tree_2-id-fbb68df8e99f8b3afd4862846ad531f7 https://mikrotik.com/download/changelogs#show-tab-tree_2-id-fbb68df8e99f8b3afd4862846ad531f7]
 = No ability to show bridge table =

@@ Line 29: / Line 29: @@
 = RFC3021 /31 links =
-Mikrotik doesn't support this.  This is an over 20 year old RFC.  Come on.
+<s>Mikrotik doesn't support this.  This is an over 20 year old RFC.  Come on.
-https://forum.mikrotik.com/viewtopic.php?p=163163
+https://forum.mikrotik.com/viewtopic.php?p=163163 </s>
 = /export changes at random across different firmware =

← Older revision		Revision as of 06:22, 29 November 2024
Line 1:		Line 1:
		+	[[Category:MikroTik]]
		+
	This is a list of basic failures that I've found MikroTik Routers to have. This is by no means exhaustive.		This is a list of basic failures that I've found MikroTik Routers to have. This is by no means exhaustive.

@@ Line 3: / Line 3: @@
 = IS-IS Support =
-Mikrotik doesn't support and will not support ISIS.
+<s>Mikrotik doesn't support and will not support ISIS.  </s>
 The stated [https://forum.mikrotik.com/viewtopic.php?t=30587#p149066 reason] is it's not a "coooool protocol" like OSPF.
 = No ability to show bridge table =

← Older revision		Revision as of 17:01, 11 August 2022
Line 31:		Line 31:

	This means config backups are basically worthless unless you can input them manually and see what breaks. There's no revision testing on it either by MT.		This means config backups are basically worthless unless you can input them manually and see what breaks. There's no revision testing on it either by MT.
		+
		+	= 4 byte ASN =
		+
		+	Per [https://mailman.nanog.org/pipermail/nanog/2022-August/220138.html this message] on NANOG, they can't do 4 byte ASN's

← Older revision		Revision as of 04:35, 26 March 2022
Line 25:		Line 25:

	https://forum.mikrotik.com/viewtopic.php?p=163163		https://forum.mikrotik.com/viewtopic.php?p=163163
		+
		+	= /export changes at random across different firmware =
		+
		+	/export is not idempotent between OS upgrades on the same hardware.
		+
		+	This means config backups are basically worthless unless you can input them manually and see what breaks. There's no revision testing on it either by MT.

← Older revision		Revision as of 04:24, 26 March 2022
Line 1:		Line 1:
	This is a list of basic failures that I've found MikroTik Routers to have. This is by no means exhaustive.		This is a list of basic failures that I've found MikroTik Routers to have. This is by no means exhaustive.
		+
		+	= IS-IS Support =
		+
		+	Mikrotik doesn't support and will not support ISIS.
		+
		+	The stated [https://forum.mikrotik.com/viewtopic.php?t=30587#p149066 reason] is it's not a "coooool protocol" like OSPF.
		+
		+	= No ability to show bridge table =
		+	In a bridge wireless network where CPE are bridging the LAN port to Wireless, then to the AP, and out the AP Ethernet port, one cannot find the MAC address of the CPE radio and what MAC's it's bridging to the AP. There has to be a table of this internally in the AP, but it is not exposed. This makes locating a misbehaving MAC address complex as you have to look at each CPE device's MAC table.
		+
		+	Alvarion/Cisco/Symbol/Karlnet/Canopy has had this since like 1995.
		+
		+	= VRF table ignored for local responses =
		+
		+	In a VRF, where you have a traceroute going through it, MT will source it's ICMP TTL packets using an IP from the main routing table. This means anyone tracrouting to the VRF will be able to see IP it's going over, or if it's a private IP that the main table has, it will likely just show "* * *" as the IP will be unreachable.
		+
		+	This is a [https://forum.mikrotik.com/viewtopic.php?t=78816&start=100 known issue].
		+
		+	https://old.reddit.com/r/mikrotik/comments/5ixk1u/intermediate_hop_dont_show_in_traceroutes_when/
		+
		+	= RFC3021 /31 links =
		+
		+	Mikrotik doesn't support this. This is an over 20 year old RFC. Come on.
		+
		+	https://forum.mikrotik.com/viewtopic.php?p=163163