MikroTik

That is the beauty and the curse of RouterOS - sky is the limit. But the "sky" here is the administrator, who should be aware that possibilities are endless, but hardware resources are not. If we remove features, then others can not use them in different combinations of services or even th...

To which issue/s introduced in v7.17 do you refer to? What's new in 7.17rc8 (2025-Jan-15 08:19): !) webfig - redesigned HTML, styling and functionality (additional fixes); *) system - fixed crypto for Alpine CPUs (introduced in v7.17beta1); Once again, I will repeat: I'm smelling a "If we say i...

rzirzi, oreggin - Thank you for your reports. We have discovered that Alpine CPU ARM64 devices does not work with GCM AES encryption. We are working on a fix.

If the setting is set to "auto", then it works as "disabled" unless you enable BTH functionality. If you enable BTH, then it will automtically enable Cloud service, since it can not work without it. It seems that your router simply tried to reach Cloud. Maybe it was not reachable...

Activation is intended to be "started" while command is being viewed. Thus, the error is not some kind of parameter, but an informative message. Why would you need to get it into a variable?

Yes, device-mode is currently not implemented in GUI. These are not issues/bugs.

My apologies for the "wrong" explanation. I did mean smaller than /64 - 65, 66, ... Address pool must be /64 or smaller to be divided into /128 prefixes. Currently, IPv6 pool does not support "more prefixes" per pool. I'm still not understanding somehow. I interpret what you said...

Address pool must be /64 or smaller to be divided into /128 prefixes. Currently, IPv6 pool does not support "more prefixes" per pool. Has anyone gotten *) dhcpv6-server - added IPv6 address delegation support; working yet? I see in Winbox where there is now an Address Pool setting. But I c...

See the changelog:

*) ovpn - added VRF support to OVPN server (server menu now supports multiple entries and previous server configuration is automatically imported);

That first OVPN server that you have is the default server, same as there was one before.

syue87, Arthur2000 - Please send supout file from your router to support@mikrotik.com. deadmaus911 - We will look into this forwarders issue. Ullinator - Please send supout file from your router to support@mikrotik.com. If you refer to the old CAPsMAN - are you sure that wireless package is install...

Anyone who is experiencing these problems with "No Internet" after upgrade to beta5, please generate supout file while running beta5 and send this files to support@mikrotik.com.

You must use address-pool instead of prefix-pool and address pool specified prefix-length must be /128. Other than that you have gotten the idea correctly - IPv6/ND must be used to advertise managed-network for end devices. *) dhcpv6-server - added IPv6 address delegation support; I'm trying this ne...

Nothing to resist. That is the whole point of beta releases. Bunch of new stuff to test which can break something else. Otherwise, we would not release them at all like in the past and just prepare stable rc. Again - betas are released to test specific fixes, not the general system stability.

Do not worry, we are working on a new beta releases, new features and improvements - including device mode and others. We have never promised to release a new beta every few days. Nobody is hiding here from anyone - we are working! Beta is beta - it is released so you can test fixes and new features...

There was a possibility that if you use an ARM router with wireless that has 128 MB of RAM and is using wifi-qcom-ac package, not wireless, then simply router could run out of RAM resources causing the router to reboot. That happened just because a RAM usage slightly increased in these releases. We ...

itimo01, bjoerns - Can you please send supout.rif files from your router to support@mikrotik.com?

There was a possibility that OVPN router can get a "Kernel Failure". If you have a router running OVPN and it sometimes reboots due to a Kernel Failure, then upgrade and see how it goes. If the problem remains, then of course contact support@mikrotik.com and send supout file.

You can download basically any RouterOS version from our upgrade server. Just change the version number in URL.

https://upgrade.mikrotik.com/routeros/7 ... -arm64.npk

Thank you. Issue reproduced. We are working on a fix. Seems that problem is present if you configure 6to4 before adding any IPv4 configuration. Basically - while setting up. On Topic: 7.16 RC1 - Found an annoying bug with the 6to4 tunnel interface. I have VRRP on-backup and on-master scripts that di...

As stated in the post and many other posts in other version topics - please keep this topic related to its purpose. This is v7.16 topic. For other discussions, open up a new topic. The bigger half of posts in this article is not in any way related to this release.

This is basically WInBox release for future use. At some point, 3.41 will become the minimal supported WinBox version. For end user, this release does not change anything.

The beta versions are released in order to find the bugs! The more, the better. That is the whole point of betas - find issues before the stable releases. Otherwise we would not release them at all. You should use betas if you agree to risk and help for us to find issues of different kind of sets of...

Static DNS querying will be fixed in the upcoming RouterOS beta release. Please remember - this is beta. Released for testing new features and fixes. Some services might not work properly, and these version should not be used on important routers. As for the DoH - we are looking into this and will u...

That was the solution up until now. It was not enough for some users. Previously, changes were divided "change in this release" and "other since previous stable".

May I suggest splitting change logs into additions/changes and fixes?

https://forum.mikrotik.com/viewtopic.php?t=208039&sid=9c3dc112466a03b021281efdae15b10b#p1078346 WireGuard creates a new connection when it communicates to the other end. Thus, standard load balancing will not work which handles replies, not new connections. A possible solution would be to add-sr...

