MT7615D STA+AP not working
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
When adding STA to the 2.4Ghz radio on the GL-MT1300 (MT7615D) 2.4Ghz, the radio does not come up anymore.
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='SNAPSHOT'
DISTRIB_REVISION='r19119-da2b97210c'
DISTRIB_TARGET='ramips/mt7621'
DISTRIB_ARCH='mipsel_24kc'
DISTRIB_DESCRIPTION='OpenWrt SNAPSHOT r19119-da2b97210c'
Tue Mar 15 13:06:54 2022 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy wlan0-1) --> new PHY
Tue Mar 15 13:06:54 2022 kern.info kernel: [ 306.269406] br-lan: port 3(wlan0-1) entered blocking state
Tue Mar 15 13:06:54 2022 kern.info kernel: [ 306.274981] br-lan: port 3(wlan0-1) entered disabled state
Tue Mar 15 13:06:54 2022 kern.info kernel: [ 306.281491] device wlan0-1 entered promiscuous mode
Tue Mar 15 13:06:54 2022 daemon.notice hostapd: wlan0-1: interface state UNINITIALIZED->ENABLED
Tue Mar 15 13:06:54 2022 daemon.notice hostapd: wlan0-1: AP-ENABLED
Tue Mar 15 13:06:56 2022 daemon.notice netifd: radio0 (6384): sh: out of range
Tue Mar 15 13:06:56 2022 daemon.notice netifd: Wireless device 'radio0' is now up
Tue Mar 15 13:06:56 2022 daemon.notice netifd: Interface 'test' is enabled
Tue Mar 15 13:06:56 2022 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 15 13:07:02 2022 daemon.notice wpa_supplicant[3621]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Tue Mar 15 13:07:11 2022 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 15 13:07:11 2022 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 15 13:07:11 2022 daemon.notice hostapd: handle_probe_req: send failed
When STA+AP is run on the 5Ghz interface, it also does not come up anymore. In addition, it is not possible to connect to the 2.4Ghz AP, despite its SSID showing.
Tue Mar 15 13:47:31 2022 daemon.notice netifd: Interface 'lan' has link connectivity
Tue Mar 15 13:47:31 2022 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->HT_SCAN
Tue Mar 15 13:47:32 2022 kern.info kernel: [ 2743.919345] br-lan: port 4(wlan0) entered disabled state
Tue Mar 15 13:47:32 2022 daemon.notice netifd: radio1 (6762): sh: out of range
Tue Mar 15 13:47:32 2022 daemon.notice netifd: Wireless device 'radio0' is now up
Tue Mar 15 13:47:32 2022 daemon.notice netifd: Wireless device 'radio1' is now up
Tue Mar 15 13:47:32 2022 daemon.notice netifd: Interface 'test' is enabled
Tue Mar 15 13:47:32 2022 daemon.notice hostapd: 20/40 MHz operation not permitted on channel pri=1 sec=5 based on overlapping BSSes
Tue Mar 15 13:47:32 2022 daemon.notice hostapd: Fallback to 20 MHz
Tue Mar 15 13:47:33 2022 kern.info kernel: [ 2744.602524] br-lan: port 4(wlan0) entered blocking state
Tue Mar 15 13:47:33 2022 kern.info kernel: [ 2744.607862] br-lan: port 4(wlan0) entered forwarding state
Tue Mar 15 13:47:33 2022 daemon.notice netifd: Network device 'wlan0' link is up
Tue Mar 15 13:47:33 2022 daemon.notice hostapd: wlan0: interface state HT_SCAN->ENABLED
Tue Mar 15 13:47:33 2022 daemon.notice hostapd: wlan0: AP-ENABLED
Tue Mar 15 13:47:33 2022 daemon.notice wpa_supplicant[3621]: wlan1: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Tue Mar 15 13:47:33 2022 daemon.notice hostapd: wlan1-1: ACS-COMPLETED freq=5180 channel=36
Tue Mar 15 13:47:33 2022 daemon.notice hostapd: wlan1-1: interface state ACS->ENABLED
Tue Mar 15 13:47:33 2022 daemon.notice hostapd: wlan1-1: AP-ENABLED
Tue Mar 15 13:47:45 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:47:46 2022 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 15 13:47:49 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:47:53 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:47:57 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:48:00 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:48:04 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:48:08 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:48:12 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:48:16 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:48:20 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:48:24 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:48:28 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:48:32 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:48:35 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:48:39 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:48:43 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:48:47 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:48:51 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:48:55 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:48:59 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:49:03 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:49:07 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:49:10 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:49:14 2022 daemon.warn wpa_supplicant[3621]: wlan1: Failed to initiate sched scan
Tue Mar 15 13:49:15 2022 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 15 13:49:17 2022 daemon.notice hostapd: handle_probe_req: send failed
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing STA+AP on the GL-MT1300 with the reported 2.4 GHz and 5 GHz configurations, then inspect the hostapd, wpa_supplicant, netifd, and kernel log messages shown here. Done means both STA+AP configurations bring up the radio and allow clients to connect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100