DHCP issues on RT-BE88U

[gameleon]

Ever since the most recent stock firmware update of the BE88U (3.0.0.6.102_37094, November 25, 2024) I'm having DHCP issues on a few of my IoT devices (Example used here is a Philips TAR8805 radio).

The devices connect to the network but aren't able to obtain an IP address through DHCP. They end up with a 0.0.0.0 or 169.254.* IP address.
Assigning a manual IP configuration to the devices works fine and the device will connect properly.

(For some reason the device will still show up as DHCP instead of Static in the client list, but this seems to be mostly a display issue. The statically assigned IP works fine)

The devices are connected to the IoT SSID. This network is 2.4Ghz only with WPA2-Personal security, with no other wireless filers set.
I tested with my primary SSID but it had the same issue for the affected devices.
Connecting the devices to another wifi network (such as my phone hotspot) works fine. A bunch of other IoT devices connect perfectly fine using DHCP too. I cannot determine a common denominator between the devices having DHCP issues.

The system log on the Asus shows only these entries for the devices:

wlceventd: wlceventd_proc_event(685): wl0.2: Auth MAC_OMITTED, status: Successful (0), rssi:-59
kernel: SBF: dhd0: INIT [MAC_OMITTED] ID 65535 BFW 65535 THRSH 2048
wlceventd: wlceventd_proc_event(722): wl0.2: Assoc MAC_OMITTED, status: Successful (0), rssi:-59

Extra info:
* A factory reset of both the router and devices didn't help.
* This router is the only node/ap in the wireless network.

Are there any known DHCP related issues/changes with the latest firmware?

 

[sercontri]

It happens to me, among other things, that they are connected and do not appear connected to me. I also have different devices that don't connect no matter how hard I try. I put another router with the same configuration and these devices connect without problems.

 

[Digilog]

(For some reason the device will still show up as DHCP instead of Static in the client list, but this seems to be mostly a display issue. The statically assigned IP works fine)

There could be a couple of ways this could be happening. One would be statically assigning an address in the DHCP pool. Or it could be the list you are seeing is the wireless network clients regardless if they are static or DHCP.

But to be fair, download the firmware, disconnect everything from the router and flash the router again. Because technically, the router should not be running a network wile its getting flashed.