The issue with wifi access-list or in other words, wrong signal levels recognised at the beginning of wifi client connection, has been reproduced, and we will solve it as soon as possible. We are very sorry for any inconvenience caused.

In simple words - we discovered that RouterOS internally did some unnecessary checks on specific situations under the hood, so we improved some part of code making routing processes more agile. You should notice the difference on large routing setups, not on a home router. *) route - improved system...

daaf - Can you please provide supout files from your access points to support@mikrotik.com? Please make sure that files are generated at the moment when APs are not working properly.

The beta/rc changelog represents changes since the previous stable release. So if there was an additional fix for some feature added, we do not write it as a new chagelog entry on each and every beta/rc release. We simply "move it up". So what was changed regarding adlist or media feature ...

As RFC states, the DUID must be 2-octets long and be followed with at least one octet with the identifier itself. So the minimal length MUST be 2+1=3 octets: https://datatracker.ietf.org/doc/html/rfc8415#section-11.1 DUID Contents A DUID consists of a 2-octet type code represented in network byte or...

The PPP RADIUS accounting issue is reported to our development team and will be resolved as soon as possible.

UpRunTech - Can you please reproduce the wifi problem with authentication/roaming/etc. and generate supout files on your APs and CAPsMAN? Send all these files to support@mikrotik.com and let us know MAC address of the problematic wifi client. Same rules apply for anyone else having difficulties to ...

This change came together with a ton of changes in a package of: !) system - added support for AMPERE (R) and ARM64 CHR installations (new ARM64 CHR image available); Yes, of course, there are more git commits in the code than entries in the changelog. Many of them are bundled into one generic log e...

RouterOS changelog covers all the changes introduced in any particular release, despite ones that are there for products which are not released yet or features that are "on the way". The fact that we list in the changelog what was actually done, of course, differs of listing all the possib...

These versions are of course installed on routers in the factory. So new units will have fixed/improved default configuration.

*) system - general work on optimizing the size of RouterOS packages;

hello everyone, is there a chance to be able to install it on 16 mb devices? I don't see size reduction anywhere in the changelog

Sit75 - This seems to probably be a story as old as the planet Earth - RouterOS and its great possibilities which come with a great responsibility. We more or less do let the system administrator to do any kinds of nonsense on the router, but you do that on your own risk. It seems that the reply fr...

Please do remember that "increase in RAM usage" in 99% cases is a normal behaviour - that is why such a thing as RAM exists. Questions here are: 1) Does the increase stop at some point and remains the same? If yes, then some service has "max RAM/cache" setting or built-in limit s...

Although the mentioned CAKE issue was caused by this bug, it was not limited to CAKE. However, mostly CAKE/Codel/PCQ/SFQ did let the issue to "appear" more easily. In short - queues handle packets and if the combination of queue configuration and processed traffic did meet some very specif...

It simply means that when these ARM devices were designed and released, such package did not exist yet.

We are stilll doing our best to fit it in there.

Package wifi-qcom-ac for ARM devices has always been an "extra". Yes, using ARM 16 MB device with wifi-qcom-ac will not leave you with much free space left. But this package for a reason is not installed "out of box". If you use such combination, you know that you will be living ...

As mentioned before - IPv6 accounting must be enabled under PPP/AAA menu. If you can not make it work, then please as always contact support@mikrotik.com. Debugging should not be done here in general version release topic. https://help.mikrotik.com/docs/display/ROS/PPP+AAA "Enable IPv6 separate...

Did you see the last changelog? This option was just added in this release.

*) ppp - added "enable-ipv6-accounting" option under PPP AAA menu (CLI only);

Here is the correct Delegated-IPv6-Prefix usage example: /user-manager/attribute/print detail where name~"Delegated" Flags: * - default 8 * name="Delegated-IPv6-Prefix" default-name="Delegated-IPv6-Prefix" vendor-id=standard type-id=123 value-type=ip6-prefix packet-type...

These fixes had nothing to do with BTH directly. We added WireGuard logging. Turned out that WireGuard tries to connect to peer even if it does not know the peer IP. Then it tries to connect to IP 0.0.0.0. This fix changes that and router will not try to connect to 0.0.0.0 if it does not know the re...

Please keep in mind that this is beta . This version is released mainly to test particular fixes. For example, test Media feature, Traffic Flow fixes, SFP fixes or any other ones. As you can see in the changelog - "space" issue is being addressed . This is not a stable release yet. Nobody ...

Version 7.15 will include WireGuard peer functionality "responder". Then you will be able to mark your peer as "responder". Then the peer will not spam your log, if you enable this option manually.

WireGuard fix solves an issue where RouterOS was trying to connect to peers which have not been used yet and there is no known endpoint-address. WireGuard is a bidirectional tunnel. Once you connect peer, it knows "last remote endpoint" information and tries to connect to it. Fix solved th...

Missing "routeros" directory: https://upgrade.mikrotik.com/routeros/7.14.1/CHANGELOG Hi, Access to CHANGELOG information via CLI does not work: [admin@MikroTik] > :put ([/tool fetch "https://upgrade.mikrotik.com/7.14.1/CHANGELOG" output=user as-value] -> "data") failure...

