Didn’t fix the veth interface problem. Apart from that, no issues.
Currently, there are a few issues with Tx Stats, which are related to the following change introduced in version 7.20:
- switch - rework ethernet counters for 98DXxxxx, 98PX1012 and CRS1xx/2xx switches (add tx-drop-queueX-byte/packet, tx-drop-byte/packet, tx-queueX-byte to /in/eth and updated GUI);
The issue you saw is caused by a limitation in WinBox v3. It should display correctly in the latest WinBox 4.0beta35.
Another issue is that devices which do not support per-queue counters still show empty values in the GUI. This will be fixed in version 7.20.2.
All these are GUI-related issues.
4 Likes
7.20.1 presents the same problem with PPPoE for mass authentication of clients, you have to disable the vlans and wait for the goodwill to upload the PPPoE clients
Support file sent!!
At what version Mikrotik team will stop adding new features but will fix all the existing bugs?
6 Likes
7.200
3 Likes
I didn't see if it was reported yet, but the system history from Winbox isn't working, it shows a blank screen, from the console it shows the history without problems.
1 Like
Confirmed (and it's already with 7.20) but ... on 7.21b2 and 7.21b3 it does show (tested on RB5009).
So that bug most likely will also be ported forward ?
Hi, Auto Import (uploaded *.auto.rsc file) not works in 7.20.1. Worked in 7.19.4.
Error says:
executing script from sshd failed, please check it manually
(sftp-auto-run) cannot open import file, bad file name (:import; line 1)
Manually script executes succesfully (import filename.auto.rsc)
Uploaded file name does not affect the result
Model: CCR1036
1 Like
Experiencing issue with WPA button event flapping without touching that button after upgrade to 7.20.1 from 7.19.6 on Chateau 5G R17 ax:
> /log/print where message~"led settings changed by mode-button"
2025-10-16 21:01:13 system,info led settings changed by mode-button/script:toggle-leds (/system leds settings set all-leds-off=never)
2025-10-16 21:01:15 system,info led settings changed by mode-button/script:toggle-leds (/system leds settings set all-leds-off=immediate)
2025-10-16 21:03:55 system,info led settings changed by mode-button/script:toggle-leds (/system leds settings set all-leds-off=never)
2025-10-16 21:04:22 system,info led settings changed by mode-button/script:toggle-leds (/system leds settings set all-leds-off=immediate)
2025-10-16 21:09:38 system,info led settings changed by mode-button/script:toggle-leds (/system leds settings set all-leds-off=never)
2025-10-16 21:10:12 system,info led settings changed by mode-button/script:toggle-leds (/system leds settings set all-leds-off=immediate)
2025-10-16 21:15:36 system,info led settings changed by mode-button/script:toggle-leds (/system leds settings set all-leds-off=never)
2025-10-16 21:15:39 system,info led settings changed by mode-button/script:toggle-leds (/system leds settings set all-leds-off=immediate)
> /system/routerboard/wps-button/print
enabled: yes
hold-time: 0s..10s
on-event: toggle-leds
I had to disable this event to prevent this.
Router is on stable surface, it was not moved and nether WPA button pressed recently, is this possible HW button issue or ROS? Betting on the latter because this was not occurring on prev. ROS versions.
I can confirm it is broken also in 7.20 and working in 7.19.6
Same issue here.
Is there a known memory leak issue for containers with this release? I didn’t see anything mentioned.
Every time I run a container on my AX3 the containers itself memory usage is stable but the router memory slowly increases until the router reboots. I tried new containers, same issue. Stop containers running then there is no issue and router stays up for many days. Always reboots for me early hours of the morning and all I see is the general “router rebooted without proper shutdown” message as first entry in logs the next day. A difficult issue to resolve I’m sure. I’m using Adguardhome and mrtg containers if that matters. I also restricted container memory usage to 600Mb but the running container memory does not go anywhere near that and only uses around 300Mb in total.
After reboot, there should be an autosupout.rif.
Create support ticket describing your problem and include that file.
1 Like
Issue confirmed!
Same problem on hAP ax^2 on 7.20.1
Yes, you are right, I have also faced this issue
My suspicion of a memory leak with containers was incorrect. After no mention from anyone else I decided to rule out a power issue with my mini UPS by using the original power adapter for my AX3 and since replacing it and running containers my router has remained up(I’ve run this mini UPS with router for many years without issue). The memory consumption or gradual increase of memory from router is normal.
Hi! Has anyone experienced any WiFi issues after updating to 7.20.1 on older devices (wAP, hAP ac lite)? Clients, especially phones, connect and then disconnect after 30-60 seconds with the message 'disconnected, received deauth: sending station leaving (3)'. Reverting to version 7.19.6 fixed everything.
Best regards.