SFT1200 2.4 GHz Repeater Disconnects

Hi,

Just received the Opal router GL-SFT1200. This is my second gl inet router exhibiting the exact same problem. My first was the older Slate 750ext

Here is the issue: When I connect the Opal to a 2.4 ghz access point to provide internet backhaul and connect my client devices to either the 2 or 5 GHz Opal ap, any traffic (browsing etc) will cause the Opal to drop the repeater side connection. The light goes from white to slow flashing "blue" (which really looks like a dim white!) And if I'm logged into the admin panel I see an error that the Opal has lost internet. Waiting a few mins, the connection reestablished, only for more traffic to cause the issue to repeat.

If I reverse the "stream" and connect the Opal to a 5ghz internet wifi backhaul and my client to the 2.4ghz Opal ap, everything works fine, so it doesn't appear to be a 2.4 GHz radio problem, but strictly a repeater problem when using 2.4 as the internet link. (For these tests, I control all wifi units and all wifi devices are within line of site with each other, so this is not a reception problem. I've moved units around and tested multiple times)

I've tried this test using several different wifi aps as the internet source and compared this to connecting my clients directly and this is a very repeatable issue. The clients connecting directly to the internet sourced wifi ap have no problems browsing at all! Only when routing via the Opal using 2.4 GHz as backhaul does this problem appear. It's very frustrating as I sometimes travel to places that only provide 2.4 GHz internet access.

This has been tested both on the 3.x and beta 4.x firmware. Same result across the board.

I see many posts about connection drops with repeater but none specifically call out this configuration (2.4 GHz as backhaul) so putting this out there for feedback.

I'm considering returning this unit if I can't solve this as it's clearly been an issue that's plagued these series of routers for a long time.

1 Like

That sounds like an issue with the uplinking AP for me. Maybe they donā€™t support another router inside the network, or they will not accept NAT, for example?

Since you can directly connect to the 2.4 GHz, it seems that they are running on different SSIDs - are they different networks as well?

The connection establishes and even some data moves through, the problem occurs when there is a ā€œloadā€ ā€“ like a lot of content on a page, etc. I can see some text and the odd image, but move more than a trivial amount of data and it dies.

As mentioned, this is my network, Iā€™ve connected other devices that repeat (like my Pixel phone in hotspot mode to test) and there is no issue with this config, so no, itā€™s not the host network.

Can you post the log?

Here is a snippet from last up to down and back up againā€¦ the trigger is always loading a web page.