What's new in 7.14.1 (2024-Mar-08 14:50): *) bgp-vpn - use VRF interface as gateway for leaked connected routes; *) chr - fixed Xen and Vultr missing ethernet (introduced in v7.14); *) chr - fixed bogus messages printed out while booting up the system (introduced in v7.14); *) console - fixed do/wh...

As mentioned on every version topic - please keep the topic related to the issues that are introduced just in this release and new features. Logging rules have always worked as "and" filters. You have unlimited options there. For example, "info" will log info messages, but "...

Link to the new IP/Media feature manual: https://help.mikrotik.com/docs/pages/viewpage.action?pageId=237699479 Also new feature - IP/DNS/Adlist: https://help.mikrotik.com/docs/display/ROS/DNS#DNS-Adlist Updated switch QoS manual (see WRED, ECN): https://help.mikrotik.com/docs/pages/viewpage.action?p...

The comment from w0lt was correct. In order to disable specific topic logs, go to System/Logging and open, for example, "info" topic. Add "!wireguard" to it. All info logs, except WireGuard, will be logged now. Yes, these are new logs, nothing changed in the WireGuard behavior. S...

It is impossible to provide precise release notes for everyone's needs. As we have described in many topics before - we do write in release notes what did we fix, not how the problem might have appeared for the user. We do write what was changed under the hood, not on "user experience". In...

Willi - Please do the following: 1) Upgrade your router to v7.14rc or later (if one is available when you decide to do this); 2) Generate supout file before you add queue; 3) Add queue; 4) Generate another supout file; 5) Execute reboot command, make sure that the problem is still there, generate t...

Ullinator - Did you manage to create a support ticket? We would like to check out what is going on here for you, since the issue clearly is caused by an upgrade.

In other words, usually changes with "!" describe that behaviour will change in the RouterOS after an upgrade. For example, here SMB is removed from one package and mover to other one. As for the importance of fixes - yes, they are indeed all equal. Because what is something very important...

Usually such issues are fixed even before CVE is created. Thus, there is no CVE number to refer to. When there is an actual CVE available at the time of the release, then it is mentioned in the changelog. You can go through changelog history and see that by yourselves. We do not "update" c...

The fq_codel type is set for wired (Ethernet, SFP) interfaces in order to reduce bufferbloat. No interface queue for LTE interface itself. I think the "failure: non rate limit queues are useless on this interface" warning is just if you try to assign a queue to the bridge, as opposed to ju...

RouterOS version 7.14beta has been released on the "v7 testing" channel! Before an upgrade: 1) Remember to make backup/export files before an upgrade and save them on another storage device; 2) Make sure the device will not lose power during upgrade process; 3) Device has enough free stor...

What do you see on the AP in logs? Can you provide supout file to support@mikrotik.com? Plenty of Tuya devices connected to MikroTik routers all over the globe. This definitely is not a global incompatibility issue.

If you do try to upgrade/downgrade RouterOS manually, then router do expect 1:1 packages match. If that is not possible (for example, wifi-qcominstalled on 7.13) then on packages menu schedule these packages for uninstall. Uploadpackages that you want to install and execute downgrade command. If tha...

Version 7.13 has been released:

viewtopic.php?t=202423

RouterOS version 7.13 have been released in the "v7 stable" channel! Before an upgrade: 1) Remember to make backup/export files before an upgrade and save them on another storage device; 2) Make sure the device will not lose power during upgrade process; 3) Device has enough free storage ...

