SF1200 repeater mode hangs and disconnects

Routers
1

i have a opal sf1200 that i use as repeater for my second floor. it is connected to main router flint2 mt6000.

it loses a lot connections , sometimes it reconnects itself and sometimes i need to reboot it physically by unplugging it and plugging it back. while it loses connection i cannot connect to its wifi neither , it seems like the router is hanging/freezing but it seems that it doesn’t crash because crash log is empty.

I tried switching from 2.4ghz to 5ghz , forcing 40mhz , programming daily reboot, be sure timezone is fixed, changing to beta version 4.7.2 instead of last stable version. but same!

here is what it looks like when it hangs out for example at 23:20 , and at 23:39 i unplugged and plugged back

.

Sat Dec 27 23:20:42 2025 user.notice kmwan: config json str={ "op": 0, "data": { "sensitivity": 3000, "mode": "failover", "rtmode": 0 } }
Sat Dec 27 23:20:42 2025 kern.warn kernel: [ 56.116196] kmwan: sensitivity and mode are set.
Sat Dec 27 23:20:42 2025 daemon.err gl-repeater[947]: (repeater-nl80211.lua:305) hapdctl_connect: /var/run/hostapd-phy1.conf" not exist
Sat Dec 27 23:20:42 2025 daemon.err gl-repeater[947]: (repeater-nl80211.lua:174) wpactl_connect fail: /var/run/wpa_supplicant/sta1 does not exist
Sat Dec 27 23:20:44 2025 daemon.err gl-repeater[947]: (repeater-nl80211.lua:174) wpactl_connect fail: /var/run/wpa_supplicant/sta1 does not exist
Sat Dec 27 23:20:45 2025 daemon.err gl-repeater[947]: (repeater-nl80211.lua:174) wpactl_connect fail: /var/run/wpa_supplicant/sta1 does not exist
Sat Dec 27 23:20:47 2025 daemon.err gl-repeater[947]: (repeater-nl80211.lua:174) wpactl_connect fail: /var/run/wpa_supplicant/sta1 does not exist
Sat Dec 27 23:20:47 2025 daemon.notice netifd: init DPS_NL ret=0
Sat Dec 27 23:20:47 2025 daemon.notice netifd: get dps group=4
Sat Dec 27 23:20:47 2025 kern.info kernel: [ 60.845708] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sat Dec 27 23:20:47 2025 kern.info kernel: [ 61.548447] IPv6: ADDRCONF(NETDEV_UP): lo: link is not ready
Sat Dec 27 23:20:47 2025 kern.warn kernel: [ 61.682715] gmac open success
Sat Dec 27 23:20:47 2025 kern.info kernel: [ 61.695447] br-lan: port 1(eth0.1) entered blocking state
Sat Dec 27 23:20:47 2025 kern.info kernel: [ 61.701014] br-lan: port 1(eth0.1) entered disabled state
Sat Dec 27 23:20:47 2025 kern.info kernel: [ 61.707166] device eth0.1 entered promiscuous mode
Sat Dec 27 23:20:47 2025 kern.info kernel: [ 61.712515] device eth0 entered promiscuous mode
Sat Dec 27 23:20:48 2025 kern.info kernel: [ 61.721640] br-lan: port 1(eth0.1) entered blocking state
Sat Dec 27 23:20:48 2025 kern.info kernel: [ 61.727119] br-lan: port 1(eth0.1) entered forwarding state
Sat Dec 27 23:20:48 2025 daemon.notice netifd: Interface 'lan' is enabled
Sat Dec 27 23:20:48 2025 daemon.notice netifd: Interface 'lan' is setting up now
Sat Dec 27 23:20:48 2025 kern.warn kernel: [ 61.734220] [hnat info]add lan ip c0a80801 pf 24 index 0 name br-lan
Sat Dec 27 23:20:48 2025 daemon.notice netifd: Interface 'lan' is now up
Sat Dec 27 23:20:48 2025 daemon.notice netifd: Interface 'wan' is enabled
Sat Dec 27 23:20:48 2025 kern.info kernel: [ 61.758876] br-lan: port 2(eth0.2) entered blocking state
Sat Dec 27 23:20:48 2025 kern.info kernel: [ 61.764574] br-lan: port 2(eth0.2) entered disabled state
Sat Dec 27 23:20:48 2025 kern.info kernel: [ 61.771276] device eth0.2 entered promiscuous mode
Sat Dec 27 23:20:48 2025 kern.info kernel: [ 61.776705] br-lan: port 2(eth0.2) entered blocking state
Sat Dec 27 23:20:48 2025 kern.info kernel: [ 61.782378] br-lan: port 2(eth0.2) entered forwarding state
Sat Dec 27 23:20:48 2025 daemon.notice netifd: Interface 'loopback' is enabled
Sat Dec 27 23:20:48 2025 daemon.notice netifd: Interface 'loopback' is setting up now
Sat Dec 27 23:20:48 2025 daemon.notice netifd: Interface 'loopback' is now up
Sat Dec 27 23:20:48 2025 daemon.notice netifd: bridge 'br-lan' link is up
Sat Dec 27 23:20:48 2025 daemon.notice netifd: Interface 'lan' has link connectivity
Sat Dec 27 23:20:48 2025 daemon.notice netifd: Network device 'eth0' link is up
Sat Dec 27 23:20:48 2025 daemon.notice netifd: VLAN 'eth0.1' link is up
Sat Dec 27 23:20:48 2025 daemon.notice netifd: VLAN 'eth0.2' link is up
Sat Dec 27 23:20:48 2025 daemon.notice netifd: Interface 'wan' has link connectivity
Sat Dec 27 23:20:48 2025 daemon.notice netifd: Interface 'wan' is setting up now
Sat Dec 27 23:20:48 2025 daemon.notice netifd: Network device 'lo' link is up
Sat Dec 27 23:20:48 2025 daemon.notice netifd: Interface 'loopback' has link connectivity
Sat Dec 27 23:20:48 2025 daemon.err gl-repeater[947]: (repeater-nl80211.lua:174) wpactl_connect fail: /var/run/wpa_supplicant/sta1 does not exist
Sat Dec 27 23:20:48 2025 daemon.notice netifd: radio0 (1803): Command failed: Invalid argument
Sat Dec 27 23:20:48 2025 daemon.notice netifd: radio0 (1802): uci: Invalid argument
Sat Dec 27 23:20:48 2025 daemon.notice netifd: wan (1871): udhcpc: started, v1.29.3
Sat Dec 27 23:20:48 2025 kern.info kernel: [ 62.487473] lb-fmac 11000000.wifi-lb sta0: CLOSE
Sat Dec 27 23:20:48 2025 kern.warn kernel: [ 62.500089] lmac[0] vif_mgmt_unregister index=0
Sat Dec 27 23:20:48 2025 kern.warn kernel: [ 62.505008] rx_bufsz - 2560, rx_pd_offset - 224
Sat Dec 27 23:20:48 2025 daemon.notice netifd: radio0 (1803): uci: Invalid argument
Sat Dec 27 23:20:48 2025 kern.info kernel: [ 62.606582] lb-fmac 11000000.wifi-lb sta0: Remove Interface
Sat Dec 27 23:20:48 2025 kern.warn kernel: [ 62.612420] found hnat device to del
Sat Dec 27 23:20:48 2025 daemon.notice netifd: radio1 (1804): Command failed: Invalid argument
Sat Dec 27 23:20:48 2025 kern.info kernel: [ 62.687645] lb-fmac 11000000.wifi-lb sta0 (unregistering): Remove Interface Over
Sat Dec 27 23:20:48 2025 kern.info kernel: [ 62.701415] hb-fmac 17800000.wifi-hb sta1: CLOSE
Sat Dec 27 23:20:48 2025 kern.warn kernel: [ 62.706268] lmac[1] vif_mgmt_unregister index=0
Sat Dec 27 23:20:48 2025 kern.warn kernel: [ 62.714166] rx_bufsz - 2560, rx_pd_offset - 224
Sat Dec 27 23:20:49 2025 daemon.notice netifd: wan (1871): udhcpc: sending discover
Sat Dec 27 23:20:49 2025 daemon.notice netifd: radio0 (1803): command failed: No such device (-19)
Sat Dec 27 23:20:49 2025 kern.info kernel: [ 62.772999] hb-fmac 17800000.wifi-hb sta1: Remove Interface
Sat Dec 27 23:20:49 2025 kern.warn kernel: [ 62.778697] found hnat device to del
Sat Dec 27 23:20:49 2025 user.notice mac80211: Failed command: iw dev sta0 del
Sat Dec 27 23:20:49 2025 kern.info kernel: [ 62.854684] hb-fmac 17800000.wifi-hb sta1 (unregistering): Remove Interface Over
Sat Dec 27 23:20:49 2025 kern.info kernel: [ 62.961776] hb-fmac 17800000.wifi-hb wlan1: Remove Interface
Sat Dec 27 23:20:49 2025 kern.warn kernel: [ 62.967560] found hnat device to del
Sat Dec 27 23:20:49 2025 kern.info kernel: [ 63.082544] hb-fmac 17800000.wifi-hb wlan1 (unregistering): Remove Interface Over
Sat Dec 27 23:20:49 2025 kern.warn kernel: [ 63.148869] found hnat device to add
Sat Dec 27 23:20:49 2025 kern.warn kernel: [ 63.152684] [hnat notice]add wifi dev index 6 ndev85829000
Sat Dec 27 23:20:49 2025 kern.info kernel: [ 63.158955] lb-fmac 11000000.wifi-lb wlan0: Remove Interface
Sat Dec 27 23:20:49 2025 kern.warn kernel: [ 63.165009] found hnat device to del
Sat Dec 27 23:20:49 2025 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Sat Dec 27 23:20:49 2025 kern.info kernel: [ 63.242246] lb-fmac 11000000.wifi-lb wlan0 (unregistering): Remove Interface Over
Sat Dec 27 23:20:49 2025 daemon.notice netifd: radio1 (1805): command failed: Not supported (-122)
Sat Dec 27 23:20:49 2025 user.notice mac80211: Failed command: iw sta1 set power_save off
Sat Dec 27 23:20:49 2025 kern.warn kernel: [ 63.450507] lmac[1] vif_mgmt_register, vif_type : 0 status=0 index=0, req_idx=0
Sat Dec 27 23:20:49 2025 kern.warn kernel: [ 63.460597] lmac[1] use low txpower table
Sat Dec 27 23:20:49 2025 kern.warn kernel: [ 63.704468] radar set region 2
Sat Dec 27 23:20:49 2025 kern.warn kernel: [ 63.709055] radar set region 2
Sat Dec 27 23:20:50 2025 daemon.err gl-repeater[947]: (repeater-nl80211.lua:174) wpactl_connect fail: /var/run/wpa_supplicant/sta1 does not exist
Sat Dec 27 23:20:50 2025 user.notice mac80211: Failed command: iw phy phy0 set antenna all all
Sat Dec 27 23:20:50 2025 daemon.notice netifd: radio0 (1802): command failed: Not supported (-122)
Sat Dec 27 23:20:50 2025 user.notice mac80211: Failed command: iw phy phy0 set antenna_gain 0
Sat Dec 27 23:20:50 2025 kern.warn kernel: [ 64.395183] found hnat device to add
Sat Dec 27 23:20:50 2025 kern.warn kernel: [ 64.398864] [hnat notice]add wifi dev index 7 ndev85a2b000
Sat Dec 27 23:20:51 2025 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Sat Dec 27 23:20:51 2025 daemon.notice wpa_supplicant[2007]: Successfully initialized wpa_supplicant
Sat Dec 27 23:20:51 2025 kern.warn kernel: [ 64.769931] lmac[0] vif_mgmt_register, vif_type : 2 status=0 index=0, req_idx=0
Sat Dec 27 23:20:51 2025 kern.warn kernel: [ 64.777376] lmac[0] use low txpower table
Sat Dec 27 23:20:51 2025 user.notice mac80211: Failed command: iw phy phy1 set antenna all all
Sat Dec 27 23:20:51 2025 kern.info kernel: [ 64.801880] br-lan: port 3(wlan0) entered blocking state
Sat Dec 27 23:20:51 2025 kern.info kernel: [ 64.807303] br-lan: port 3(wlan0) entered disabled state
Sat Dec 27 23:20:51 2025 kern.info kernel: [ 64.814299] device wlan0 entered promiscuous mode
Sat Dec 27 23:20:51 2025 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat Dec 27 23:20:51 2025 daemon.notice netifd: radio1 (1804): command failed: Not supported (-122)
Sat Dec 27 23:20:51 2025 daemon.warn hostapd: wlan0: Could not connect to kernel driver
Sat Dec 27 23:20:51 2025 user.notice mac80211: Failed command: iw phy phy1 set antenna_gain 0
Sat Dec 27 23:20:51 2025 kern.info kernel: [ 64.833919] lb-fmac 11000000.wifi-lb wlan0: Del key for vif(0), key index : 0
Sat Dec 27 23:20:51 2025 kern.info kernel: [ 64.842754] lb-fmac 11000000.wifi-lb wlan0: Del key for vif(0), key index : 1
Sat Dec 27 23:20:51 2025 kern.info kernel: [ 64.851594] lb-fmac 11000000.wifi-lb wlan0: Del key for vif(0), key index : 2
Sat Dec 27 23:20:51 2025 kern.info kernel: [ 64.859743] lb-fmac 11000000.wifi-lb wlan0: Del key for vif(0), key index : 3
Sat Dec 27 23:20:51 2025 daemon.err hostapd: Using interface wlan0 with hwaddr 66:aa:ef:e0:ab:3e and ssid "GL-SFT1200-81c"
Sat Dec 27 23:20:51 2025 daemon.err gl-repeater[947]: (repeater-nl80211.lua:174) wpactl_connect fail: /var/run/wpa_supplicant/sta1 does not exist
Sat Dec 27 23:20:51 2025 daemon.notice hostapd: WPS: Converting push_button to virtual_push_button for WPS 2.0 compliance
Sat Dec 27 23:20:51 2025 kern.warn kernel: [ 65.402151] lmac[0] {CTXT-0} Create channel context: freq=2467MHz bw=40MHz pwr=20dBm
Sat Dec 27 23:20:51 2025 kern.warn kernel: [ 65.410090] lmac[0] {CTXT-0} link to {VIF-0}: status=0 nb_vif=0
Sat Dec 27 23:20:51 2025 kern.info kernel: [ 65.410379] lb-fmac 11000000.wifi-lb wlan0: AP started: ch=0, bcmc_idx=64
Sat Dec 27 23:20:51 2025 kern.info kernel: [ 65.423513] br-lan: port 3(wlan0) entered blocking state
Sat Dec 27 23:20:51 2025 kern.info kernel: [ 65.428934] br-lan: port 3(wlan0) entered forwarding state
Sat Dec 27 23:20:51 2025 kern.info kernel: [ 65.437925] lb-fmac 11000000.wifi-lb wlan0: Add key for vif(0), key index : 1
Sat Dec 27 23:20:51 2025 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->ENABLED
Sat Dec 27 23:20:51 2025 daemon.notice hostapd: wlan0: AP-ENABLED
Sat Dec 27 23:20:52 2025 kern.warn kernel: [ 65.792008] found hnat device to add
Sat Dec 27 23:20:52 2025 kern.warn kernel: [ 65.795698] [hnat notice]add wifi dev index 5 ndev8714b000
Sat Dec 27 23:20:52 2025 daemon.notice netifd: Network device 'wlan0' link is up
Sat Dec 27 23:20:52 2025 daemon.err hostapd: Configuration file: /var/run/hostapd-phy1.conf
Sat Dec 27 23:20:52 2025 daemon.notice netifd: sf_eth_event port 2 updown 1 is_wan 0 vlanid 1 ifname eth0
Sat Dec 27 23:20:52 2025 daemon.notice netifd: wan (1871): udhcpc: sending discover
Sat Dec 27 23:20:52 2025 user.notice relay: Reloading relay due to ifup of lan (br-lan)
Sat Dec 27 23:20:52 2025 kern.warn kernel: [ 65.882429] lmac[1] vif_mgmt_register, vif_type : 2 status=0 index=1, req_idx=0
Sat Dec 27 23:20:52 2025 kern.warn kernel: [ 65.890849] lmac[1] use low txpower table
Sat Dec 27 23:20:52 2025 kern.info kernel: [ 65.916964] br-lan: port 4(wlan1) entered blocking state
Sat Dec 27 23:20:52 2025 kern.info kernel: [ 65.922600] br-lan: port 4(wlan1) entered disabled state
Sat Dec 27 23:20:52 2025 kern.info kernel: [ 65.931146] device wlan1 entered promiscuous mode
Sat Dec 27 23:20:52 2025 daemon.notice hostapd: wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat Dec 27 23:20:52 2025 daemon.notice hostapd: ACS: Automatic channel selection started, this may take a bit
Sat Dec 27 23:20:52 2025 daemon.notice hostapd: wlan1: interface state COUNTRY_UPDATE->ACS
Sat Dec 27 23:20:52 2025 daemon.notice hostapd: wlan1: ACS-STARTED
Sat Dec 27 23:20:52 2025 daemon.err eco[700]: (gl-ngx-session:266) call cable.get_status fail: connect "127.0.0.1 80" fail: Connection refused
Sat Dec 27 23:20:52 2025 daemon.err eco[700]: (gl-ngx-session:266) call cable.get_status fail: connect "127.0.0.1 80" fail: Connection refused
Sat Dec 27 23:20:52 2025 daemon.notice wpa_supplicant[2291]: sta1: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Dec 27 23:20:53 2025 daemon.notice netifd: Interface 'wwan' is enabled
Sat Dec 27 23:20:53 2025 user.notice firewall: Reloading firewall due to ifup of loopback (lo)
Sat Dec 27 23:20:53 2025 daemon.notice wpa_supplicant[2291]: sta1: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sat Dec 27 23:20:54 2025 daemon.err block: /dev/ubiblock0_0 is already mounted on /rom
Sat Dec 27 23:20:54 2025 daemon.err block: /dev/ubi0_1 is already mounted on /overlay
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: acs_noradar = 1 means that the radar channels will be avoided under acs
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: wlan1: ACS-COMPLETED freq=5180 channel=36
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: wlan1: interface state ACS->HT_SCAN
Sat Dec 27 23:20:54 2025 daemon.warn hostapd: wlan1: Could not connect to kernel driver
Sat Dec 27 23:20:54 2025 kern.info kernel: [ 68.423956] hb-fmac 17800000.wifi-hb wlan1: Del key for vif(1), key index : 0
Sat Dec 27 23:20:54 2025 kern.info kernel: [ 68.431827] hb-fmac 17800000.wifi-hb wlan1: Del key for vif(1), key index : 1
Sat Dec 27 23:20:54 2025 kern.info kernel: [ 68.440453] hb-fmac 17800000.wifi-hb wlan1: Del key for vif(1), key index : 2
Sat Dec 27 23:20:54 2025 kern.info kernel: [ 68.448285] hb-fmac 17800000.wifi-hb wlan1: Del key for vif(1), key index : 3
Sat Dec 27 23:20:54 2025 daemon.err hostapd: Using interface wlan1 with hwaddr 2a:14:73:bc:84:7f and ssid "GL-SFT1200-81c-5G"
Sat Dec 27 23:20:54 2025 daemon.notice hostapd: WPS: Converting push_button to virtual_push_button for WPS 2.0 compliance
Sat Dec 27 23:20:55 2025 user.notice relay: Reloading relay due to ifup of loopback (lo)
Sat Dec 27 23:20:55 2025 daemon.err eco[700]: (gl-ngx-session:266) call cable.get_status fail: connect "127.0.0.1 80" fail: Connection refused
Sat Dec 27 23:20:55 2025 daemon.notice procd: /etc/rc.d/S50ieee80211: sh: can't open '/etc/hotplug.d/ieee80211/99-gl-detect': No such file or directory
Sat Dec 27 23:20:55 2025 daemon.notice procd: /etc/rc.d/S50ieee80211: sh: can't open '/etc/hotplug.d/ieee80211/99-gl-detect': No such file or directory
Sat Dec 27 23:20:56 2025 kern.info kernel: [ 70.196382] tertf: br-lan registered, add it
Sat Dec 27 23:20:56 2025 daemon.err gl-repeater[947]: (repeater-nl80211.lua:183) wait STATUS response fail: timeout
Sat Dec 27 23:20:56 2025 kern.warn kernel: [ 70.519458] lmac[1] {CTXT-0} Create channel context: freq=5180MHz bw=80MHz pwr=20dBm
Sat Dec 27 23:20:56 2025 kern.warn kernel: [ 70.527425] lmac[1] {CTXT-0} link to {VIF-1}: status=0 nb_vif=0
Sat Dec 27 23:20:56 2025 kern.info kernel: [ 70.527761] hb-fmac 17800000.wifi-hb wlan1: AP started: ch=0, bcmc_idx=65
Sat Dec 27 23:20:56 2025 kern.info kernel: [ 70.541136] br-lan: port 4(wlan1) entered blocking state
Sat Dec 27 23:20:56 2025 kern.info kernel: [ 70.546665] br-lan: port 4(wlan1) entered forwarding state
Sat Dec 27 23:20:56 2025 daemon.notice netifd: wan (1871): udhcpc: sending discover
Sat Dec 27 23:20:56 2025 daemon.notice wpa_supplicant[2291]: sta1: Trying to associate with 5e:45:92:14:02:32 (SSID='MAISON 5G' freq=5220 MHz)
Sat Dec 27 23:20:56 2025 kern.info kernel: [ 70.557708] hb-fmac 17800000.wifi-hb wlan1: Add key for vif(1), key index : 1
Sat Dec 27 23:20:56 2025 daemon.notice hostapd: wlan1: interface state HT_SCAN->ENABLED
Sat Dec 27 23:20:56 2025 daemon.notice hostapd: wlan1: AP-ENABLED
Sat Dec 27 23:20:56 2025 kern.warn kernel: [ 70.636188] lmac[1] {CTXT-1} Create channel context: freq=5220MHz bw=80MHz pwr=20dBm
Sat Dec 27 23:20:56 2025 kern.warn kernel: [ 70.644184] lmac[1] {CTXT-1} link to {VIF-0}: status=0 nb_vif=0
Sat Dec 27 23:20:56 2025 kern.warn kernel: [ 70.644229] lmac[1] rc_init: station_id=0 format_mod=4 pre_type=0 short_gi=1 max_bw=2
Sat Dec 27 23:20:56 2025 kern.warn kernel: [ 70.658231] lmac[1] rc_init: nss_max=1 mcs_max=9 r_idx_min=12 r_idx_max=12 no_samples=10
Sat Dec 27 23:20:56 2025 daemon.notice netifd: Network device 'sta1' link is up
Sat Dec 27 23:20:56 2025 daemon.notice netifd: Interface 'wwan' has link connectivity
Sat Dec 27 23:20:56 2025 daemon.notice netifd: Interface 'wwan' is setting up now
Sat Dec 27 23:20:56 2025 daemon.notice wpa_supplicant[2291]: sta1: Associated with 5e:45:92:14:02:32
Sat Dec 27 23:20:56 2025 daemon.notice wpa_supplicant[2291]: sta1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sat Dec 27 23:20:56 2025 kern.info kernel: [ 70.689084] hb-fmac 17800000.wifi-hb sta1: Add key for sta 0 (5e:45:92:14:02:32)
Sat Dec 27 23:20:56 2025 kern.info kernel: [ 70.701254] hb-fmac 17800000.wifi-hb sta1: Add key for vif(0), key index : 1
Sat Dec 27 23:20:56 2025 daemon.notice wpa_supplicant[2291]: sta1: WPA: Key negotiation completed with 5e:45:92:14:02:32 [PTK=CCMP GTK=CCMP]
Sat Dec 27 23:20:56 2025 daemon.notice wpa_supplicant[2291]: sta1: CTRL-EVENT-CONNECTED - Connection to 5e:45:92:14:02:32 completed [id=0 id_str=]
Sat Dec 27 23:20:57 2025 daemon.notice netifd: Network device 'wlan1' link is up
Sat Dec 27 23:20:57 2025 daemon.notice netifd: wwan (2879): udhcpc: started, v1.29.3
Sat Dec 27 23:20:57 2025 daemon.notice netifd: wwan (2879): udhcpc: sending discover
Sat Dec 27 23:20:57 2025 daemon.notice netifd: wwan (2879): udhcpc: sending select for 192.168.1.243
Sat Dec 27 23:20:57 2025 daemon.notice netifd: wwan (2879): udhcpc: lease of 192.168.1.243 obtained, lease time 43200
Sat Dec 27 23:20:57 2025 daemon.notice netifd: Interface 'wwan' is now up
Sat Dec 27 23:20:58 2025 daemon.info gl-repeater[947]: (repeater-nl80211.lua: 82) ATTACH /var/run/wpa_supplicant/sta1
Sat Dec 27 23:20:58 2025 daemon.info gl-repeater[947]: (repeater-nl80211.lua:163) ifname sta1 mtu nil
Sat Dec 27 23:20:58 2025 daemon.info gl-repeater[947]: (repeater.lua:485) connected to MAISON 5G 5e:45:92:14:02:32
Sat Dec 27 23:20:58 2025 daemon.info gl-repeater[947]: (repeater.lua:1695) interface "wwan" up
Sat Dec 27 23:20:58 2025 user.notice kmwan: config json str={ "op": 2, "data": { "cells": [ { "interface": "wwan", "netdev": "sta1", "track_mode": "force", "addr_type": 4, "force_ip": "192.168.1.243", "tracks": [ { "type": "ping", "ip": "1.1.1.1" }, { "type": "ping", "ip": "8.8.8.8" }, { "type": "ping", "ip": "208.67.222.222" }, { "type": "ping", "ip": "208.67.220.220" } ] } ] } }
Sat Dec 27 23:20:58 2025 kern.warn kernel: [ 72.146594] [add_dev_config 319]add node success. iface:wwan, dev:sta1, ifindex:13
Sat Dec 27 23:20:59 2025 user.notice firewall: Reloading firewall due to ifup of wwan (sta1)
Sat Dec 27 23:21:00 2025 daemon.info gl-repeater[947]: (repeater-portal.lua:410) portal detecting...
Sat Dec 27 23:21:01 2025 daemon.info gl-repeater[947]: (repeater-portal.lua:433) not found portal
Sat Dec 27 23:21:01 2025 user.notice relay: Reloading relay due to ifup of wwan (sta1)
Sat Dec 27 23:21:01 2025 daemon.err eco[700]: (gl-ngx-session:266) call cable.get_status fail: connect "127.0.0.1 80" fail: Connection refused
Sat Dec 27 23:21:05 2025 daemon.info procd: Instance relayd::instance1 pid 3195 not stopped on SIGTERM, sending SIGKILL instead
Sat Dec 27 23:21:08 2025 user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/dhcp
Sat Dec 27 23:21:08 2025 user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/radvd
Sat Dec 27 23:21:08 2025 user.notice ucitrack: Setting up /etc/config/wireless reload dependency on /etc/config/network
Sat Dec 27 23:21:08 2025 user.notice ucitrack: Setting up /etc/config/firewall reload dependency on /etc/config/luci-splash
Sat Dec 27 23:21:08 2025 user.notice ucitrack: Setting up /etc/config/firewall reload dependency on /etc/config/qos
Sat Dec 27 23:21:08 2025 user.notice ucitrack: Setting up /etc/config/firewall reload dependency on /etc/config/miniupnpd
Sat Dec 27 23:21:08 2025 user.notice ucitrack: Setting up /etc/config/dhcp reload dependency on /etc/config/odhcpd
Sat Dec 27 23:21:08 2025 user.notice ucitrack: Setting up non-init /etc/config/fstab reload handler: /sbin/block mount
Sat Dec 27 23:21:08 2025 user.notice ucitrack: Setting up /etc/config/system reload trigger for non-procd /etc/init.d/led
Sat Dec 27 23:21:09 2025 user.notice ucitrack: Setting up /etc/config/system reload dependency on /etc/config/luci_statistics
Sat Dec 27 23:21:09 2025 user.notice ucitrack: Setting up /etc/config/system reload dependency on /etc/config/dhcp
Sat Dec 27 23:21:12 2025 daemon.notice ksmbd: Starting Ksmbd userspace service.
Sat Dec 27 23:21:14 2025 daemon.info hostapd: wlan0: STA a2:2e:66:21:aa:cc IEEE 802.11: authenticated
Sat Dec 27 23:21:14 2025 kern.warn kernel: [ 88.545320] lmac[0] rc_init: station_id=0 format_mod=2 pre_type=0 short_gi=1 max_bw=1
Sat Dec 27 23:21:14 2025 kern.warn kernel: [ 88.553372] lmac[0] rc_init: nss_max=0 mcs_max=7 r_idx_min=12 r_idx_max=12 no_samples=10
Sat Dec 27 23:21:14 2025 kern.warn kernel: [ 88.579971] add sta(a2:2e:66:21:aa:cc) to hash table 33!
Sat Dec 27 23:21:14 2025 kern.info kernel: [ 88.585424] lb-fmac 11000000.wifi-lb wlan0: Add sta 0 (a2:2e:66:21:aa:cc) flags=[SHORT_PREAMBLE][WME][AUTHENTICATED][ASSOCIATED]
Sat Dec 27 23:21:14 2025 daemon.info hostapd: wlan0: STA a2:2e:66:21:aa:cc IEEE 802.11: associated (aid 1)
Sat Dec 27 23:21:14 2025 kern.info kernel: [ 88.652514] lb-fmac 11000000.wifi-lb wlan0: Del key for sta 0 (a2:2e:66:21:aa:cc)
Sat Dec 27 23:21:14 2025 kern.info kernel: [ 88.669125] lb-fmac 11000000.wifi-lb wlan0: Del key for sta 0 (a2:2e:66:21:aa:cc)
Sat Dec 27 23:21:14 2025 kern.info kernel: [ 88.683998] lb-fmac 11000000.wifi-lb wlan0: Del key for sta 0 (a2:2e:66:21:aa:cc)
Sat Dec 27 23:21:14 2025 kern.info kernel: [ 88.697107] lb-fmac 11000000.wifi-lb wlan0: Add key for vif(0), key index : 1
Sat Dec 27 23:21:15 2025 daemon.notice hostapd: wlan0: AP-STA-CONNECTED a2:2e:66:21:aa:cc
Sat Dec 27 23:21:15 2025 kern.info kernel: [ 88.719666] lb-fmac 11000000.wifi-lb wlan0: Add key for sta 0 (a2:2e:66:21:aa:cc)
Sat Dec 27 23:21:15 2025 daemon.info hostapd: wlan0: STA a2:2e:66:21:aa:cc RADIUS: starting accounting session 36C1FBF69C31586A
Sat Dec 27 23:21:15 2025 daemon.info hostapd: wlan0: STA a2:2e:66:21:aa:cc WPA: pairwise key handshake completed (RSN)
Sat Dec 27 23:21:15 2025 user.notice gl-switch: switch released
Sat Dec 27 23:21:15 2025 user.notice gl-switch: no config
Sat Dec 27 23:21:15 2025 daemon.notice procd: /etc/rc.d/S99wan_speed: uci: Entry not found
Sat Dec 27 23:21:15 2025 daemon.info procd: - init complete -
Sat Dec 27 23:39:10 2025 user.notice root: modem_traffic : ntp success...
Sat Dec 27 23:39:18 2025 daemon.info gl-repeater[947]: (repeater.lua:1197) ntp been valid
Sat Dec 27 23:39:24 2025 kern.err usbmuxd[5343]: [1] Another instance is already running (pid 3956). exiting.
Sat Dec 27 23:39:24 2025 kern.err usbmuxd[5345]: [1] Another instance is already running (pid 3956). exiting.
Sat Dec 27 23:39:26 2025 kern.err usbmuxd[5467]: [1] Another instance is already running (pid 3956). exiting.