Sun Oct 22 15:44:37 2023 user.notice firewall: Reloading firewall due to ifup of wwan (wlan-sta0)
Sun Oct 22 15:44:38 2023 user.notice relay: Reloading relay due to connected of wwan (wlan-sta0)
Sun Oct 22 15:44:38 2023 daemon.err dnscrypt-proxy[1919]: dnscrypt-proxy Unable to retrieve server certificates
Sun Oct 22 15:44:39 2023 user.notice relay: Reloading relay due to ifup of wwan (wlan-sta0)
Sun Oct 22 15:45:35 2023 daemon.info dnscrypt-proxy[1919]: dnscrypt-proxy Refetching server certificates
Sun Oct 22 15:45:36 2023 daemon.notice wpa_supplicant[8756]: wlan-sta0: WPA: Group rekeying completed with 66:d1:54:5e:0e:e0 [GTK=CCMP]
Sun Oct 22 15:45:36 2023 daemon.info lua: (...pkg-mips_siflower/gl-sdk4-repeater/usr/sbin/repeater:548) <3>WPA: Group rekeying completed with 66:d1:54:5e:0e:e0 [GTK=CCMP]
Sun Oct 22 15:45:36 2023 kern.info kernel: [  935.943687] lb-fmac 11000000.wifi-lb wlan-sta0: Add key for vif(0), key index : 2
Sun Oct 22 15:45:50 2023 daemon.err dnscrypt-proxy[1919]: dnscrypt-proxy Unable to retrieve server certificates
Sun Oct 22 15:46:51 2023 daemon.info dnscrypt-proxy[1919]: dnscrypt-proxy Refetching server certificates
Sun Oct 22 15:47:06 2023 daemon.err dnscrypt-proxy[1919]: dnscrypt-proxy Unable to retrieve server certificates
Sun Oct 22 15:47:09 2023 daemon.notice wpa_supplicant[8756]: wlan-sta0: CTRL-EVENT-DISCONNECTED bssid=66:d1:54:5e:0e:e0 reason=2
Sun Oct 22 15:47:09 2023 daemon.info lua: (...pkg-mips_siflower/gl-sdk4-repeater/usr/sbin/repeater:548) <3>CTRL-EVENT-DISCONNECTED bssid=66:d1:54:5e:0e:e0 reason=2
Sun Oct 22 15:47:09 2023 kern.warn kernel: [ 1029.446121] lmac[0] {CTXT-1} unlink from {VIF-0}: status=4 nb_vif=1
Sun Oct 22 15:47:09 2023 kern.warn kernel: [ 1029.446151] lmac[0] {CTXT-1} Delete channel context
Sun Oct 22 15:47:09 2023 kern.info kernel: [ 1029.452719] lb-fmac 11000000.wifi-lb wlan-sta0: Del key for vif(0), key index : 0
Sun Oct 22 15:47:09 2023 kern.info kernel: [ 1029.465254] lb-fmac 11000000.wifi-lb wlan-sta0: Del key for vif(0), key index : 1
Sun Oct 22 15:47:09 2023 kern.info kernel: [ 1029.473458] lb-fmac 11000000.wifi-lb wlan-sta0: Del key for vif(0), key index : 2
Sun Oct 22 15:47:09 2023 kern.info kernel: [ 1029.481960] lb-fmac 11000000.wifi-lb wlan-sta0: Del key for vif(0), key index : 3
Sun Oct 22 15:47:09 2023 kern.info kernel: [ 1029.489578] lb-fmac 11000000.wifi-lb wlan-sta0: Del key for vif(0), key index : 4
Sun Oct 22 15:47:09 2023 kern.info kernel: [ 1029.497192] lb-fmac 11000000.wifi-lb wlan-sta0: Del key for vif(0), key index : 5
Sun Oct 22 15:47:09 2023 daemon.notice netifd: Network device 'wlan-sta0' link is down
Sun Oct 22 15:47:09 2023 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Sun Oct 22 15:47:09 2023 kern.warn kernel: [ 1029.555042] lmac[0] final dsss power is 27 ofdm power is 27
Sun Oct 22 15:47:09 2023 daemon.info lua: (...pkg-mips_siflower/gl-sdk4-repeater/usr/sbin/repeater:548) <3>CTRL-EVENT-SCAN-STARTED
Sun Oct 22 15:47:09 2023 kern.warn kernel: [ 1029.585879] lmac[0] final dsss power is 27 ofdm power is 27
Sun Oct 22 15:47:09 2023 daemon.notice netifd: wwan (4078): udhcpc: received SIGTERM
Sun Oct 22 15:47:09 2023 kern.warn kernel: [ 1029.616742] lmac[0] final dsss power is 27 ofdm power is 27
Sun Oct 22 15:47:10 2023 kern.warn kernel: [ 1029.647527] lmac[0] final dsss power is 27 ofdm power is 27
Sun Oct 22 15:47:10 2023 kern.warn kernel: [ 1029.678343] lmac[0] final dsss power is 27 ofdm power is 27
Sun Oct 22 15:47:10 2023 kern.warn kernel: [ 1029.709181] lmac[0] final dsss power is 27 ofdm power is 27
Sun Oct 22 15:47:10 2023 kern.warn kernel: [ 1029.740042] lmac[0] final dsss power is 27 ofdm power is 27
Sun Oct 22 15:47:10 2023 kern.warn kernel: [ 1029.770849] lmac[0] final dsss power is 27 ofdm power is 27
Sun Oct 22 15:47:10 2023 kern.warn kernel: [ 1029.801688] lmac[0] final dsss power is 27 ofdm power is 27
Sun Oct 22 15:47:10 2023 daemon.err lua: (...pkg-mips_siflower/gl-sdk4-repeater/usr/sbin/repeater:1270) disconnected, wait reconnect...
Sun Oct 22 15:47:10 2023 daemon.notice netifd: Interface 'wwan' is disabled
Sun Oct 22 15:47:10 2023 kern.warn kernel: [ 1029.832556] lmac[0] final dsss power is 27 ofdm power is 27
Sun Oct 22 15:47:10 2023 kern.warn kernel: [ 1029.863404] lmac[0] final dsss power is 27 ofdm power is 27
Sun Oct 22 15:47:10 2023 daemon.info lua: (...pkg-mips_siflower/gl-sdk4-repeater/usr/sbin/repeater:548) <3>CTRL-EVENT-SCAN-RESULTS
Sun Oct 22 15:47:10 2023 daemon.info lua: (...pkg-mips_siflower/gl-sdk4-repeater/usr/sbin/repeater:548) <3>WPS-AP-AVAILABLE
Sun Oct 22 15:47:10 2023 daemon.notice wpa_supplicant[8756]: wlan-sta0: Trying to associate with 66:d1:54:5e:0e:e0 (SSID='riots' freq=2462 MHz)
Sun Oct 22 15:47:10 2023 daemon.info lua: (...pkg-mips_siflower/gl-sdk4-repeater/usr/sbin/repeater:548) <3>Trying to associate with 66:d1:54:5e:0e:e0 (SSID='riots' freq=2462 MHz)
Sun Oct 22 15:47:10 2023 kern.warn kernel: [ 1029.904839] lmac[0] final dsss power is 27 ofdm power is 27
Sun Oct 22 15:47:10 2023 kern.warn kernel: [ 1029.934909] lmac[0] {CTXT-2} Create channel context: freq=2462MHz bw=20MHz pwr=20dBm
Sun Oct 22 15:47:10 2023 kern.warn kernel: [ 1029.942796] lmac[0] {CTXT-2} link to {VIF-0}: status=0 nb_vif=0
Sun Oct 22 15:47:10 2023 kern.warn kernel: [ 1029.942825] lmac[0] final dsss power is 27 ofdm power is 27
Sun Oct 22 15:47:10 2023 kern.warn kernel: [ 1029.954463] lmac[0] rc_init: station_id=5 format_mod=2 pre_type=0 short_gi=1 max_bw=0
Sun Oct 22 15:47:10 2023 kern.warn kernel: [ 1029.962386] lmac[0] rc_init: nss_max=1 mcs_max=7 r_idx_min=12 r_idx_max=12 no_samples=10
Sun Oct 22 15:47:10 2023 daemon.notice netifd: Network device 'wlan-sta0' link is up
Sun Oct 22 15:47:10 2023 daemon.notice netifd: Interface 'wwan' has link connectivity
Sun Oct 22 15:47:10 2023 daemon.notice wpa_supplicant[8756]: wlan-sta0: Associated with 66:d1:54:5e:0e:e0
Sun Oct 22 15:47:10 2023 daemon.notice wpa_supplicant[8756]: wlan-sta0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sun Oct 22 15:47:10 2023 daemon.info lua: (...pkg-mips_siflower/gl-sdk4-repeater/usr/sbin/repeater:548) <3>Associated with 66:d1:54:5e:0e:e0
Sun Oct 22 15:47:10 2023 daemon.info lua: (...pkg-mips_siflower/gl-sdk4-repeater/usr/sbin/repeater:548) <3>CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sun Oct 22 15:47:10 2023 kern.info kernel: [ 1029.982205] lb-fmac 11000000.wifi-lb wlan-sta0: Add key for sta 5 (66:d1:54:5e:0e:e0)
Sun Oct 22 15:47:10 2023 kern.info kernel: [ 1029.991357] lb-fmac 11000000.wifi-lb wlan-sta0: Add key for vif(0), key index : 2
Sun Oct 22 15:47:10 2023 daemon.notice wpa_supplicant[8756]: wlan-sta0: WPA: Key negotiation completed with 66:d1:54:5e:0e:e0 [PTK=CCMP GTK=CCMP]
Sun Oct 22 15:47:10 2023 daemon.info lua: (...pkg-mips_siflower/gl-sdk4-repeater/usr/sbin/repeater:548) <3>WPA: Key negotiation completed with 66:d1:54:5e:0e:e0 [PTK=CCMP GTK=CCMP]
Sun Oct 22 15:47:10 2023 daemon.notice wpa_supplicant[8756]: wlan-sta0: CTRL-EVENT-CONNECTED - Connection to 66:d1:54:5e:0e:e0 completed [id=0 id_str=]
Sun Oct 22 15:47:10 2023 daemon.info lua: (...pkg-mips_siflower/gl-sdk4-repeater/usr/sbin/repeater:548) <3>CTRL-EVENT-CONNECTED - Connection to 66:d1:54:5e:0e:e0 completed [id=0 id_str=]
Sun Oct 22 15:47:10 2023 user.notice mwan3[10838]: Execute ifdown event on interface wwan (unknown)
Sun Oct 22 15:47:10 2023 user.info mwan3track[4989]: Detect ifdown event on interface wwan (wlan-sta0)
Sun Oct 22 15:47:10 2023 user.notice mwan3track[4989]: Interface wwan (wlan-sta0) is offline
Sun Oct 22 15:47:12 2023 user.notice firewall: Reloading firewall due to ifdown of wwan ()
Sun Oct 22 15:47:12 2023 user.notice relay: Reloading relay due to disconnected of wwan (wlan-sta0)
Sun Oct 22 15:47:13 2023 daemon.info lua: (...pkg-mips_siflower/gl-sdk4-repeater/usr/sbin/repeater:1239) connected to 'riots(66:d1:54:5e:0e:e0)' channel: 11, spent 3s
Sun Oct 22 15:47:13 2023 daemon.notice netifd: Interface 'wwan' is enabled
Sun Oct 22 15:47:13 2023 daemon.notice netifd: Interface 'wwan' is setting up now
Sun Oct 22 15:47:13 2023 daemon.notice netifd: wwan (11401): udhcpc: started, v1.29.3
Sun Oct 22 15:47:13 2023 daemon.notice netifd: wwan (11401): udhcpc: sending discover
Sun Oct 22 15:47:13 2023 daemon.notice netifd: wwan (11401): udhcpc: sending select for 192.168.10.95
Sun Oct 22 15:47:13 2023 user.notice relay: Reloading relay due to ifdown of wwan ()
Sun Oct 22 15:47:13 2023 daemon.notice netifd: wwan (11401): udhcpc: lease of 192.168.10.95 obtained, lease time 86400
Sun Oct 22 15:47:14 2023 daemon.warn dnsmasq[1826]: no servers found in /tmp/resolv.conf.auto, will retry
Sun Oct 22 15:47:14 2023 daemon.notice netifd: Interface 'wwan' is now up
Sun Oct 22 15:47:14 2023 daemon.info dnsmasq[1826]: reading /tmp/resolv.conf.auto
Sun Oct 22 15:47:14 2023 daemon.info dnsmasq[1826]: using local addresses only for domain test
Sun Oct 22 15:47:14 2023 daemon.info dnsmasq[1826]: using local addresses only for domain onion
Sun Oct 22 15:47:14 2023 daemon.info dnsmasq[1826]: using local addresses only for domain localhost
Sun Oct 22 15:47:14 2023 daemon.info dnsmasq[1826]: using local addresses only for domain local
Sun Oct 22 15:47:14 2023 daemon.info dnsmasq[1826]: using local addresses only for domain invalid
Sun Oct 22 15:47:14 2023 daemon.notice netifd: wwan (11401): /lib/netifd/dhcp.script: line 62: netclash: not found
Sun Oct 22 15:47:14 2023 daemon.info dnsmasq[1826]: using local addresses only for domain bind
Sun Oct 22 15:47:14 2023 daemon.info dnsmasq[1826]: using local addresses only for domain lan
Sun Oct 22 15:47:14 2023 daemon.info dnsmasq[1826]: using nameserver 1.1.1.3#53
Sun Oct 22 15:47:14 2023 daemon.info dnsmasq[1826]: using nameserver 1.0.0.3#53
Sun Oct 22 15:47:14 2023 user.info mwan3track[4989]: Lost 5 ping(s) on interface wwan (wlan-sta0)
Sun Oct 22 15:47:15 2023 user.notice mwan3[11491]: Execute ifup event on interface wwan (wlan-sta0)
Sun Oct 22 15:47:16 2023 user.notice mwan3[11491]: Starting tracker on interface wwan (wlan-sta0)
Sun Oct 22 15:47:16 2023 user.notice mwan3track[4989]: Stopping mwan3track for interface "wwan"
Sun Oct 22 15:47:19 2023 user.info mwan3rtmon[2275]: Detect rtchange event.
Sun Oct 22 15:47:20 2023 user.notice firewall: Reloading firewall due to ifup of wwan (wlan-sta0)
Sun Oct 22 15:47:20 2023 user.notice relay: Reloading relay due to connected of wwan (wlan-sta0)
Sun Oct 22 15:47:21 2023 user.notice relay: Reloading relay due to ifup of wwan (wlan-sta0)