Autosupout is the same supout file as manually generated, but is generated automatically when there is a software error. In short, there are such possibilities: 1) Router rebooted due to an out-of-memory condition or Kernel Failure (not on Watchdog reboots since Watchdog is a reboot done on purpose,...

We have received a single report about "non-working" WireGuard in v7.13 on support, and it does not seem that it has anything to do with the software, but either a networking or configuration problem. If there are any other setups where WireGuard worked just fine in v7.12, but does not wor...

Hopefully, we have managed to reproduce the same problem with "defconf" generation for AX routers. It is a cosmetic, harmless issue that can occur randomly on any upgrade/downgrade, package installation/removal. We will try to fix it in upcoming RouterOS releases. The error has nothing to ...

Error about defconf generation process is just an outcome of many possible reasons. Simply "hey, there was some kind of error". As you can see in changelogs, defconf is updated quite often. This error only says "there was something wrong here". It is not a single issue. Quite oft...

No, not the same. Even better, and includes more fixes!

What's new in 7.13beta3 (2023-Nov-24 13:52): *) bridge - added automatic "path-cost" values depending on interface rate; *) bridge - fixed HW offload enable with multiple switches (introduced in v7.13beta1); *) bridge - improved HW offload enable; *) certificate - fixed CRL check (introdu...

WinBox in RouterOS is not just the winbox.exe. WinBox is a protocol that you use to transport RouterOS data from router to application, which includes winbox.exe, mobile applications and tne Dude. We have managed to reproduce the memory leak introduced in beta2 release. We will fix it as soon as pos...

We have managed to reproduce the memory leak introduced in beta2 release. We will fix it as soon as possible. It is caused by opened WinBox sessions.

Let us call this "luck" this time. But it would not be correct for everyone to post their findings here and assume that there is a bug and scare away others. When in the end, the issue for a particular user had nothing to do with the release/software. That is our goal - to not scare away o...

About "many" menus. In the past, you had menus - CAPsMAN and Wireless. Always. If you added wifiwave2 package, then you also had the third menu for wireless. Now in "worst" case scenario you have two menus (less than before) - wireless and wifi. Of course, each of these feature s...

Both CAPsMAN systems can work at the same time. Yes, they use the same port, but they differ the "call" from CAP and recognise which one must manage the CAP. Common mistake might be that old CAPsMAN is trying to generate certificate on a system where WiFi CAPsMAN was already made on older ...

This upgrade does not in any way free disk space. However, on a device which does not need to have wireless package, for example, CRS which do not run CAPsMAN, you know have separate wireless package. It is not a part of bundle any more. You can now uninstall it, and you will not only save disk spac...

Wifi menu is included in the bundle as described in changelog. All routers will have "WifiI" menu. You can not run router without system (a.k.a. bundle) package. If you require "legacy" wireless (either router requires 60 GHz support, legacy wireless support or you need to use ol...

Wireless package and wifi package can be installed on a router at the same time, but one of them will be disabled. Both can not work at the same time. Have a look at the "/system package print" and see which package is active. Wifi menu is a configuration menu and does not care about extra...

If you install wireless and wifi packages at the same time, then of course there are two menus. You can run both of them at the same time as separate solutions on a single router. In 99% of cases you will require either wireless or wifi package and then there will be only one menu. Uninstall the pac...

Several complaints here about specific issues - Zerotier, Wireguard, etc.
but Zero tickets about that to support@mikrotik.com. Please remember that actual "bugs" must be reported to support@mikrotik.com complemented with logs, supout files, etc.

Now also upgrade from ARM64 routers with installed wifiwave2 package should work. Sorry for any inconvenience caused.

Please keep this and other version topics related to the particular version. Issues that were present in older versions should be reported to support@mikrotik.com and/or discussed in separate forum threads. These forum topics are created in order to find "what got broken". There is no need...

Yes, these devices will install wireless package automatically and will also be shipped from the factory with wireless package. You can install wifi-qcom-ac package manually. - I believe @DanMos79 is asking for an alternative DIY wireless card compatible with WifiWave2 drivers for RB4011, if availab...

By the way, if someone decides to upgrade to beta and then wants to downgrade back to, for example, 7.12. You can execute "uninstall" command for wifi or wireless packages and run check-for-updates with ignore-missing parameter. Bundle to bundle downgrade will still work or downgrade for a...

Unfortunately, it is not possible. If you need both - use wireless.npk. If you are satisfied with using just 5 GHz, then wifi-qcom-ac will work for you. Functionality in wifi (old wifiwave2) that has been changed is described in the changelog. Still, wifi package does not include drivers for RB4011 ...

Yes, WPA3 on AC devices, etc. Also old and new type of CAPsMAN can be managed on the same router. Not as a unified mechanism, but two separate and parallel systems on the same router.

Njumaen - Copy actually works. Simply, you do not see the "highlight". We will try to fix this in the future WInBox releases, but at the moment try to highlight the text, press right mouse button, select copy, and you are good to go. As for the "client-allowed-ips" do you mean t...

For those who experience issues with the DoH service? Is "/certificate/settings/set crl-use=" set to "yes" on your routers? If it is "yes", then do DoH work if you change value to "no"?

sas2k, DeGlucker - Please send supout files from your non-working DoH client routers to support@mikrotik.com. Are you sure that log does not already tell what is wrong here?

This is actually already fixed in 7.13 which is coming soon. Deprecate message will not be sent if actual prefix is re-used.

Why is that a problem? That is intended behaviour at the moment. Opened SUP-133893 where RA deprecate messages for an active RA are sent at the same time as the active RA. Workaround: toggle "use interface duid" to temporarily get a new PD then it reverts back to the actual PD and the RA w...

What do you mean with "corrupt"? Downloads just fine for me (https://download.mikrotik.com/routeros/ ... l-7.12.exe).

The Dude client is corrupt on the download page!

https://help.mikrotik.com/docs/display/ ... pendentNAT

Couple of questions
(1) what is "ein-snat" and "ein-dnat" ( searched mt docs and no match ).
(2) CLI winbox import & export capability - will this get ported to winbox eventually?

The issue with USB stick changing its name on RB5009 is a known issue, and we will try to fix it as soon as possible. It is not caused by version 7.12. . Please let us know through support@mikrotik.com if any one of you experience similar issues on a router which is not RB5009. Please make sure that...

These values are there for a purpose. Is there a problem with them? Came together with - "webfig - improved Webfig performance and responsiveness". Minor webfig error with RC2 (not sure if it happened on RC1, screenshot is from RC2), there's an erroneous TX/RX rates (that keeps updating) o...

Since version 7.9 few processes were not working properly and could have caused an extra load on single CPU core, compared to older versions. That was caused due to the fact that parallel processes were not started as separate tasks. For example, this did affect SSL processes, certificate management...

On iOS 17 devices, established IKE2 peers will disconnect after 24 minutes of being connected. The disconnect happened after rekeying sent by the responder and then rejected by the initiator. ROS = 7.11.2, 7.12rc1 Responder PFS= none 14:13:28 ipsec --->IPSEC: -> ike2 request, exchange: CREATE_CHILD...

Sorry about that. Changelogs are fixed now.

What's new in 7.12rc2 (2023-Oct-16 17:50): *) bridge - fixed bridge host ageing timeout behaviour (introduced in 7.12beta8); *) led - fixed CRS312 Ethernet port LED functionality (introduced in 7.12rc1); *) led - fixed 5G modem mobile network category LED colours; *) ospf - fixed OSPFv3 authenticat...

Do not worry, rc2 is coming soon. No need for intrigues. Simply we do release the next rc usually when all the known regressions are resolved. We are not there yet but will be soon.

Also RouterOS upgrade will be required. BTH is not yet released as stable feature. Will work just fine in upcoming betas.

While UI for BTH is gone as expected, I notice BTH config from 7.11rc builds remains and works – this seems right, since that part is just WG config. But is the DNS for BTH going to remain active? e.g. I have couple working peers using the <sn>.vpn.mynetname.net to resolve the router's public IP. I...

We had three options - release BTH as is, delay 7.11 stable just due to the BTH or remove BTH. We did choose to remove BTH as we can not call it "stable" yet and move a step closer to 7.11 (stable) for those who do not care about BTH. We would like to call it a win-win. BTH will be back on...

DNS changes are listed in the changelogs. You can re-read them here. You are referring to versions 7.4,7.5,7.6,7.7, 7.8, and others. There are plenty of changes listed in the changelog: https://mikrotik.com/download/changelogs So no, we did not hide anything there. Just described hundreds of code li...

It is quite clear that fixes go into RouterOS without mention in the changelog. If only because some thing suddenly appear "broken" without any mentioned change in that function or anything related to it. The changelog is only a recap of the most important changes in that version, otherwi...

To everyone! Please remember - this is a user forum. Report bugs to support@mikrotik.com immediately, if you are sure that the issue you have is a bug. This will get things done much faster!

We are very sorry if you felt offended in some way. However, I do not see why. You were just asked few additional questions in a polite manner which you did refuse to answer. Yes, the problem was not - wireguard does not work with any IPv6 allowed addresses. Particular addresses and specifi routers ...

What's new in 7.11rc2 (2023-Aug-03 10:50): *) certificate - fixed trust store CRL link if generated on an older version (introduced in v7.7); *) console - improved stability when canceling console actions; *) ike2 - fixed ECP521 DH group usage (introduced in v7.11 beta1); *) lte - fixed R11e-LTE6 &...

Put decimal to hex function as well to reduce confusion. Decimal 127 output must be 7F not 313237. Yup. If someone had time for =rot13.... num to hex seems pretty reasonable... Basically, :convert to=hex should be type aware. At least for input arg is typeof=num... Right now :convert only deals wit...

The Wireguard interface is always in a "running" state. You can connect multiple peers to the same interface. There is no easy way to determine if the interface should be up or down.

Most likely you are looking for the Wireguard peers parameter "last-handshake".

Yes, LE does not work currently in RouterOS on an IPv6-only network. This is not implemented yet. This particular scenario is not in any way related to the v7.11rc release.

Are you sure that your firewall rules list is ordered by column "#"? It is not allowed to move rules if the list is not sorted by ID.

Yes, the RC release contains all the fixes that you have ever seen in v7.11. Now upcoming v7.11 releases will be only RC releases with cherry-picked fixes for major issues or regressions introduced in 7.11. All other fixes will be added only in v7.12beta. When RC will become stable (better than 7.10...

Version 7.11rc1 has been released.

viewtopic.php?t=198228

RouterOS version 7.11rc has been released on the "v7 testing" channel! Before an upgrade: 1) Remember to make backup/export files before an upgrade and save them on another storage device; 2) Make sure the device will not lose power during the upgrade process; 3) Device has enough free st...

This is done on purpose and supout file includes export, not "/user export". So the supout does not contain any user configuration information besides groups. This works properly as designed. You can see user configuration if you run export manually

Regarding the OVPN service not working with 7.10. We have found the issue and will release 7.11beta with a potential fix soon. However, the issue is not a bug exactly. If you are running OVPN service with 7.10.2 and it is not working, check if you use OVPN in "IP" mode, but have specified ...

As stated in the CVE - "MikroTik RouterOS stable before 6.49.7...". Yes, 6.49.8 is built on 6.49.7. Thus it includes the same fix.

6.49.8 has been promoted to the long-term channel. At the moment, for v6, the long-term and stable releases are both the same - 6.49.8. There is a little mixup with the download page which will be fixed as soon as possible. The only difference between stable and long-term releases is the name under,...

Code: Select all
*) mpls - improved MPLS TCP performance;
What can this mean?

