[admin@xxx-AP3] > /ip cloud/print
ddns-enabled: yes
ddns-update-interval: none
update-time: yes
public-address: 212.xx.xx.xx
dns-name: he80xxxxx.sn.mynetname.net
status: updated
warning: Router is behind a NAT. Remote connection might not work.
That is weird, @dibatech! I would expect a line mentioning BTH. And as your router is ARM based, no reason AFAIK why it is not there.
What version were you running befor the upgrade? Did BTH work on that version?
Last resort: netinstall:
https://help.mikrotik.com/docs/spaces/ROS/pages/24805390/Netinstall
Reset the router.
Back to Home options are back.
Thanks for the help.
I would have created a supout.rif and sent it to Mikrotik support. Too late unfortunately. This could have been very interesting. Maybe you were at 7.8.1 and not 7.18.1?
I have the same issue. (WAPAC) Deleting files does not free any disk space, console cleared, and cant reboot the device remotely. I find it truly shocking you cant reboot a device if there is no free disk available? I think there is an internal OS Partition which has filled up, and there is no way to clear out the usage such as temp files.
uptime: 6d19h56m24s
version: 7.18.1 (stable)
build-time: 2025-02-28 11:31:28
factory-software: 6.44.6
free-memory: 31.7MiB
total-memory: 128.0MiB
cpu: ARM
cpu-count: 4
cpu-frequency: 672MHz
cpu-load: 1%
free-hdd-space: 0
total-hdd-space: 16.0MiB
write-sect-since-reboot: 29625
write-sect-total: 388563
architecture-name: arm
board-name: wAP ac
I had a similar problem.
This is a consequence of the RoOs successive upgrade.
At some point, RoOS does not partition the disk correctly when upgrading from version 6 to version 7.
Mikrotik mentioned this in one of the descriptions for the 7th line.
The only option for you is to export the configuration to the console, copy and save it as a script.
Next, NetInstall 7.18.1 and loading the configuration through the console or script.
Thanks for the advice, It seems based on this that it is recommended to netinstall when moving from v6 to v7.
Yes, that certainly is the case. Netinstall and import an export made just before (not a restore of a backup).
That will free up space, and prevent unexplainable problems as well.
But we have some 2116 that were born with 7.8, that crashed brutally (bootloop) from 7.17.2 to 7.18
The ticket system allows submitting feature requests 
Besides that, RouterOS already offers a “configure session” in terminal mode! Most people do not know it…
When you enter a { in terminal mode, you enter a “block” (as in scripting) and you can enter commands, and when you enter } the block is closed and the commands are executed.
Only:
- it is not available in the GUI
- when a command has an error (other than a parsing error) it will not roll back the commands before it automatically
- there is no “test” mode other than the “safe mode”.
I’m seeing similar problems with several different CRS devices using S+RJ10 SFP+ modules.
When running 7.18 and 7.18.1 , the links using S+RJ10 very often never complete autonegotation and the links never come up. Other links using DA cables or other SFP+ modules work fine.
Sometimes, bouncing the port down and up will establish the links.
The links always come up with RouterOS 7.17.2 and lower.
SFP info:
sfp-type: SFP/SFP+/SFP28/SFP56
sfp-connector-type: RJ45
sfp-link-length-copper-active-om4: 1m
sfp-vendor-name: MikroTik
sfp-vendor-part-number: S+RJ10
sfp-vendor-revision: 2.16
My ISP advised me to set the speed on the port manually.
Also I want to try to enable the “Ignore Rx Lose” option. But remotely I don’t want to play this game 
The links always come up with RouterOS 7.17.2 and lower.
From 7.18 change log:
*) sfp,qsfp - improved initialization and linking;
Seems like the improvement is not so much an improvement for S+RJ10.
And it also seems MT does not test test their own SFP modules with their own ROS releases on their own devices.
S+RJ10 are only supposed to run with auto-negotiation on.
I’ve tried to trim the advertised rates, but that didn’t help.
Ignore Rx Loss seems to help, but I will not want to run an interface with that option enabled.
I’ve upgraded, and notice that my ipv4 NAT is masq to the same IP regardless of my srcnat rules.
The BTH dynamic NAT seems to be marked as “unknown” interface and it eating all of the masq?
I’m going to create a backup/regular wireguard user with full access.. disable the BTH and re-enable it.. see if the issue is fixed without me losing access via my primary BTH.
What’s new in 7.18.2 (2025-Mar-11 13:59):
*) console - fixed issue with file-name completion (introduced in v7.18);
*) container - fixed repository name handling to prevent redirect issues when basic authentication is used;
*) lte - additional fixes for eSIM management support;
*) lte - AT modems, improved redialing when modem lost connectivity without notifying host about APN status change;
*) netinstall - fixed socket reset (introduced in v7.18);
*) queue - fixed system failure when CAKE kind queue was configured but queue type definition does not exist anymore (introduced in v7.18);
*) wifi - improved stability for wifi interfaces;
*) winbox - improve graphing efficiency when communicating with WinBox;
Was the instability of CAKE that you previously mentioned really limited to having an interface with a CAKE queue and then deleting the queue type?
In the mention it seemed to be more complicated than that. Was it reduced to only this?
(i.e. can I go back to using CAKE in 7.18.1 without worry when I do not delete the type)
Updated HAP AX3 to 7.18.2 i just noticed this in log on boot
DoH server connection error: SSL: ssl: no trusted CA certificate found (6)
DoH server connection error: SSL: ssl: no trusted CA certificate found (6) [ignoring repeated messages]
DoH server connection error: SSL: ssl: no trusted CA certificate found (6)
DoH server connection error: SSL: ssl: no trusted CA certificate found (6) [ignoring repeated messages]
Im not using DoH in DNS settings (Use DoH is empty) and never used it, anybody knows whats this about?
ivicask
Please send the supout.rif file from your device to support@mikrotik.com