@bpwl1 have you tried the new 4.3.24 firmware?
https://dl.gl-inet.com/router/sft1200/stable
Heh no! Didn't see that upgrade, was only following the 4.7.2beta for improvements. There were lots of improvements in 4.7.2beta. (but with power and DFS problem)
Are the same improvements to be expected in 4.3.24 ??? (This is a lower version number, will 4.7.2 improvements be there then?)
Ok will certainly check. AFAIK 4.3.21 had no low power or DFS channel problem, but MPDU and connection stability with multiple BSSID, and too strict hotplug actions with MWAN3. So I'm a bit confused with the 4.3.24 release notes.
Waw ... will need some time to figure out where we are with this.
- looks like a 4.3.21 upgrade (4.7.2beta features missing)
- But 27 dBm stonger than 4.7.2beta, forgot exact power numbers for 4.3.21)
- This starts DFS radar detect !? Country in LUCI is still US? Power cfr LUCI is 20 dBm , don't believe this, LOG says different things.
Mon Feb 10 07:03:32 2025 daemon.notice hostapd: wlan1: interface state DFS->ENABLED
Mon Feb 10 07:03:32 2025 daemon.notice hostapd: wlan1: AP-ENABLED
Mon Feb 10 07:03:32 2025 kern.warn kernel: [ 536.088647] lmac[1] final dsss power is 27 ofdm power is 27
Next day:
OK time to do a little test today, have to remember what where the issues with 4.3.21.
SFT1200 helps me remember it in the first minutes of the test already, for the bad reason, problems come back ..
Here is the first: SFT1200 confused by beacon information.
Mon Feb 10 16:23:13 2025 daemon.info lua: (...pkg-mips_siflower/gl-sdk4-repeater/usr/sbin/repeater:1239) connected to 'bpacrt_5G(48:a9:8a:d7:eb:46)' channel: 100, spent 2s
Mon Feb 10 16:23:14 2025 user.notice mwan3[18202]: Execute ifup event on interface wwan (wlan-sta0)
Mon Feb 10 16:23:15 2025 user.notice mwan3[18202]: Starting tracker on interface wwan (wlan-sta0)
Mon Feb 10 16:23:15 2025 user.notice mwan3track[15761]: Stopping mwan3track for interface "wwan"
Mon Feb 10 16:23:18 2025 user.info mwan3rtmon[2419]: Detect rtchange event.
Mon Feb 10 16:23:19 2025 user.notice firewall: Reloading firewall due to ifup of wwan (wlan-sta0)
Mon Feb 10 16:23:20 2025 user.notice relay: Reloading relay due to connected of wwan (wlan-sta0)
Mon Feb 10 16:23:20 2025 user.notice relay: Reloading relay due to ifup of wwan (wlan-sta0)
Mon Feb 10 16:27:07 2025 authpriv.info dropbear[27136]: Child connection from 192.168.8.142:59458
Mon Feb 10 16:27:20 2025 authpriv.notice dropbear[27136]: Password auth succeeded for 'root' from 192.168.8.142:59458
Mon Feb 10 16:37:42 2025 daemon.notice wpa_supplicant[17836]: wlan-sta0: CTRL-EVENT-DISCONNECTED bssid=48:a9:8a:d7:eb:46 reason=1 locally_generated=1
Mon Feb 10 16:37:42 2025 daemon.info lua: (...pkg-mips_siflower/gl-sdk4-repeater/usr/sbin/repeater:548) <3>CTRL-EVENT-DISCONNECTED bssid=48:a9:8a:d7:eb:46 reason=1 locally_generated=1
Mon Feb 10 16:37:42 2025 kern.warn kernel: [ 1222.047585] lmac[1] vif working channel(100) is different from channel(0) of received beacon frame, notify that we are lost!
Mon Feb 10 16:37:42 2025 kern.warn kernel: [ 1222.058867] lmac[1] {CTXT-1} unlink from {VIF-3}: status=4 nb_vif=2
Mon Feb 10 16:37:42 2025 kern.info kernel: [ 1222.059386] hb-fmac 17800000.wifi-hb wlan-sta0: Del key for vif(3), key index : 0
Mon Feb 10 16:37:42 2025 kern.info kernel: [ 1222.073422] hb-fmac 17800000.wifi-hb wlan-sta0: Del key for vif(3), key index : 1
Mon Feb 10 16:37:42 2025 kern.info kernel: [ 1222.081056] hb-fmac 17800000.wifi-hb wlan-sta0: Del key for vif(3), key index : 2
Mon Feb 10 16:37:42 2025 kern.info kernel: [ 1222.088827] hb-fmac 17800000.wifi-hb wlan-sta0: Del key for vif(3), key index : 3
Mon Feb 10 16:37:42 2025 kern.info kernel: [ 1222.096360] hb-fmac 17800000.wifi-hb wlan-sta0: Del key for vif(3), key index : 4
Mon Feb 10 16:37:42 2025 kern.info kernel: [ 1222.103984] hb-fmac 17800000.wifi-hb wlan-sta0: Del key for vif(3), key index : 5
Mon Feb 10 16:37:42 2025 daemon.notice netifd: Network device 'wlan-sta0' link is down
Mon Feb 10 16:37:42 2025 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Mon Feb 10 16:37:43 2025 daemon.info lua: (...pkg-mips_siflower/gl-sdk4-repeater/usr/sbin/repeater:548) <3>CTRL-EVENT-SCAN-STARTED
Mon Feb 10 16:37:43 2025 kern.warn kernel: [ 1222.191737] lmac[1] final dsss power is 27 ofdm power is 27
Mon Feb 10 16:37:43 2025 daemon.notice netifd: wwan (18137): udhcpc: received SIGTERM
Blockquote
Does GL.inet ever test their device firmware? Only against other GL.inet???
Take some AP, 5GHz on 40 MHz wide channel, 56dBm signal. Connect GL.inet (2S/40MHz,400Mbps real interface rate)... get good Speedtest speed on the ethernet port. (My ISP only gives 50Mbps , and I get it full speed via GL.inet repeater uplink, and ethernet client connect.
As repeater the config of the 5GHz client wifi setting is defined by the uplink. However the bandwidth is not the same (but is set to 20MHz), just get 3Mbps download on 5GHz wifi-link, and 2 Mbps on 2.4GHz wifi-link with 144Mbps interface rate. Quite a repeater dramatic bad performance. Expected half or 40%, not 5% performance of the single connection.
OK lets remove the ISP.
Download from my NAS on my home network. Via SFT1200 uplink (2S/40MHz,400Mbps interface rate) and Wifi 5GHz client (173Mbps interface rate) gives 15Mbps data, ethernet client 256Mbps data, with that 5GHz uplink through the SFT1200.
Just as reference , same test with Cudy TR1200 (similar travel router, but only 100Mbps ethernet)
5GHz , same AP, same SSID, same connection, 2S/40MHz/400Mbps. Cudy follows channel 100 and correctly copies the 40MHz bandwidth. WISP mode (= router + NAT)
5GHz AP : 400Mbps interface rate, 300Mbps dynamic MCS rate at AP, -62dBm signal at AP.
5GHz client show 400Mbps at PC. [Windows PC only shows max MCS rate, never real time actual rate]
Effective Data rate 120Mbps (118-125Mbps)
Idem with ethernet setup as client link: 99Mbps data rate
Idem with 2.4GHz client connect (2S/20MHz/144Mbps at PC)
[Windows PC only shows max MCS rate, never real time actual rate]
Effective 80Mbps data rate (71-87Mbps)
So comparing, while using that 5GHz uplink with 400Mbps MCS data rate
PC Client rate (interface/GL.inet SFT1200 - Cudy TR1200)
(5GHz / 15Mbps - 120Mbps)
(ethernet / 256Mbps - 99Mbps)
(2.4GHz /8Mbps - 80Mbps)
OK. Moving back to the beta version. Nothing usefull here with this regular version.
After moving and checking if DFS and power would still be there ...
It's not, and LUCI proves again to live in a parallel world.
Uplink still shows channel 100, client shows channel 36.
And that uplink LUCI info is clearly wrong with the dB power setting 127dBm , waw, "microwave oven/drone gun" power.
Not a fair test with such a weak signal (dropped to single stream, and lower MCS giving 120Mbps interface rate, missing 1 in 3 packets per CCQ, this AP still sends 40MHz bandwidth, on channel 36, SFT forced itself to 20 MHz, but still only getting 3Mbps on this connection is too low). Forcing it to 40MHz with LUCI brings just a little more)
2 Likes