It works better now

Anyone who has upgraded to 7.10 and encounters DNS crashes, can try using the following code to disable the dns-to-address-list configuration first: /ip dns static set [find where address-list!=""] address-list="" It is known that version 7.10, due to the addition of endpoint-in...

Regarding the OVPN issue with "Problem accepting server-pushed peer-id: parse/range issue"! We have managed to reproduce the problem and are working on a fix for it.

As it has been already for several years, the beta/rc changelog has been written as you would read it from previous stable release (at the moment 7.9.2) point of view. Since between beta/rc releases there have been multiple additional fixes for BFD, the same changelog entry has been repeated.

We are aware of the issue with AX Wireless becoming unavailable/inaccessible at some point. Believe it or not, we can not reproduce this locally at the moment in order to fix the issue. At the moment our assumption is that some specific traffic or client must be present in the network in order to tr...

If you experience problems with OVPN even after 7.10rc installation, then please let us know about that through support@mikrotik.com. Several issues regarding the OVPN service have been addresses in v7.10.

meconiotronic, msilcher - Have you opened support ticket regarding this issue? If not, then please do so and provide supout file which would be generated after the problem has been present on your router. We have seen several reports in this and other topics about problems with wireless. Please not...

If you experience system reboots with this or actually any other RouterOS release, then please send supout files from your routers (from the latest RC and generated after the router has rebooted by itself at least once) to support@mikrotik.com. Users in the forum can not see in supout files the actu...

