I am currently on my home-network where I am trying to recreate the problem, but without success. With the same config the stick works perfectly fine for almost 3 days now. There is something specific to the hotel environment that triggers the problem roughly every 24hrs.
Any further suggestions what to enable before the problem reoccurs and what to collect
when the issue happens?
Thanks!
Hello All!
I am back at the location where I can reproduce the issue. I currently have left the device in the broken state. From logread, this is when it happened:
Thu Aug 14 09:32:31 2025 daemon.notice netifd: WAN (18017): udhcpc: sending renew to server 10.0.10.1
Thu Aug 14 09:32:31 2025 daemon.notice netifd: WAN (18017): udhcpc: lease of 10.0.9.60 obtained from 10.0.10.1, lease time 1800
Thu Aug 14 09:47:31 2025 daemon.notice netifd: WAN (18017): udhcpc: sending renew to server 10.0.10.1
Thu Aug 14 09:47:31 2025 daemon.notice netifd: WAN (18017): udhcpc: lease of 10.0.9.60 obtained from 10.0.10.1, lease time 1800
Thu Aug 14 09:47:32 2025 user.notice firewall: Reloading firewall due to ifupdate of WAN (phy2-sta0)
Thu Aug 14 10:02:32 2025 daemon.notice netifd: WAN (18017): udhcpc: sending renew to server 10.0.10.1
Thu Aug 14 10:02:32 2025 daemon.notice netifd: WAN (18017): udhcpc: lease of 10.0.9.60 obtained from 10.0.10.1, lease time 1800
Thu Aug 14 10:17:18 2025 daemon.notice netifd: Network device 'phy2-sta0' link is down
Thu Aug 14 10:17:18 2025 daemon.notice netifd: Interface 'WAN' has link connectivity loss
Thu Aug 14 10:17:18 2025 kern.info kernel: [111012.396945] phy2-sta0: deauthenticated from 90:0a:00:05:3a:c7 (Reason: 3=DEAUTH_LEAVING)
Thu Aug 14 10:17:18 2025 daemon.notice netifd: WAN (18017): udhcpc: received SIGTERM
Thu Aug 14 10:17:18 2025 daemon.notice netifd: WAN (18017): udhcpc: unicasting a release of 10.0.9.60 to 10.0.10.1
Thu Aug 14 10:17:18 2025 daemon.notice netifd: WAN (18017): udhcpc: sending release
Thu Aug 14 10:17:18 2025 daemon.notice netifd: WAN (18017): udhcpc: entering released state
Thu Aug 14 10:17:18 2025 daemon.notice netifd: WAN (18017): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "WAN" } (Permission denied)
Thu Aug 14 10:17:18 2025 daemon.notice netifd: Interface 'WAN' is now down
Please, advise what to collect before i reboot the device to recover.
Performing an SSID scan does not show any output just spinning wheel… Thanks!
Update: The UI is also extremely slow and fails to load as well:
The process did not produce any response