v7.13.5 [stable] is released!

Crs326 - bonding stop working after update to 7.13
Disabling/enabling bonding interface, recreation doesn’t help.
Traffic is just stop going after update. (Synology nas is in the other end)

I also have problems with a Mikrotik S+RJ10 Module and CRS326-24G-2S+RM:

it says link ok, but i cannot connect to the server that is connected via ethernet 10G. Had to netinstall 7.12.1 to get the connection working again…

Thanks, however, HAP AC3 (RBD53iG-5HacD2HnD) central led now flashing red. I believe this central LED is related to lte / wps?
Up until version 7.12.1 it was solid blue.
Please advise.

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

The same on hAP ac^3. Sometime after reboot I’ve got lte interface and internet access but can’t access web interface of the modem in hilink mode.

Do you have usb modem attached? I’ve got red blinks right after modem connection.

There is station bridge mode in new drivers. Tried it just yesterday on LHG52.

Yup, already in beta versions. Tested it as well.

Updated all my devices without issues.

Regards.

I know it’s a guessing game, but I cannot find what seems to be the problem. I have 2 pairs of PtP link, similar setup (apart for SSID names etc). Both pairs were on 6.49.11. I’ve upgraded both pairs to 7.12.1 and both were working. Now I upgraded one pair to 7.13 and have above issues. I checked all settings but cannot find the cause.

Start separate thread with export of config.

+1, report the same error:

  • fetch with ipv4 url are automatically “translated” into ipv6 by being prefixed with “::ffff:”
  • This results in either host unreachable or data content = null

Had to roll back to 7.12.1

When i upgraded LHG52 to 7.13 first in didn’t even see wireless intefaces even if wireless package was installed (checked). Probably because there was also Zerotier package on it and something went wrong with the instalation (to little space for all those packages).
I just deleted it and installed qcom ac package and everything seems fine.

Yes!
Just tested this and your’re right. After connecting the USB modem the LED starts flashing red.
Unplugging it doesn’t change it’s behavior. You need to reboot the whole router with the modem unplugged. Plugging it back makes the LED starts blinking red again.
EDIT: disabling the dynamic lte1 interface also restores the LED back to normal (static blue).

Why is that needed? In my WifiWave2/WiFi CAPsMAN setup I don’t use this, and devices connect and roam successfully.

Now I’m just hoping that VLAN tagging will find its way back into wifi-qcom-ac driver to restore the flexibility it provides.

Me too. It would make CAP more controlled - better provisioned without a need to manually set bridge ports and VLANs for wifi interfaces on each CAP.

My modem is useless with 7.13 (
lte interface just disappeared )

Indeed that is the problem, you have explained it better than me :wink:
Let's see what solution they give us.

TESTs:

# Imput CLI:
{
:local urlSesTokInfo "http://192.168.8.1/api/webserver/SesTokInfo"
:put ([/tool fetch $urlSesTokInfo output=user as-value]->"data")
}

# Log message v7.13:
Download from http://::ffff:192.168.8.1/api/webserver/SesTokInfo (::ffff:192.168.8.1) to RAM FINISHED

# Log message v7.12.1:
No message (ok)

Why do more messages appear in the log like fetch, stp, debug, etc?

At least with FT disabled, the default connect-priority setting delays roaming to a new AP until a client has disconnected from its previous AP. With my Android phone this caused several seconds of delay when roaming.

Setting connect-priority=0/1 ensures connections to a new AP are immediately accepted and the old AP connection is dropped automatically. When using PSK authentication, this allows seamless roaming even without FT.

Hi all!

I have the same problem with script on CHR after upgrade :frowning:

Download from https://antifilter.download/list/ip.lst to <nothing> FINISHED
Download from https://antifilter.download/list/ip.lst to RAM FAILED: Fetch failed with status 206

What can i do with this?