Routers are made of hardware, if new chips, for example, NAND, are used in order to manufacture routers, then the minimal supported RouterOS version must be bumped up since support for that chip can be added only in the latest releases. MikroTik has never bumped up the minimal supported RouterOS ver...

Please try to avoid using old versions for new installations. Upgrade your new router to the latest stable (at the moment 7.8 ) and your old router to the same version. Then transfer configuration. Of course, first, read this article: https://help.mikrotik.com/docs/display/ROS/Upgrading+to+v7 Also r...

tpedko - If we push all of the possible fixes in every release, then we will never reach a "stable" release. We do, at some point when we consider all of the new features quite stable, build an RC version. Then rc1 is released. After that only fixes that polish particular release tree are...

Rc versions almost always will include fixes for problems introduced in a particular release tree. That is the whole point of "release-candidate". Once rc1 is released, then other releases will be further attempts to stabilize the version before the "stable" release. Other new fi...

At the moment Ed25519 key import/export is available only under the "/ip/ssh/" menu. The format must be PKCS8. An additional fix for the "/ip/ssh/import-host-key" function will be available in rc2. Please note that ssh-keygen ignores the PKCS8 format parameter for Ed25519 key, yo...

Can anyone please send a supout file from the problematic router to support@mikrotik.com? We would like to figure out what is going on here.

Maggiore81 - Why do you say so? If we sum up the topic, then basically we have found out that few SFP modules are not working properly, which were working on v7.7. Rest of the issues discussed here are already known issues from previus versions, misconfiguraiton, or minor bug reports about trivial ...

denisnk - Thank you for your report. Although it is not version related. We will try to fix this as soon as possible. Yes, several devices might not show this on WinBox. parham - Please contact us through support@mikrotik.com. These files are not missing on upgrade servers. We would like to figure ...

ZeroTier and WW2 packages are present on download servers and must be upgraded automatically if the "check-for-updates" feature is used. If that is not happening for someone, then please contact us through support@mikrotik.com.

Regarding the missing changelog entries - the release does not differ from the rc3. Simply changelog has been updated a little bit. Some changes were merged or rewritten. There is no need to look for something more than simple changelog improvements.

Yes, the Internet Detect issue is not solved yet. When it will be fixed, then that will be mentioned in the release notes. We are aware of a problem with Detect Internet. Please keep this topic related only to v7.8 and the issues introduced in it compared to 7.7.

Jotne - Please do not create a new ticket even if there was an attempt to fix your issue, but it did fail. Keep all of the conversations about a single issue within a single support ticket. Report support issues on separate tickets (single ticket, single issue) but do not start multiple tickets for...

In v7.7 you still can not see the default route added by SLAAC, but that will be fixed in v7.9.

Ability to specify domain name with some kind of a "none" action is on its way. We do not know how it will look yet, but you will be able to add dummy DNS record that will override DNS name lookup. Yes, nobody is forced to upgrade RouterOS on every stable release. Release notes are availab...

Pl07R3K - Not sure what was the purpose of this message. Building multiple rc releases before stable build is exactly "stabilising". Main goal on eacn and every new stable is to make it better than previous one. Of course, there are no bugfree versions, but we do not plan to delay many fi...

mducharme - New flags and properties are added to routing table. Default SLAAC routes will be there in v7.9.

Jotne - My apologies for this mistake, LEDs will be fixed in v7.8, not v7.9.

DenisPDA, ivicask, smotrov, kev445, own3r1138, curtdept, own3r1138, ErfanDL, username2, mszru, Brendon - Please send the supout file from your router to us to the support@mikrotik.com e-mail address or use our client portal https://help.mikrotik.com/servicedesk/ DjM - We discovered an issue that co...

dksoft - We will see about that... New packages are included in stable versions when we can consider them "stable". At the moment we can not promise that ROSE-storage will be included in v7.8, but we will do our best in order to make that happen. Of course, even if it will not be released...

What kind of algorithms do you use? Starting from the RouterOS v7.7 some of the very old mechanisms as, for example, pkcs#7 encryption method "pbeWithSHA1And40BitRC2", are not supported, since nowadays they can not be considered as "secure".

memelchenkov - Please send supout file from your router to support@mikrotik.com. Please note that your router did fail while running v7.6. The issue is not caused by v7.7.

Version 7.7 has been released:
viewtopic.php?t=192427

Version 7.7 has been released:
viewtopic.php?t=192427

