LED Configuration - 2.4G and 5G LED not working - Snapshot build (Newifi D2)

Installing and Using OpenWrt
1

Hi All,

I've have flashed my main router (Newifi D2) from 21.02.04 build to a custom build (from snapshot) a few weeks back. I only noticed this last week that the 2.4G and 5G LED lights where disabled (not working). Then when I checked the LED Configuration in LUCI, it says that wlan0 and wlan1 are missing interfaces.

image
image707×576 36.8 KB

In the "Devices" list from the "Interface", the list of wifi devices are below that are related to the wifi interfaces.
image
The phy0 and phy1 used to be (i believe) the wlan0 and wlan1 but basing on the selection on the LED Configuration edit screen, I can only select devices that only are only in the Device screen.

What config adjustments should I do to re-enable the LEDs for the 2.4G and 5G?

2

And what about the 3 WiFi interfaces that you blacked-out?

Is there a reason you're ignoring them and not using them?

  • Is this why your WiFi devices say phyx instead of wlanx?
  • Perhaps you should ask the person who made the custom build?
3

Those are SSID's rather than actual interfaces, it's one of my Main SSID and Guest SSID (2.4 and 5G).

I'm the one who did the build, but I'm not sure why it changed from wlanx to phyx.

4

So since youn made the build and know they're phyx...does that work instead?

5

Tried changing it manually via SSH in /etc/config/system but phy0 and phy1 also doesn't work. Even tried changing then a reboot but not working.

6

Do they work in official firmware from the downloads site?

7

I haven't tried using latest official builds yet to test as this is currently my main router. It might take me a while before trying that route to see if the LED settings work since my network is almost 24/7 being used.

8

I've tried using official builds by downloading via the https://firmware-selector.openwrt.org/ and tried the following on my Newifi D2. And I've finally figured out the correct setup to enable the 2.4G and 5G LED of the device. It seems using a SNAPSHOT build will render the default LED config for the mentioned LEDs invalid.

21.02.5 - working with default wlan0 and wlan1 interface names of the wifi devices
22.03.2 - working with default wlan0 and wlan1 interface names of the wifi devices
SNAPSHOT - not working due to default name of the wifi devices has changed from "wlanX" to "phyX-apX", and the default "LED Configuration" still points to the "wlanX" interfaces

So based on the findings, it seems there is a major change in the naming of the wifi interface/devices in the latest MASTER/SNAPSHOT of OpenWRT. See logs below:

Logs from official build 22.03.2

Thu Dec 29 22:26:00 2022 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy wlan0) --> new PHY
Thu Dec 29 22:26:00 2022 kern.info kernel: [  180.123948] br-lan: port 5(wlan0) entered blocking state
Thu Dec 29 22:26:00 2022 kern.info kernel: [  180.129294] br-lan: port 5(wlan0) entered disabled state
Thu Dec 29 22:26:00 2022 kern.info kernel: [  180.135581] device wlan0 entered promiscuous mode
Thu Dec 29 22:26:00 2022 kern.info kernel: [  180.155101] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Thu Dec 29 22:26:00 2022 kern.info kernel: [  180.162020] br-lan: port 5(wlan0) entered blocking state
Thu Dec 29 22:26:00 2022 kern.info kernel: [  180.167391] br-lan: port 5(wlan0) entered forwarding state
Thu Dec 29 22:26:00 2022 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->ENABLED
Thu Dec 29 22:26:00 2022 daemon.notice hostapd: wlan0: AP-ENABLED
Thu Dec 29 22:26:00 2022 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy1.conf (phy wlan1) --> new PHY
Thu Dec 29 22:26:00 2022 kern.info kernel: [  180.681676] br-lan: port 6(wlan1) entered blocking state
Thu Dec 29 22:26:00 2022 kern.info kernel: [  180.686995] br-lan: port 6(wlan1) entered disabled state
Thu Dec 29 22:26:00 2022 kern.info kernel: [  180.692816] device wlan1 entered promiscuous mode
Thu Dec 29 22:26:00 2022 kern.info kernel: [  180.697947] br-lan: port 6(wlan1) entered blocking state
Thu Dec 29 22:26:00 2022 kern.info kernel: [  180.703466] br-lan: port 6(wlan1) entered forwarding state
Thu Dec 29 22:26:00 2022 daemon.notice hostapd: wlan1: interface state UNINITIALIZED->HT_SCAN
Thu Dec 29 22:26:01 2022 kern.info kernel: [  181.171675] br-lan: port 6(wlan1) entered disabled state
Thu Dec 29 22:26:01 2022 daemon.notice netifd: Wireless device 'radio0' is now up
Thu Dec 29 22:26:01 2022 daemon.notice netifd: Network device 'wlan0' link is up
Thu Dec 29 22:26:01 2022 kern.info kernel: [  181.719409] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Thu Dec 29 22:26:01 2022 kern.info kernel: [  181.726131] br-lan: port 6(wlan1) entered blocking state
Thu Dec 29 22:26:01 2022 kern.info kernel: [  181.731737] br-lan: port 6(wlan1) entered forwarding state
Thu Dec 29 22:26:01 2022 daemon.notice hostapd: wlan1: interface state HT_SCAN->ENABLED
Thu Dec 29 22:26:01 2022 daemon.notice hostapd: wlan1: AP-ENABLED
Thu Dec 29 22:26:01 2022 daemon.notice netifd: Wireless device 'radio1' is now up
Thu Dec 29 22:26:01 2022 daemon.notice netifd: Network device 'wlan1' link is up