As a side note my Mikrotik router (the backhaul ap in this test) shows a log msg of ā€œdisconnected, extensive data lossā€.

Iā€™m using the GL-SFT1200 as a repeater and I have slowdown problems. Out of 290MB it only delivers 50MB of speed as a repeater and no one identifies the problem.

I want to know these settings:

  1. 2.4G wifi channel
  2. Is your 2.4G and 5G wifi using the same SSID and key on Mikrotik?
  3. Do you have some settings e.g. band steering in your Mikrotik router?

I want to know these settings:

  1. 2.4G wifi channel

The previously attached log output for an AP that advertises multiple SSIDs on Ch. 11. However, I also tested this on another 2Ghz only AP with only one SSID on ch. 3 and had the same results.

  1. Is your 2.4G and 5G wifi using the same SSID and key on Mikrotik?

The MT AP advertises multiple different network SSIDs, but for the one I was testing, I used a dedicated 2G SSID that did not have a corresponding 5G SSID.

  1. Do you have some settings e.g. band steering in your Mikrotik router?

MT routers donā€™t support this as far as I know. I have nothing special set on either of the APs I tested with and no other devices are experiencing problems.

Channel 11 should be fine. But donā€™t use channel 3. Use 1, 6 or 11 only.

@dxf can you have a check of the 2.4G wifi disconnect log?