RouterOS version 7.7 is released in the "v7 stable" channel! Before an upgrade: 1) Remember to make backup/export files before an upgrade and save them on another storage device; 2) Make sure the device will not lose power during the upgrade process; 3) Device has enough free storage space...

What's new in 7.7rc5 (2023-Jan-11 13:20): *) dns - fixed CNAME reading from the cache (introduced in v7.7rc3); *) dns - fixed incorrect TTL=0 reporting for cached entries; *) ike2 - added support for ChaChaPoly1305 encryption; *) port - fixed R11e-LTE6 port mapping; Please keep this forum topic str...

We have tested "dig -t AAAA auth.split.io" type requests and can confirm, that replies have "Authority RRs: 0". However, that is the exact same behaviour in v7.6 and v7.7rc. Can anyone confirm that the services which are not working properly with 7.7rc are indeed working with v7....

Unfortunately, we still have not received any packet captures from the problematic scenario. If anyone is ready to share them, then please send .pcap files to support@mikrotik.com. Also please include supout file just in case.

Yes, that post was written before v7.7rc4 where we fixed that problem that I was referring to. I do recommend that we try to debug this problem through the support ticket first and then post the results in forum when there will be some actual information (verified facts) about the problem.

pe1chi - Your ticket was replied to at the same time when my previous post was made. At the moment there are no known and reproduced DNS problems for us (which would be introduced in v7.7). We do now that your ViaPlay service is not working as expected since 7.7rc3, but so far there is no informati...

We managed to figure out what are those "0.0.0.0" entries in DNS cache. First of all - 0.0.0.0 is not an IP address. That is just a WinBox visual interpretation of "empty" value. These entries in cache that does not have a type, data and flags are "unknown type entries"...

We have received several reports about issues with the DNS cache in v7.7rc but so far none of them have had some precise examples. Please, if someone can reproduce the problem with the DNS cache, then provide step-by-step instructions on how you manage to see the problem. At the moment we are not aw...

Up until v7.7, there was a difference between static DNS and static DNS regex entries. Once you had, for example, static A DNS entry, the cache also did take care of AAAA records and if there were no entries for that, then AAAA was not resolved. Regex did not do that. If you add A static record, you...

chiem - Can you please provide a simple static DNS entry example (from export) that has been broken ni v7.7?

Can anyone here please do the following: 1) Capture just the UDP RDP packets for a single RDP connection between two RDP devices from a failed connection in v7; 2) Do the same in v6 when the connection is working properly without any changes in configuration? Send these capture files to supprot@mikr...

kcarhc - If you refer to FWD DNS static entries that forward requests to another server by using the domain name as the server address, not the IP, then the issue will be fixed in the next release. If not, then please send an example to support@mikrotik.com or post it here.

We have been trying to reproduce this problem, but at the moment it seems that UDP timeout is a very good workaround for actual Windows Server issues. Of course, we want to get to the bottom of this. 1) Are all of the affected connections related to the Windows Servers? If yes, then which versions? ...

Thank you for your reprots. We have managed to reproduce 7.7beta9 DNS type=FWD entry issue and will try to fix it as soon as possible.

kcarhc, jhbarrantes - Can you please provide a precise example of the DNS forward rule which does not work with 7.7beta9? We can not seem to reproduce this problem with our regular tests. WW2 support for other architectures besides ARM is provided in this release strictly for CAPsMAN functionality ...

Yes, that was the issue for this particular "sudden" increased number of TILE routers rebooting. The problem was introduced in RouterOS v7. Most likely affected routers simply did not process any SCTP traffic before. From where did this traffic appear in your networks? Hard to guess. Maybe...

The particular issue has been resolved in v7.7beta9. If you experience Kernel Failures even after applying the fix, please contact support@mikrotik.com and send a supout file.

We have lately received multiple complaints regarding Kernel Failures while running RouterOS v7. First of all, please note that we can not ever be sure if multiple users are suffering from the same issue without seeing the supout file. We can talk much about concrete configuration and network struct...

We have managed to reproduce the issue with FWD regex DNS static entries. We are very sorry for any inconvenience caused. Fix is on the way!

rpingar - Yes. these changes should allow routing processes to consume more than 2 GB of RAM Rox169 - Please keep these version topics related to the issues introduced in the particular release. These are not meant for feature requests. own3r1138, fabeni, rpingar - Yes, this seems to be the same pr...

fabeni - Which version did you test before? It sounds like an issue solved in 7.6 "ppp - improved service stability when multiple users disconnect simultaneously". If you did still experience a such problem with 7.6 or 7.7, then please send supout to support@mikrotik.com.

own3r1138 - Please send a supout file from your router running v7.6 where such functionality would not be working although it did work in v7.5. ivicask - It seems that this is not related to 7.6 and did not work also in earlier versions. We are looking into it, however, this issue is not related to...

eddieb - Changelog did not list any changes that the issue would be solved. We will do our best to solve the issue as soon as possible. Meanwhile please keep this topic strictly related to the issues that are introduced between 7.5 and 7.6rc. The main reason why we create these release topics is to...

eddieb - Was something broken related to USB in specifically v7.6? Please keep this topic related to version. If the issue is not related to particular version, then please create a support ticket. mszru, rb9999 - As mentioned multiple times in the forum, we are aware of these issues and it is in o...

