Which of the 2 devices (uplink router or the repeater) is hard to find out.
- GL.inet repeater claims that of beacon with the wrong (zero) channel is received, and says it has lost the connection.
The uplink router (Mikrotik) says ..
disconnected, ok, signal strength -57/
attempts to associate/
connected signal strength -57/
reassociating/
disconnected, ok, signal strength -57/
In Mikrotik language, "reassociating" means that the device associates while still associated.
This happens on all my Mikrotiks hAPac2, hAPax2, hAPac3, wAPac, hAP Lite .... no other client device shows any problems on those AP, only the GL.inet SFT1200.
Same problem with my friend. He is testing at our 30 AP large monitored Mikrotik campus installation. Performance on all connections is excellent, except the SFT1200.
So who is dropping the connection here ? I think it is the GL.inet, not the uplink router.
2.4 GHz is actually unusable, 5 GHz drops too frequently under load.
EDIT: It was exceptionally bad this evening. Friend at remote location, with SFT1200 connections that last only 1 or 2 sconds, even on 5GHz band, what used to be 5 minute sessions. Ideal to do some tweaking on the Mikrotiks, that I manage remotely. Guess what ... session was stable for 8hours ! No disconnects. OK this was on 5 GHz band, 2.4GHz is stable if the 802.11g only is forced there. No such thing on 5 GHz (n or n/ac makes no difference).
So tweaked a lot (RTS/CTS, AMSDU size, only 6Mbps basic rate, multicast helper), and the "multicast helper" set to "Full" made it 100% stable. Not only no-disconnects, but 100%CCQ and the dynamic interface rate goes up to the max possible : 400Mbps for 40MHz width/2 stream/short guard. All other tweaks turned off, it remains stable 100% with only the "multicast helper" set to full, on Mikrotik
In Mikrotik the multicast helper set to "default", as it is set by default actually means the helper is OFF or disabled !
Multicast helper on Full, converts multicasts in separate unicasts.
Don't know if this is done for beacons also.
Mikrotik - SFT1200 : there clearly is a multicast/broadcast problem. Wrong channel info as read from beacon, forces disconnects. But yes beacon/multicast does not do ACK-NACK or retransmits.
Have to test this helper workaround on the 2.4 GHz band, and compare it to the previous 802.11g workaround.
EDIT 2
Previous ... now this is on 4.3.21 .... and this supports DFS channels now, scanning, selecting, receiving and repeat/transmitting on channel 132 , with country BE (Europe/ETSI) . More changes than listed in the release notes. the previous workaround on 2.4GHz as "802.11g" does not help ... anymore ???Everything to be tested again ???
And we have new error types now:
Sat Nov 9 14:21:10 2024 kern.warn kernel: [ 9333.012255] lmac[1] Error, msdu index reach maximum limit, 31
Sat Nov 9 14:21:10 2024 kern.warn kernel: [ 9333.018094] lmac[1] Error, buffer is not uploaded to host buffer completely