Logs from official SNAPSHOT build (as of Dec 29, 2022 10pm UTC/GMT)

Thu Dec 29 22:15:14 2022 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy phy0-ap0) --> new PHY
Thu Dec 29 22:15:14 2022 kern.info kernel: [  186.468608] br-lan: port 5(phy0-ap0) entered blocking state
Thu Dec 29 22:15:14 2022 kern.info kernel: [  186.474220] br-lan: port 5(phy0-ap0) entered disabled state
Thu Dec 29 22:15:14 2022 kern.info kernel: [  186.481035] device phy0-ap0 entered promiscuous mode
Thu Dec 29 22:15:14 2022 kern.info kernel: [  186.496161] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-ap0: link becomes ready
Thu Dec 29 22:15:14 2022 kern.info kernel: [  186.503484] br-lan: port 5(phy0-ap0) entered blocking state
Thu Dec 29 22:15:14 2022 kern.info kernel: [  186.509421] br-lan: port 5(phy0-ap0) entered forwarding state
Thu Dec 29 22:15:14 2022 daemon.notice hostapd: phy0-ap0: interface state UNINITIALIZED->ENABLED
Thu Dec 29 22:15:14 2022 daemon.notice hostapd: phy0-ap0: AP-ENABLED
Thu Dec 29 22:15:14 2022 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy1.conf (phy phy1-ap0) --> new PHY
Thu Dec 29 22:15:15 2022 kern.info kernel: [  187.008024] br-lan: port 6(phy1-ap0) entered blocking state
Thu Dec 29 22:15:15 2022 kern.info kernel: [  187.013603] br-lan: port 6(phy1-ap0) entered disabled state
Thu Dec 29 22:15:15 2022 kern.info kernel: [  187.019801] device phy1-ap0 entered promiscuous mode
Thu Dec 29 22:15:15 2022 kern.info kernel: [  187.025217] br-lan: port 6(phy1-ap0) entered blocking state
Thu Dec 29 22:15:15 2022 kern.info kernel: [  187.031045] br-lan: port 6(phy1-ap0) entered forwarding state
Thu Dec 29 22:15:15 2022 daemon.notice hostapd: phy1-ap0: interface state UNINITIALIZED->HT_SCAN
Thu Dec 29 22:15:15 2022 kern.info kernel: [  187.497976] br-lan: port 6(phy1-ap0) entered disabled state
Thu Dec 29 22:15:15 2022 daemon.notice netifd: Wireless device 'radio0' is now up
Thu Dec 29 22:15:15 2022 daemon.notice netifd: Network device 'phy0-ap0' link is up
Thu Dec 29 22:15:16 2022 kern.info kernel: [  188.045704] IPv6: ADDRCONF(NETDEV_CHANGE): phy1-ap0: link becomes ready
Thu Dec 29 22:15:16 2022 kern.info kernel: [  188.052739] br-lan: port 6(phy1-ap0) entered blocking state
Thu Dec 29 22:15:16 2022 kern.info kernel: [  188.058524] br-lan: port 6(phy1-ap0) entered forwarding state
Thu Dec 29 22:15:16 2022 daemon.notice hostapd: phy1-ap0: interface state HT_SCAN->ENABLED
Thu Dec 29 22:15:16 2022 daemon.notice hostapd: phy1-ap0: AP-ENABLED
Thu Dec 29 22:15:16 2022 daemon.notice netifd: Wireless device 'radio1' is now up
Thu Dec 29 22:15:16 2022 daemon.notice netifd: Network device 'phy1-ap0' link is up