rpingar - Please keep this topic related to the version. It is in our plans, however, we can not provide any ETA. Unfortunately, it is not as simple as increasing the limit by changing its max value.

We are aware of the issues regarding the DNS cache and several LTE interfaces in this rc1 release. We are working on fixes and the rc2 release. So if your DNS service or LTE is failing, then we recommend downgrading your device to 7.5 until 7.6rc2 is released.

We have been trying to reproduce this problem in our lab with the latest RouterOS v7 releases and have not managed to notice such behavior. If anyone is still experiencing memory leak caused by DoH services with v7.5 or later, then please send a supout file from your device (generated while the prob...

rextended - If you tried to Netinstall ARM device and it either freezes before the installation process (you could see that on a serial console) or reboots itself before the installation process is started, then this fix should be the one that helps. In general, the fix should be safe enough so you...

This problem should be resolved in v7.4beta4. Please test and see if the fix is working properly for you.

Sorry for any inconvenience caused regarding the Netwatch service unavailability under CLI. This will be fixed in the next beta release.

Regarding the out-of-memory issues - we can not simply determine from logs the cause of the particular issue. Most of times when we receive such reports simply router/switch have a too complex configuration in order to run RouterOS, process traffic, and do everything that is configured on the device...

Version 7.3.1 with two quick fixes has been released!

What's new in 7.3.1 (2022-Jun-09 11:58):

*) rb3011 - fixed RB3011 going into a reboot loop when the SFP module is present (introduced in v7.3);
*) wifiwave2 - fixed WPA3-PSK authentication incompatibility with certain vendor and model devices;

twamuc - Could you please provide supout file to support@mikrotik.com? Generate a file after you have noticed such an error while running v7.3.

We have managed to reproduce the problem with RB3011 rebooting with this particular version and are working on a fix for it. The issue is somehow related to the particular SFP module presence. If you do not use SFP, then you should be safe.

For those who experience problems with the new window functionality - it is also working just fine for us. Indeed it seems to be Wine related. Have you tried to upgrade Wine first and then test this functioanliy?

hecatae - Congratulations, that was fast :) Znevna - We will re-check this issue with repartitioning. Sob - We will check what we can do about NAT netmap functionality in ROS. memelchenkov - Works for us. Can you provide supout file from this device to support@mikrotik.com which would be generated ...

Everyone... As also mentioned in previous release topics the error about default configuration when the ww2 package is used is a known issue and will be resolved in the upcoming releases. ARP ping issue will be fixed in the upcoming releases, however, at the moment there is no ETA for the fix. Ever...

RouterOS version 7.4beta2 has been released the "v7 testing" channel! Before an upgrade: 1) Remember to make backup/export files before an upgrade and save them on another storage device; 2) Make sure the device will not lose power during the upgrade process; 3) Device has enough free stor...

There are no changes since rc2.

Chaosphere64 - Yes, you are correct. We have just reproduced the problem and we will try to resolve it as soon as possible.
lyubomirtraykov - Have you reported this to support@mikrotik.com? If not, then open a new ticket and provide supout file from your router.

New version v7.3 has been released!

viewtopic.php?t=186567

New version v7.3 has been released!

viewtopic.php?t=186567

RouterOS versions 7.3 and 7.3.1 are released in the "v7 stable" channel! Before an upgrade: 1) Remember to make backup/export files before an upgrade and save them on another storage device; 2) Make sure the device will not lose power during the upgrade process; 3) Device has enough free s...

Hi, I keep having issues with the position of *some* windows inside winbox. They tend to move to the upper left corner of the enlarged window. Sometimes its only the pppoe-out1 or lte1 and sometimes its all of the opened windows, they get all mixed up, one on top of the other. It happens on my ubun...

Everyone - We are very sorry for the issue with ww2 package. We are working on a fix for this problem and will publish it as soon as possible.
Rfulton - Have you opened a support ticket regarding this issue and provided supout files problem the problematic devices?

Now the fix is also included in RouterOS v7.2.2.

This problem was related only to RouterOS v7 (v7 to v7 - upgrade, downgrade, extra package installation, package removal). It was triggered by internal algorithms of configuration maintaining processes and could not be workarounded or triggered whenever you want. A bunch of things had to be done in ...

Everyone , thank you very much for all the input regarding the configuration loss problem. For your reports in the forum and support tickets. By putting our heads together and combining all of your reports we managed to reproduce this problem and seems that we have resolved it. The fix is included ...

Everyone , thank you very much for all the input regarding the configuration loss problem. For your reports in the forum and support tickets. By putting our heads together and combining all of your reports we managed to reproduce this problem and seems that we have resolved it. The fix is included ...

Everyone , thank you very much for all the input. For your reports in the forum and support tickets. By putting our heads together and combining all of your reports we managed to reproduce this problem and seems that we have resolved it. The fix is included in v7.3beta37 and, of course, if it will ...

Beta 33? Out of the world version numbering.

How do you think where the fixes for 7.2.1 were tested?

For starters - this fix has nothing to do with the problem that some rare routers lose configuration after an upgrade. Still with all of your reports to support. we have not managed to reproduce the problem. As we thought before, most likely this problem is already fixed and affected are only router...

Search found 1666 matches