v7.13.5 [stable] is released!

[mozerd]

If after this you do not understand it open a support ticket with Mikrotik.

@diamuxin, you are correct … I did not fully comprehend the meaning of your comment “You have to delete (uninstall) the existing packages except the “routeros” package, then do the downgrade.”

Please accept my apology … and Thank You …

[diamuxin]

If after this you do not understand it open a support ticket with Mikrotik.

@diamuxin, you are correct … I did not fully comprehend the meaning of your comment “You have to delete (uninstall) the existing packages except the “routeros” package, then do the downgrade.”

Please accept my apology … and Thank You …

You are welcome.
No problem.

[NickOlsen]

I have an issue with 7.13 that 7.12.1 didn’t have (nor before) - I have a bunch of 1gb SFP’s in a CRS328-4C-20S-4S+ switch. None of them will link up auto negotiation at full duplex (they are all fiber). I can hard code both sides of a link and it works full duplex, but with auto negotiation duplex is never picked up and you end up with hundreds of “sfpxx excessive or late collision, link duplex match?” errors and most paths not even passing traffic. Downgrade to 7.12 and it auto negotiates correctly. My 10GB SFP+'s are auto negotiating, only 1GB SFP modules are failing to.

Exact same issue here on CRS328-4C-20S-4S+'s. Downgrading to 7.12.1 fixes it. Only an issue with 1G SFP’s.

[dioeyandika]

after few hours, with the help of chatgpt i modify the backup scripts to

# FTP settings
:local ftpAddress               "192.168.0.100"
:local ftpPort                  "990"
:local ftpUser                  "****"
:local ftpPassword              "***"
:local ftpDestination           "/NAS/Mikrotik"

# System backup settings
:local systemBackupDir "/sd1-part1/"

# Router identity
:local routerOSVersion ("RouterOS_v" . [/system package get number=0 value-name=version])
:local routerBoardModel [/system routerboard get model]

# Clean special characters in model name for filenames
:local cleanedRouterModel [:tostr $routerBoardModel]

# Create backup filenames with timestamp, model, and version
:local currentTime [/system clock get time]
:set currentTime ([:pick $currentTime 0 2] . [:pick $currentTime 3 5])

:local currentDate [/system clock get date]
:set currentDate ([:pick $currentDate 7 11] . [:pick $currentDate 4 6] . [:pick $currentDate 1 3])

:local backupFilenameBackup ($cleanedRouterModel . "_" . $routerOSVersion . "_" . $currentDate . "_" . $currentTime . ".backup")
:local backupFilenameConfig ($cleanedRouterModel . "_" . $routerOSVersion . "_" . $currentDate . "_" . $currentTime . ".rsc")

# Perform system backup for .backup file
/system backup save name=($systemBackupDir . $backupFilenameBackup)

# Export show-sensitive for .rsc file
/export show-sensitive file=($systemBackupDir . $backupFilenameConfig)

# Upload .backup file to FTP
/tool fetch mode=ftp address=$ftpAddress port=$ftpPort user=$ftpUser password=$ftpPassword \
    src-path=($systemBackupDir . $backupFilenameBackup) dst-path=($ftpDestination . "/" . $backupFilenameBackup) upload=yes

# Upload .rsc file to FTP
/tool fetch mode=ftp address=$ftpAddress port=$ftpPort user=$ftpUser password=$ftpPassword \
    src-path=($systemBackupDir . $backupFilenameConfig) dst-path=($ftpDestination . "/" . $backupFilenameConfig) upload=yes

now it works perfectly, i still doesnt now which part before doesnt work with v.7.13

[pekr]

Upgraded two LHG XL52 ac (PtP setup), settings were intact, no issue with signal (-42), devices register themselves on one another (both 2GHz and 5GHz), but can’t see other LHG via Winbox.
Any clues ?

EDIT: on 7.12.1 was working perfectly.

Are you using the new wifi package? If yes, it does not support station bridge mode yet with old devices/old driver! I use bridge and eoip over wifi link for extending the L2 segment

Is this limitation described anywhere? This is crucial information to me, as I have already upgraded hap ac2s to the 7.13, using wireless so far, and will travel soon there to switch to the wave2 package. Well, I could use vxlan tunel probably, or stay with the old wireless package, but was really looking into hassle free station bridge solution