Just thought Iā€™d add: I just received from Amazon the Beryl GL-MT1300 and configured it exactly the same as the troubled Opal, using all the same clients and backhaul access points ā€“ and so far it works flawlessly. So either I have a bum Opal or there is something fundamentally wrong with that product line and my setup.

Iā€™m going to be returning the Opalā€¦ :frowning:

Hi everyone! Iā€™m facing the same issue here: my repeater mode works fine with my home Wi-Fi 5ghz network, but it loses internet connection after a few minutes on the 2.4ghz one. I donā€™t want to use the 5ghz radio for repeater mode because I want to keep it free. Has anyone found a solution for this? I appreciate your help!

1 Like

Do you mean SFT1200? Seems you have different routers.
Do you have the logs?

Long shot, but do you notice if the BSSID is changing when on 2.4Ghz? Jump over to Luci and remove the BSSID for that wireless connection (think Iā€™ve also seen it with a tick box as ā€˜lock BSSIDā€™ on some version of OpenWRT).

2 Likes

Hello @alzhao! Yest, this problem only happens with the STF1200, just like OP.

I believe @McMuckle nailed it: Iā€™ve set the repeater to lock BSSID, since I have two AP broadcasting the same SSID and OPAL seems to work just fine now, great idea! It seems this is problem related to the OPAL software, since this is not an issue at all with the Beryl.

