Confirming that!
@mszru did you send a supout file to the support team ? Don’t expect to get your problem fixed by posting it on the forum. About netinstall sometimes helps, sometimes doesn’t.
@Ovic, I have similar issues with hAP AX2’es, with 7.13. Created support ticket, attached bunch of autosupout and manual supout files. 0 response so far.
FWIW my AX2 (currently on 7.13) has never reboot since Dec 28th when I applied that version.
Simply using it as AP though via RB5009 capsman controller.
Anyone using Virtual Wifi interfaces on a master interface in station mode should in my opinion stay on away from 13.1.
It just doesn’t work (proven on hap ac’s). The country code could be the issue, but I would be surprised that’s the only reason (I have not seen any error log anywhere in my config
/winbox logs while it was not working). The station i/f is connected to the AP, it gets inbound traffic
but no outbound traffic. You can’t do anything with the i/f (no DHCP, no outgoing ping on L2 etc.)
In meantime better stay on 7.13 or try beta 14
Same setup, AX’ses are crashing, pretty much, daily.
Upgraded to 7.13.1 and had first crash with it, just 15 mins ago.
Yes, and as far as I can tell, the problem hasn’t been identified. Support team advised to try downgrading to the previous stable build or upgrading to the next beta and see if that helps.
I just wanted to warn others that ROS >= 7.12 may be unstable on hAP ac2. I can live with that since it’s a home router that I use to test new features and configurations.
I confirm 7.12 is unstable not only on hAP AC2, but on other ARM based devices too such as cAP AC and Chateau 5G.
Unfortunately quality of testing latest ROS releases leaves much to be desired…
Hello
I have this device
routerboard: yes
board-name: cAP ac
model: RBcAPGi-5acD2nD
revision: r2
firmware-type: ipq4000L
factory-firmware: 6.44
current-firmware: 7.13.1
upgrade-firmware: 7.13.1
I have scripts that use another script with telegram function and working properly.
The Telegram function script inside has the command
/tool fetch url=“https://api.telegram.org/MYBOT/sendMessage?chat_id=MY_CHAT&text=TEST”
All fine.
The same command I used to use the last years on Netwatch in UP or Down and it worked until update 7.13.
When I tried the same command from netwatch to terminal is working but not from netwatch.
Another interest thing with netwatch that into netwatch UP when I have this below is working the email sending but stack to “log info TEST Telegram netwatch”
:log error “TEST Email netwatch”
/tool e-mail send to=“MY EMAIL” subject=“MyDevice Up $[/system clock get time]”
:log info "TEST Telegram netwatch "
/tool fetch url=“https://api.telegram.org/MYBOT/sendMessage?chat_id=MY_CHAT&text=MyDevice Up”
If I reverse the script then it gets stuck in Telegram and doesn’t proceed to email either.
:log info "TEST Telegram netwatch "
/tool fetch url=“https://api.telegram.org/MYBOT/sendMessage?chat_id=MY_CHAT&text=MyDevice Up”
:log error “TEST Email netwatch”
/tool e-mail send to=“MY EMAIL” subject=“MyDevice Up $[/system clock get time]”
I don’t have any wrong error on log just stack to :log info “TEST Telegram netwatch”
What can I do for that? What you suggest?
If you you have never ever Netinstalled this device not even for the changing to v7 series (which is the risk averse way to go) than it is definitely time for
/export verbose show-sensitive file=filenameyoulike
and Netinstall latest stable or testing (choose whichever you like) and
/system/routerboard/upgrade
. This will likely not only leave you with a bit more free storage space however might as well cure seemingly inexplicable issues such as the ones you are experiencing (for example same device with similar usage pattern works rock solid for some while often reboots for others).
Than it’s time to Netinstall and
/system/routerboard/upgrade
if you haven’t already and you may experience that MikroTik’s QA might be a hair better than you’ve experienced lately (although there are some hoops to jump for APs).
I have issues with the backup script.
I made an export then upload via FTP.
7.12.1 works, from 7.13 no.
The script is described here:
https://forum.mikrotik.com/viewtopic.php?p=1048251
05:00:01 system,info,account user spadadmin logged out from 100.127.255.253 via winbox
05:00:02 script,info Config export finished (1/1).
05:00:02 script,info Uploading config export (1/1).
05:00:02 fetch,info,debug Upload from [internal] to ftp://mikrotik:***@20.240.141.60//SPADHAUSEN-MT Sw Trasporto T6 ATTIVO–1301-0-050000.rsc (20.240.141.60) FAILED: cannot
open file: No such file or directory
05:00:02 fetch,info,debug Upload from [internal] to ftp://mikrotik:***@20.240.141.60//SPADHAUSEN-MT Sw Trasporto T6 ATTIVO–1301-0-050000.rsc (20.240.141.60) FINISHED
05:01:03 script,info Configuration backup finished.
File is created correctly on the disk, but it is no longer uploaded.
Open separate topic, and post the script
Upgraded D53G-5HacD2HnD from v7.13 to v7.13.1
Noticing now that the firewall rules under IP/Firewall, under many tab pages, Raw, NAT, Filter Rules, the first rule on top of each, “special dummy rule to show fasttrack counters” is 0 Bytes
Anyone else noticing it?
As usual MikroTik does things without doing in-depth tests of what changing object names entails…
Ah no, I’m wrong: we are the testers… for free…
You didn’t test the script on the command line, so you didn’t see the “error” line
Warning: file was corrected to Sw_Trasporto_T6_ATTIVO–1301-0-050000.rsc
Temporary (I hope) fix: Remove the spaces on router system identity.
@rextended thank you, the issue is that we have spaces in ALL our system identities.
I have opened SUP-140393
Non siete da soli…
chi sei, da che operatore?
A small one 
This topic is strictly moderated (or at least it should be…) let’s stop this off-topic here
It would always be best to adhere to common hostname format standards as system identity translates to hostname of the device.