Wi-Fi ping spikes every 10 seconds.

The router shows strange behavior that may be related to DHCP, DNS, or client state handling.

Devices often cannot connect to the router even when the Wi-Fi password is correct. Restarting the affected devices usually does not help. The issue is resolved only after rebooting the router.

One Tuya-like IoT device shows a specific case: if it is connected to the router and the router is rebooted, the IoT device can no longer reconnect until the IoT device itself is restarted.

Most other affected devices are iOS/macOS devices. For example, if a device is connected to the router and then its network settings are reset, it can no longer connect to the router, even though the Wi-Fi network is still visible in the list.

The same issue can happen after resetting network settings on an iPhone, reconnecting to Wi-Fi, and then changing Private Wi-Fi Address from Rotate to Fixed.

Cloud Gateway Ultra also shows that even when the affected device is not actually connected to Wi-Fi, the router still displays one or two phantom devices in the list of connected clients. These devices appear to have failed to connect in reality.

It looks like the router keeps some stale client state and then does not allow the same device to reconnect. Rebooting the router clears the issue.

Steps to reproduce:

1. Connect an iOS/macOS device to the router via Wi-Fi.

2. Reset network settings on the device.

3. Try to reconnect to the same Wi-Fi network.

4. Alternatively, on iPhone, reconnect to Wi-Fi and change Private Wi-Fi Address from Rotate to Fixed.

5. Observe whether the device can connect.

6. Check the connected clients list in Cloud Gateway Ultra.