@alzhao do you think there will be an FW update for OPAL in the near future? It might fix this issue and keep the device up to date comparing to your other routers. I know this is an affordable device, with a low spec hardware but it has great potential, especially with emerging countries like mine. It still runs OpenWrt 18.06 with Kernel Version 4.14.90.

Thank you very much guys!

1 Like

It will have firmware update. But the openwrt version and kernel version cannot be changed. We can only update the applications on top of them.

1 Like

Exact same issue here, and this is already oct 2024, problem still there.
5GHz is OK, 2.4GHz disconnects very frequently.
But the 5GHz cannot work with DFS channels. So this gives quite limited possibilities in Europe.
Tried firmware 4.3.19 till 4.3.11 ... all have the same problem

2 Likes

I configured my dumb aps using openwrt.
As a main router I use fint 2 and linksys routerswith openwrt on them as aps.

It looks like this problem is caused by mwan3tracker.
Even switcing it off in the GUI for all 3 interfaces, still starts that tracker for the WLAN interface
"Starting tracker on interface wwan (wlan-sta0)"
But also for the ethernet interface. And tracking iin the GUI s OFF !!!
"Internet always available when the interface is connected"

Sat Oct 26 12:11:13 2024 user.notice mwan3[5302]: Starting tracker on interface wan (eth0.2)
Sat Oct 26 12:11:16 2024 user.notice relay: Reloading relay due to connected of wan (eth0.2)
Sat Oct 26 12:11:16 2024 user.notice firewall: Reloading firewall due to ifup of wan (eth0.2)
Sat Oct 26 12:11:18 2024 user.notice relay: Reloading relay due to ifup of wan (eth0.2)
Sat Oct 26 12:11:19 2024 user.notice mwan3[6050]: Execute ifup event on interface wwan (wlan-sta0)
Sat Oct 26 12:11:20 2024 user.notice mwan3[6050]: Starting tracker on interface wwan (wlan-sta0)
Sat Oct 26 12:11:23 2024 user.info mwan3rtmon[5828]: Detect rtchange event.
Sat Oct 26 12:11:24 2024 user.notice firewall: Reloading firewall due to ifup of wwan (wlan-sta0)
Sat Oct 26 12:11:24 2024 user.notice relay: Reloading relay due to connected of wwan (wlan-sta0)
Sat Oct 26 12:11:25 2024 user.notice relay: Reloading relay due to ifup of wwan (wlan-sta0)