2

It looks like this is the SFT1200 not the SF1200. Quite a different device. (and different firmware)

3

yes it is sft1200 sorry for mispelling the name, it did happen again right now with 2.4ghz, with repeater disabled from luci , the sft1200 is only serving internet via lan ports.

Sun Dec 28 17:40:35 2025 kern.warn kernel: \[ 3378.485560\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:40:35 2025 kern.warn kernel: \[ 3378.564271\] lmac\[0\] ps_check_tx_status ps_retry(3) failed, notify host we are lost!
Sun Dec 28 17:40:35 2025 kern.warn kernel: \[ 3378.572090\] lmac\[0\] {CTXT-2} unlink from {VIF-0}: status=1 nb_vif=1
Sun Dec 28 17:40:35 2025 kern.warn kernel: \[ 3378.572115\] lmac\[0\] {CTXT-2} Delete channel context
Sun Dec 28 17:40:35 2025 kern.info kernel: \[ 3378.578746\] lb-fmac 11000000.wifi-lb wlan-sta0: Del key for vif(0), key index : 0
Sun Dec 28 17:40:35 2025 daemon.notice wpa_supplicant\[1858\]: wlan-sta0: CTRL-EVENT-DISCONNECTED bssid=82:d5:5e:27:e5:52 reason=1 locally_generated=1
Sun Dec 28 17:40:35 2025 kern.info kernel: \[ 3378.591453\] lb-fmac 11000000.wifi-lb wlan-sta0: Del key for vif(0), key index : 1
Sun Dec 28 17:40:35 2025 kern.warn kernel: \[ 3378.596369\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:40:36 2025 kern.warn kernel: \[ 3378.707177\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:40:36 2025 kern.warn kernel: \[ 3378.818007\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:40:36 2025 kern.warn kernel: \[ 3378.928838\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:40:36 2025 kern.info kernel: \[ 3379.039120\] lb-fmac 11000000.wifi-lb wlan-sta0: Del key for vif(0), key index : 2
Sun Dec 28 17:40:36 2025 kern.info kernel: \[ 3379.046752\] lb-fmac 11000000.wifi-lb wlan-sta0: Del key for vif(0), key index : 3
Sun Dec 28 17:40:36 2025 kern.info kernel: \[ 3379.054241\] lb-fmac 11000000.wifi-lb wlan-sta0: Del key for vif(0), key index : 4
Sun Dec 28 17:40:36 2025 kern.info kernel: \[ 3379.061784\] lb-fmac 11000000.wifi-lb wlan-sta0: Del key for vif(0), key index : 5
Sun Dec 28 17:40:36 2025 daemon.notice netifd: Network device 'wlan-sta0' link is down
Sun Dec 28 17:40:36 2025 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Sun Dec 28 17:40:36 2025 daemon.notice wpa_supplicant\[1858\]: wlan-sta0: Reject scan trigger since one is already pending
Sun Dec 28 17:40:36 2025 daemon.warn wpa_supplicant\[1858\]: wlan-sta0: Failed to initiate AP scan
Sun Dec 28 17:40:36 2025 daemon.notice wpa_supplicant\[1858\]: wlan-sta0: Trying to associate with 82:d5:5e:27:e5:52 (SSID='MAISON' freq=2467 MHz)
Sun Dec 28 17:40:36 2025 kern.warn kernel: \[ 3379.095887\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:40:36 2025 kern.warn kernel: \[ 3379.126050\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:40:36 2025 daemon.notice netifd: wwan (15691): udhcpc: received SIGTERM
Sun Dec 28 17:40:36 2025 kern.warn kernel: \[ 3379.236193\] lmac\[0\] {CTXT-0} Create channel context: freq=2467MHz bw=20MHz pwr=30dBm
Sun Dec 28 17:40:36 2025 kern.warn kernel: \[ 3379.244145\] lmac\[0\] {CTXT-0} link to {VIF-0}: status=0 nb_vif=0
Sun Dec 28 17:40:36 2025 kern.warn kernel: \[ 3379.244176\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:40:36 2025 kern.warn kernel: \[ 3379.255945\] lmac\[0\] rc_init: station_id=3 format_mod=2 pre_type=0 short_gi=1 max_bw=0
Sun Dec 28 17:40:36 2025 kern.warn kernel: \[ 3379.263982\] lmac\[0\] rc_init: nss_max=1 mcs_max=7 r_idx_min=0 r_idx_max=3 no_samples=10
Sun Dec 28 17:40:36 2025 kern.warn kernel: \[ 3379.272024\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:40:36 2025 daemon.notice netifd: Network device 'wlan-sta0' link is up
Sun Dec 28 17:40:36 2025 daemon.notice netifd: Interface 'wwan' has link connectivity
Sun Dec 28 17:40:36 2025 daemon.notice netifd: Interface 'wwan' is setting up now
Sun Dec 28 17:40:36 2025 daemon.notice wpa_supplicant\[1858\]: wlan-sta0: Associated with 82:d5:5e:27:e5:52
Sun Dec 28 17:40:36 2025 daemon.notice wpa_supplicant\[1858\]: wlan-sta0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sun Dec 28 17:40:36 2025 kern.info kernel: \[ 3379.337867\] lb-fmac 11000000.wifi-lb wlan-sta0: Add key for sta 3 (82:d5:5e:27:e5:52)
Sun Dec 28 17:40:36 2025 daemon.notice wpa_supplicant\[1858\]: wlan-sta0: WPA: Key negotiation completed with 82:d5:5e:27:e5:52 \[PTK=CCMP GTK=CCMP\]
Sun Dec 28 17:40:36 2025 daemon.notice wpa_supplicant\[1858\]: wlan-sta0: CTRL-EVENT-CONNECTED - Connection to 82:d5:5e:27:e5:52 completed \[id=0 id_str=\]
Sun Dec 28 17:40:36 2025 kern.info kernel: \[ 3379.347065\] lb-fmac 11000000.wifi-lb wlan-sta0: Add key for vif(0), key index : 1
Sun Dec 28 17:40:36 2025 daemon.notice netifd: wwan (27298): udhcpc: started, v1.29.3
Sun Dec 28 17:40:36 2025 daemon.notice netifd: wwan (27298): udhcpc: sending discover
Sun Dec 28 17:40:36 2025 daemon.notice netifd: wwan (27298): udhcpc: sending select for 192.168.1.243
Sun Dec 28 17:40:37 2025 daemon.notice netifd: wwan (27298): udhcpc: lease of 192.168.1.243 obtained, lease time 43200
Sun Dec 28 17:40:37 2025 daemon.warn dnsmasq\[951\]: no servers found in /tmp/resolv.conf.auto, will retry
Sun Dec 28 17:40:37 2025 daemon.notice netifd: Interface 'wwan' is now up
Sun Dec 28 17:40:37 2025 daemon.info dnsmasq\[951\]: reading /tmp/resolv.conf.auto
Sun Dec 28 17:40:37 2025 daemon.info dnsmasq\[951\]: using local addresses only for domain test
Sun Dec 28 17:40:37 2025 daemon.info dnsmasq\[951\]: using local addresses only for domain onion
Sun Dec 28 17:40:37 2025 daemon.info dnsmasq\[951\]: using local addresses only for domain localhost
Sun Dec 28 17:40:37 2025 daemon.info dnsmasq\[951\]: using local addresses only for domain local
Sun Dec 28 17:40:37 2025 daemon.info dnsmasq\[951\]: using local addresses only for domain invalid
Sun Dec 28 17:40:37 2025 daemon.info dnsmasq\[951\]: using local addresses only for domain bind
Sun Dec 28 17:40:37 2025 daemon.info dnsmasq\[951\]: using local addresses only for domain lan
Sun Dec 28 17:40:37 2025 daemon.info dnsmasq\[951\]: using nameserver 192.168.1.3#53
Sun Dec 28 17:40:37 2025 user.notice mwan3\[27246\]: Execute ifdown event on interface wwan (unknown)
Sun Dec 28 17:40:37 2025 user.info mwan3track\[16448\]: Detect ifdown event on interface wwan (wlan-sta0)
Sun Dec 28 17:40:37 2025 user.notice mwan3track\[16448\]: Interface wwan (wlan-sta0) is offline
Sun Dec 28 17:40:39 2025 user.notice firewall: Reloading firewall due to ifdown of wwan ()
Sun Dec 28 17:40:39 2025 user.notice relay: Reloading relay due to disconnected of wwan (wlan-sta0)
Sun Dec 28 17:40:41 2025 user.notice relay: Reloading relay due to ifdown of wwan ()
Sun Dec 28 17:40:42 2025 user.notice mwan3\[27843\]: Execute ifup event on interface wwan (wlan-sta0)
Sun Dec 28 17:40:43 2025 user.notice mwan3\[27843\]: Starting tracker on interface wwan (wlan-sta0)
Sun Dec 28 17:40:43 2025 user.notice mwan3track\[16448\]: Stopping mwan3track for interface "wwan"
Sun Dec 28 17:40:46 2025 user.info mwan3rtmon\[2230\]: Detect rtchange event.
Sun Dec 28 17:40:47 2025 user.notice firewall: Reloading firewall due to ifup of wwan (wlan-sta0)
Sun Dec 28 17:40:47 2025 user.notice relay: Reloading relay due to connected of wwan (wlan-sta0)
Sun Dec 28 17:40:48 2025 user.notice relay: Reloading relay due to ifup of wwan (wlan-sta0)
Sun Dec 28 17:45:36 2025 kern.warn kernel: \[ 3679.392165\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:45:36 2025 kern.warn kernel: \[ 3679.502962\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:45:36 2025 kern.warn kernel: \[ 3679.533870\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:45:37 2025 kern.warn kernel: \[ 3679.644656\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:45:37 2025 kern.warn kernel: \[ 3679.675588\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:45:37 2025 kern.warn kernel: \[ 3679.786357\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:45:37 2025 kern.warn kernel: \[ 3679.816620\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:45:37 2025 kern.warn kernel: \[ 3679.926750\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:45:37 2025 kern.warn kernel: \[ 3679.958498\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:45:37 2025 kern.warn kernel: \[ 3680.069333\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:50:36 2025 kern.warn kernel: \[ 3979.392591\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:50:36 2025 kern.warn kernel: \[ 3979.503385\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:50:36 2025 kern.warn kernel: \[ 3979.537274\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:50:37 2025 kern.warn kernel: \[ 3979.648065\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:50:37 2025 kern.warn kernel: \[ 3979.679136\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:50:37 2025 kern.warn kernel: \[ 3979.789931\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:50:37 2025 kern.warn kernel: \[ 3979.820454\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:50:37 2025 kern.warn kernel: \[ 3979.930594\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:50:37 2025 kern.warn kernel: \[ 3979.962165\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:50:37 2025 kern.warn kernel: \[ 3980.073019\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:55:36 2025 kern.warn kernel: \[ 4279.396573\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:55:36 2025 kern.warn kernel: \[ 4279.507375\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:55:36 2025 kern.warn kernel: \[ 4279.538276\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:55:37 2025 kern.warn kernel: \[ 4279.649077\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:55:37 2025 kern.warn kernel: \[ 4279.679981\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:55:37 2025 kern.warn kernel: \[ 4279.790780\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:55:37 2025 kern.warn kernel: \[ 4279.821011\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:55:37 2025 kern.warn kernel: \[ 4279.931159\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:55:37 2025 kern.warn kernel: \[ 4279.962727\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:55:37 2025 kern.warn kernel: \[ 4280.073560\] lmac\[0\] final dsss power is 27 ofdm power is 27
Sun Dec 28 17:56:15 2025 user.notice mwan3\[29369\]: Execute ifdown event on interface wwan (wlan-sta0)
Sun Dec 28 17:56:16 2025 user.notice firewall: Reloading firewall due to ifdown of wwan (wlan-sta0)
Sun Dec 28 17:56:17 2025 user.notice relay: Reloading relay due to ifdown of wwan (wlan-sta0)
Sun Dec 28 17:56:17 2025 user.info mwan3track\[28060\]: Detect ifdown event on interface wwan (wlan-sta0)
Sun Dec 28 17:56:22 2025 user.notice mwan3track\[28060\]: Interface wwan (wlan-sta0) is offline
Sun Dec 28 17:56:24 2025 user.notice relay: Reloading relay due to disconnected of wwan (wlan-sta0)
Sun Dec 28 17:59:32 2025 user.info mwan3track\[28060\]: Lost 70 ping(s) on interface wwan (wlan-sta0)
Sun Dec 28 18:00:08 2025 user.notice mwan3track\[28060\]: Interface wwan (wlan-sta0) is online
Sun Dec 28 18:00:09 2025 user.notice mwan3\[5097\]: Execute ifup event on interface wwan (wlan-sta0)
Sun Dec 28 18:00:10 2025 user.notice mwan3\[5097\]: Starting tracker on interface wwan (wlan-sta0)
Sun Dec 28 18:00:14 2025 user.info mwan3rtmon\[2230\]: Detect rtchange event.
Sun Dec 28 18:00:15 2025 user.notice firewall: Reloading firewall due to ifup of wwan (wlan-sta0)
Sun Dec 28 18:00:15 2025 user.notice relay: Reloading relay due to connected of wwan (wlan-sta0)
Sun Dec 28 18:00:16 2025 user.notice relay: Reloading relay due to ifup of wwan (wlan-sta0)

it seems to be a bug with MT7622 drivers. i will try to switch again to 5ghz and see while keeping repeater off

4

Hi,

Could you please confirm the following details so we can narrow this down?

  1. Please confirm you’re powering the SFT1200 with the original adapter (recommended), or a stable 5V/3A power supply.
  2. May we know whether you’re using Extender mode? We see the relay have being enabled which usually indicates a Extender mode configuration.
  3. Please upgrade to the latest v4.7.2 beta firmware, then reboot the device once after the upgrade.
  4. If you’ve modified settings in LuCI, please do a factory reset and set it up again using only the GL UI to avoid configuration conflicts.
  5. If it still happens, please export the logs and send them to us via private message, and include the approximate timestamp when the issue occurred (and what you observed at that moment). This will help us correlate it with the log entries.

Firmware Download link:

Upgrade guide:

How to export logs:

image
image1430×911 87 KB

How to send private messages:

image
image632×233 19.1 KB

5

I have never seen the need for that 3A current power. Measuring the consumed power (current) on USB never went to a high number. A USB port of a laptop (<700mA) will be strong enough.

The 3A could only be relevant if the SFT1200 USB A peripheral would draw a lot of power. (But SMB for the disk is not even supported until 4.8.3beta)

Latest 4.72beta openwrt-sft1200-4.7.2-0421-1745200874 has high power and is “usable”

However SFT1200-4.8.3_beta1-926-1209-1765245228 is even better, but has a 1000x (30dB) reduced TX power level. Just as the first beta of 4.7.2 did in openwrt-sft1200-4.7.2-1227-1735237824

Maybe the reason is visible here … (phy0 or phy1)

# cd /sys/kernel/debug/ieee80211/phy0/siwifi
root@GL-SFT1200:/sys/kernel/debug/ieee80211/phy0/siwifi# grep -H . *

Learned from: wifi调试 — 矽昌通信

6

You do have that troubled SFT1200

https://forum.gl-inet.com/t/gl-sft1200-opal-keeps-disconnecting-and-reconnecting-to-wwan/38854/7?u=bpwl1

https://siflower.github.io/2020/08/12/wifi_architecture_and_configuration_manual/#22-wifi%E4%B8%8A%E5%B1%82%E9%85%8D%E7%BD%AE%E8%AF%B4%E6%98%8E

The SIFlower hardware SF16a29 and driver are unique and closed source. It seems like they cannot make it work. Either the signal is strong and unstable, or it is stable but very very weak.

The variations are even in the different 4.7.2beta releases. (beta1,beta2 and beta3)

4.8.3 beta was stable but very weak. They removed it again!

At least the 4.8.3 had more options to reduce the connection tracking disasterous implementation.

Because the GL.Inet implementation makes it all worse.

If the connection has a glitch (you lost 20 pings as seen in you log) then the reset of the connection is a cure worse than the disease.

It drops the firewall and all IP connections, in case of a short interruption (interference?) or even when volontary roaming is done.

Stop using connection tracking, it makes no sense if there is only one possible uplink, to stop MWAN3 track disconnects

Give only one SSID for the uplink, and set the BSSID as locked, to stop roaming.(which brings yet another firewall reset and major disconnect)

For 5GHz (more stability and less interference) have no SSID for AP's that operate in the DFS channel range in the list (SFT1200 will not connect to DFS with most 4.x firmwares)

And we hope for the next 4.8.3beta with better power, as the extra options in this beta are great for uplink stability.

7

you actually described most of the problems .
i think i found the issue, and the solution for it! after almost 24 hours no disconnection so far , stable too.

my flint 2 was using channel 12 with channel set (auto) and 40 mhz , i changed it to channel 11 and reduced TX from 20dmb to 18dbm , and set it to 20mhz.
the sft1200 now receive a wifi signal/noise of -34 / 0 dBm, compared to -27 / 0 dBm with original TX = 20 dbm.

  • disabled mwan3
  • disabled Disassociate On Low Acknowledgement.
    the error ““ lmac[0] final dsss power is 27 ofdm power is 27 ““ does appear less often , and the sft1200 doesn’t drop wifi signal / connection .
    seems like the the sft1200 have problem to stay stable while connected to a wifi with channel 12 and high TX power.

I hope this will stay stable like this for a longer period, and i hope it will work for others too.
For me i hope it stays at least for 48 hours stable, i can schedule a restart if it is the case !

8

I hope it stays stable now.

I experienced the problem with too strong Wifi signals (> -30dBm) consistently on 21 Mikrotik hAPac2 that I deployed in a holiday resort. As the Mikrotiks were on a low cabinet in their room people used to put their devices on the same cabinet, “to have a good wifi signal”. But a travel router has a much stronger signal (typical 20dBm) than a laptop, tablet or smartphone (10 to 14dBm). The connection died, and EAP/enterprise logon was impossible (failed).

Too weak signal is well known, too strong signal seems to be unknown. (The guests refused to accept that “too close” fact,and ignoring this had no wifi internet with their travel router.)

1 Like
10

2Days:1Hours:*52Minutes i didn’t to reboot , wifi didn’t hang/freeze, didn’t disconnect !

I can confirm the SFT1200 doesn’t like too strong wifi signal, doesn’t like channel 12 either !

Solution : Move the sft1200 further away or lower the original wifi signal TX power.

  • Don’t use channel 12 or channel 1, use channels in the middle !*