[frank333]

I tried 7.13 on RBM11g but the scripts don’t work anymore!
I tried uninstalling the wireless package and downgrading to 7.12.1 but it doesn’t work .
How did you guys do the downgrade?

[Jotne]

I tried 7.13 on RBM11g but the scripts don’t work anymore!

What script?

PS Do add image to the post use Attachements when in full post mode. Link to other site may go away.

[mkx]

Are you using the new wifi package? If yes, it does not support station bridge mode yet with old devices/old driver! I use bridge and eoip over wifi link for extending the L2 segment

Is this limitation described anywhere?

Yes, in wifi documentation, read through replacing ‘wireless’ package section. It’s last item in “lost features”.

[peich1]

I have a similar problem, on devices using MPLS/VPLS I see kernel panics every few hours and a lot of problems with packets not being forwarded or routed properly. I have seen it on an RB4011 (arm), RB5009 (arm64), and CCR1009 (tile). No supout generated, just a log message about the router being improperly rebooted and a suggestion that a kernel panic might be the reason.

I’m getting 1 or 2 reboots a day in my RB5009 since upgrading 7.13, no sup file creation. Though I don’t use VPLS…

[frank333]

I have updated my RB5009 and my CRS326-24G and my scripts for Telegram are not working as expected. I am not getting any message more than the download message with the Chat ID.

I will be rolling back to version 7.12 if this not going to be fixed quickly by Mikrotik

It would be interesting to understand what needs to be changed in the scripts to make them work again.

[frank333]

I tried 7.13 on RBM11g but the scripts don’t work anymore!

What script?

PS Do add image to the post use Attachements when in full post mode. Link to other site may go away.

scripts that include the fetch command for telegram

[holvoetn]

I’m getting 1 or 2 reboots a day in my RB5009 since upgrading 7.13, no sup file creation. Though I don’t use VPLS…

No such thing here.
Stable since update last Friday.

[rb9999]

bonding issue on two CCR2004-16G-2S+… downgrade to 7.12.1 seems to help

[pe1chl]

Is this limitation described anywhere?

Yes, in wifi documentation, read through replacing ‘wireless’ package section. It’s last item in “lost features”.

Also, it is always good to realize that any conversion from “7.13 with routeros+wireless package” to “routeros+wifi_qcom_ac” will always make you lose all configuration of the wifi. There is no attempt to convert even simple configurations like “station connecting to an SSID with a WPA2-PSK password” or “AP with SSID and WPA2-PSK password” into a new configuration after this change.
Of course it would be possible to make a script for that, but it isn’t there. So be careful with remote systems or with routers that you manage via WiFi!

[Simonej]

scripts that include the fetch command for telegram

user policy “ftp” is enabled?

[frank333]

scripts that include the fetch command for telegram

user policy “ftp” is enabled?

is enabled.
I get this from the logs:
fetch,info,debug Download from https://api.telegram.org/bot42558852236:AAR_pTRe0CjksgfdydhdncbvfdtY4/sendMessage to RAM FAILED: Fetch failed with status 400

[sinisa]

In the “old” wireless, and even in “wifiwave2” there used to be “country info”, but I am unable to find it in 7.13 with “qcom-ac” drivers.

Am I missing something?

[holvoetn]

This ?

[a<some_user>@<some_router>] > interface/wifi/radio reg-info country=Belgium
number: 0
ranges: 2402-2482/20
5170-5250/23/indoor
5250-5330/23/indoor/dfs
5490-5710/30/dfs

[sinisa]

This ?

[a<some_user>@<some_router>] > interface/wifi/radio reg-info country=Belgium
number: 0
ranges: 2402-2482/20
5170-5250/23/indoor
5250-5330/23/indoor/dfs
5490-5710/30/dfs

Yes, just found it
Reading/searching the doc’s makes miracles

Thanks!

[mazay]

Exciting news! :trollface:
The documentation says my Audience is compatible as well as some other my devices. Starting with audience, removing the wireless package, rebooting, uploading wifi-qcom packages, rebooting and I’m in a boot loop.

Netinstall with 7.13 and install of wifi-qcom packages on a virgin clean device result in another boot loop, the only way out is another netinstall.

Stick to the old wireless package for now…