WLAN3 tracker fails from time to time with the 4 default IP addresses. (Cloudflare, Google and Cisco), even when the connection is idle. It certainly will fail under traffic load.

What is the time-out value set for the PING test ?

Should we enter a local responding device in this test also, just to avoid the disconnects. Setting tracking OFF in the GUI didn't help. Are the 4 tests evaluated as AND or OR ? Should be OR, and should be very stable with a local router in the IP list. OpenWRT has improved stability in more recent versions, than this old one on the SFT1200.

1 Like

Well one more test , as a Mikrotik WLAN driver gives lots of information ...

With the 5 GHz connection nearly 100% of the Frames are usefull (ratio TX/RX Frames versus TX/RX Hardware frames)
With the 2.4GHz connection only nearly 50% of the HW Frames transmitted by the Mikrotik are accepted as Frames in the connection. by the GL SFT1200.
(2.4GHz is connection to the Mikrotik, clients are on te 5GHz band, so there is no switching between AP and station mode on one radio.)

No wonder WLAN3tracker sees problems.
This Mikrotik does not have problems with other client devices.

Will have to start "Mikrotik wireless sniffing" to see what happens here.

1 Like

Could improve the connection stability , by fiddling with the many WLAN parameters of the Mikrotik (the AP for the uplink), but as we have no access to the management of a hotel AP, work-arounds should be on the GL-SFT1200 only.

Well the 5 GHz connection is not perfect but gets 80% succesfull transmissions (CCQ).
By setting the 2.4GHz interface to "Legacy" mode in LUCI, and not N mode , the success rate for 2.4GHz goes up to 60% to even 80%, coming from less than 17%.

It starts to get usable for simple surfing. Applications and video still face lost connections and buffering waits. But it is at least not as horrible as it was.

Yes "Legacy" is probably G-mode, what is single stream only, but I do get a double stream connection with CCQ of 80% at 78Mbps , it adjusts between 56Mbps and 104Mbps , signal going through 2 walls with a signal strength of -58dBm at Mikrotik and -53dBm at GL-SFT1200. Noise at -83dBm.

This is usable for surfing, and gets close to the 5GHz uplink experience, which also is far from perfect.

Still not fully stable.
The use of 2 streams could be because the AP (Mikrotik) is still forcing the GL-SFT1200 to use n-mode wifi (allowing for 2 streams), and from time to time LUCI indeed reports mode N.

So lets force this with the Mikrotik AP. It's 2.4GHz WLAN interface is set now to "g-only mode".

Well the CCQ goes up to 98-100%. HW Frames and Frames send are now almost identical. Of course interface rate drops to 54Mbps, the highest in g-mode. But it stays there, no extra rate reduction for missed transmissions.

HW retries (in Mikrotik advanced settings) can be lowered now. From the high 15 as earlier stabilisation action, to the default 7. CCQ remains 100%, interface rate stable at 54Mbps.

Now running some HD youtubes ... CCQ stays above 98%, interface rate 54Mbps, effective data rate on Mikrotik 18Mbps. Data rate on Windows laptop ... 18Mbps indeed.

"Mikrotik <-2.4 GHz g-mode - > GL-SFT1200 < - 5GHz ac -> laptop". Stable 18 Mbps streaming video. No hickups, just perfect
30 minutes Youtube ... even HD resolution, not a single disconnect or hickup in the video.

Looks great !

EDIT: 19 hours later ... after working on this connection all day, checked this morning ... counter on Mikrotik shows uninterrupted connection for 19 hours now , 3GB traffic, on this 2.4GHz uplink. (Most clients are on 5GHz GL-SFT1200 network, but not all, so 2.4GHz has to switch AP/station mode.)

Interface rate is 54Mbps Tx/Rx . Is it the g-mode (802.11g), or the limited rate, that is giving this rock stable connection ?