Hello forum, sorry for asking this question but I could not find any similar query / response.
I have been able to install several routers / APs with OpenWRT and I like it a lot.
Recently I got a D-LINK DAP-2610 which I want to use as a dumb AP with 2.4 and 5 G wlan.
I installed successfully 22.03.5, but it looks like my 2.4 wifi does not work... when I do the scan with the "wireless" section of LUCI, nothing is found (of course I've plenty of wifi ESSID's), but Status->Channel Analysis seems to show the wifi network.
The problem is: I cannot find the 2.4 ESSID with any client (linux, windows, android), simply does not show up.
Also tried a downgrade to 21.02.7 (hoping to get better support for IPQ4019), with no joy.
I can successfully connect to a 5G (ac) ESSID on same AP.
Any idea / suggestion? could the 2,4G radio be broken 
?
Welcome to the community!
Is Channel 13 legal in your nation?
Sorry I replied to email, and it seems got not copied to the forum.
Yes, channel 13 is legal.
But I also tried all other channels with no success.
In a nutshell:
- radio1 (5Ghz) is able to scan the wifi space and reports existing ESSID's; radio1 is working and I can "see and connect" to the ESSID (in other words, the wifi is OK),
- radio0 (2.4Ghz) says "No Data" when scanning the air and I cannot "see and connect" to the ESSID (so wifi is not Ok),
- radio1 is able to report existing ESSIDs when doing Status->Channel Analysis, while radio0 only reports its local interface.
Guess I'm looking for somebody who succeeded setting up the DAP2610 on 2.4Ghz wifi to get some help.
Maybe there is some log file on the device I can look for?
I suspect there is a HW problem. The DAP is powered via a DPE-101GI PoE injector (as indicated in the D-Link manual), so I suppose power is "OK". But I also tried with another power supply rated 9V, without PoE, and it works. But the problem with 2.4 Ghz remains.
Thanks to anyone who can give advice.
Forgot to say I'm back on 22.03.5.
Tried ACS for radio0 with no better luck.
Here below please find the extract from log which is the result of a DISABLE + ENABLE on the ESSID via LuCi.
w24G is the name of the 2.4G interface (default would be wlan0).
Tue Jun 20 09:58:43 2023 kern.info kernel: [ 1846.733844] device w24G left promiscuous mode
Tue Jun 20 09:58:43 2023 kern.info kernel: [ 1846.734044] br-lan: port 3(w24G) entered disabled state
Tue Jun 20 09:58:43 2023 daemon.notice hostapd: Remove interface 'w24G'
Tue Jun 20 09:58:43 2023 daemon.notice hostapd: w24G: interface state ENABLED->DISABLED
Tue Jun 20 09:58:43 2023 daemon.notice hostapd: w24G: AP-DISABLED
Tue Jun 20 09:58:43 2023 daemon.notice hostapd: w24G: CTRL-EVENT-TERMINATING
Tue Jun 20 09:58:43 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Tue Jun 20 09:58:43 2023 daemon.notice hostapd: nl80211: deinit ifname=w24G disabled_11b_rates=0
Tue Jun 20 09:58:43 2023 daemon.notice hostapd: nl80211: Failed to remove interface w24G from bridge br-lan: Invalid argument
Tue Jun 20 09:58:43 2023 daemon.notice netifd: Network device 'w24G' link is down
Tue Jun 20 09:58:43 2023 kern.info kernel: [ 1846.850466] ath10k_ahb a000000.wifi: mac flush null vif, drop 0 queues 0xffff
Tue Jun 20 09:58:43 2023 kern.warn kernel: [ 1846.889085] ath10k_ahb a000000.wifi: peer-unmap-event: unknown peer id 0
Tue Jun 20 09:58:43 2023 kern.warn kernel: [ 1846.889216] ath10k_ahb a000000.wifi: peer-unmap-event: unknown peer id 0
Tue Jun 20 09:58:43 2023 daemon.notice netifd: Wireless device 'radio0' is now down
Tue Jun 20 09:58:57 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy w24G) --> new PHY
Tue Jun 20 09:58:58 2023 kern.warn kernel: [ 1862.296089] ath10k_ahb a000000.wifi: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
Tue Jun 20 09:58:58 2023 kern.warn kernel: [ 1862.296153] ath10k_ahb a000000.wifi: msdu-desc: 2500 skid: 32
Tue Jun 20 09:58:58 2023 kern.info kernel: [ 1862.332549] ath10k_ahb a000000.wifi: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
Tue Jun 20 09:58:58 2023 kern.info kernel: [ 1862.333432] ath10k_ahb a000000.wifi: wmi print 'free: 53252 iram: 13432 sram: 35752'
Tue Jun 20 09:58:59 2023 kern.info kernel: [ 1862.615653] ath10k_ahb a000000.wifi: rts threshold -1
Tue Jun 20 09:58:59 2023 kern.warn kernel: [ 1862.615876] ath10k_ahb a000000.wifi: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Tue Jun 20 09:58:59 2023 kern.info kernel: [ 1862.622008] br-lan: port 3(w24G) entered blocking state
Tue Jun 20 09:58:59 2023 kern.info kernel: [ 1862.630688] br-lan: port 3(w24G) entered disabled state
Tue Jun 20 09:58:59 2023 kern.info kernel: [ 1862.636128] device w24G entered promiscuous mode
Tue Jun 20 09:58:59 2023 daemon.notice hostapd: w24G: interface state UNINITIALIZED->COUNTRY_UPDATE
Tue Jun 20 09:58:59 2023 daemon.notice hostapd: ACS: Automatic channel selection started, this may take a bit
Tue Jun 20 09:58:59 2023 daemon.notice hostapd: w24G: interface state COUNTRY_UPDATE->ACS
Tue Jun 20 09:58:59 2023 daemon.notice hostapd: w24G: ACS-STARTED
Tue Jun 20 09:59:00 2023 daemon.notice netifd: Wireless device 'radio0' is now up
Tue Jun 20 09:59:09 2023 daemon.notice hostapd: w24G: ACS-COMPLETED freq=2437 channel=6
Tue Jun 20 09:59:09 2023 kern.info kernel: [ 1873.290677] IPv6: ADDRCONF(NETDEV_CHANGE): w24G: link becomes ready
Tue Jun 20 09:59:09 2023 kern.info kernel: [ 1873.292597] br-lan: port 3(w24G) entered blocking state
Tue Jun 20 09:59:09 2023 kern.info kernel: [ 1873.296069] br-lan: port 3(w24G) entered listening state
Tue Jun 20 09:59:09 2023 daemon.notice netifd: Network device 'w24G' link is up
Tue Jun 20 09:59:09 2023 daemon.notice hostapd: w24G: interface state ACS->ENABLED
Tue Jun 20 09:59:09 2023 daemon.notice hostapd: w24G: AP-ENABLED
Tue Jun 20 09:59:18 2023 kern.info kernel: [ 1881.448261] br-lan: port 3(w24G) entered learning state
Tue Jun 20 09:59:26 2023 kern.info kernel: [ 1889.768262] br-lan: port 3(w24G) entered forwarding state
Tue Jun 20 09:59:26 2023 kern.info kernel: [ 1889.768760] br-lan: topology change detected, sending tcn bpdu
Hi all, maybe i should rephrase the question a bit... does anyone have a working 2.4 WiFi on DAP-2610?
Will try to revert to stock firmware to see if any relevant info on hardware status is showing up...
2.4Ghz radio not working, confirmed after reverting back to D-Link v2.01.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.