v7.13rc [testing] is released!

Announcements
61

iPad-App don’t show the “old” Wireless entries. The new “WiFi” is displayed but it seems not the “old” one.

62

wg import will be fixed in upcoming releases.

63

with 7.13rc2 on CCR2216, with ipv4 HWl3 offload and bgp routing, lead to unexpected reboot without any log or autosupout, we had to downgrade to 7.12.1

64

When the problem with the absence of the following path attributes in bgp update will be fixed:

  1. EXTENDED_COMMUNITIES
  2. MP_REACH_NLRI
    The problem affects only routers based on the ARM64 architecture.
65

Same behaviour for me with a CCR2004-1G12S+2XS
Yesterday during a video call the router spontaneus rebootet triggered by watchdog, what he never did in the past. It was the absolut first time he did it.
SUP-136647 open.

66

You should ask Support.

67

I have opened appeal SUP-136441. There is a feeling that their support system simply cannot withstand such a load. Maybe they need to fix the problems in sections? And do not take on everything at once, which leads to a large number of problems and customer dissatisfaction.

68

Is there any chance that the Cube 60Pro AC might get to use WiFi-qcom just for the wifi side of it, and leaving whatever is needed to keep the 60G working?
Since it is ARM.
and might be nice to have wave2 performance on the backup ac-wifi.

69

Interesting that we have a similar setup and different experience. I suspect it was the failure of the Adguard container that possibly caused all the slowness but nothing in logs, I need to revisit that component next time.

70

When will they fix MLAG?

71

Sorry, but this is a pointless post.
No one can help you here without information about what is not working with MLAG, nor what your config looks like :-/

72

http://forum.mikrotik.com/t/mlag-issue-mlag-functionality-flaps-lacp-system-id-of-secondary-when-primary-reboots/157426/13

73

Regarding MLAG: MT is an excellent Router vendor, but they make lousy Switches. Use another vendor (like FS, D-Link…) for device-overlapping aggregation-groups. MT screwed that in such an overcomplicated way up, it seems they (itself) are unabled to fix it. Same with the “Loopback Detection”, not fixable, just screwed up… my ticket is open for months.

74

I am thinking of FS currently yes as an alternative. Unfortunately I did not do enough research into this and I was saying oh we can get MLAG for cheap to my boss.

75

What’s new in 7.13rc3 (2023-Dec-06 17:16):
*) console - fixed memory leak (introduced in v7.13beta1);
*) defconf - fixed wireless band and channel-width selection (introduced in v7.12);
*) iot - fixed incorrect LoRa ACK packet handling during downlink messaging (introduced in v7.12);
*) qos-hw - added initial congestion avoidance support for 98DX224S, 98DX226S, and 98DX3236 switch chips (CLI only);
*) sfp - fixed link establishment with S+DA0001 DAC cables;
*) sfp - improved link establishment for SFP copper modules;
*) wireless - keep configuration after manual package removal;

76

On hAP ac² with wifi-qcom-ac I have:

2023-12-07 13:02:57 system,error,critical error while running customized default configuration script: no such item
2023-12-07 13:02:57 system,error,critical
2023-12-07 13:03:33 system,error,critical error while running customized default configuration script: invalid internal item number
2023-12-07 13:03:33 system,error,critical
77

hAP ax2

2023-12-07 12:20:13 system,error,critical error while running customized default
 configuration script: no such item
2023-12-07 12:20:13 system,error,critical

No such error on cAP ax

Still no power correction for the UK

interface/wifi/monitor 0,1,2,3                            
                 state: running      running running      running
               channel: 5500/ax/Ceee 2412/ax 5745/ax/Ceee 2462/ax
      registered-peers: 0            0       2            1
      authorized-peers: 0            0       2            1
              tx-power: 22           14      9            15
    available-channels: 5500/ax/Ceee 2412/ax 5745/ax/Ceee 2462/a
78

What previous RouterOS version where you running, @eworm?

79

RouterOS 7.13rc2, without errors.

80

Is the same error on RouterOS source code, that I report various times, with the exact position and fix, completely ignored.
Someone also remember it…
http://forum.mikrotik.com/t/v7-13rc-testing-is-released/171577/1
It seems that only users on the forum can read what I write, the MikroTik staff cannot.

Already reported for 7.5, 7.6, 7.9rc, 7.2.2, 7.11.2
http://forum.mikrotik.com/t/v7-11-2-stable-is-released/168778/1