Asus BE88U login page inaccessible unless I reboot it

[bennor]

@Sash2025, couple of suggestions if you haven't tried them already.
Disconnect all other local network clients from the router except one wired computer, reboot the router, then test to see if the issue persists with all other local clients disconnected from the router. As suggested by @Ripshod above something else might be interfering on the local network.
If, when, you can access the router GUI check to see if you have enabled the filtering option on who can access the GUI (may be called Enable Access Restrictions on the Administration > System page). Could be the IP address/MAC address on the client you are using to access the router has changed and the router is preventing access. Disable the option and see if the issue persists.

 

[Sash2025]

@Sash2025, couple of suggestions if you haven't tried them already.
Disconnect all other local network clients from the router except one wired computer, reboot the router, then test to see if the issue persists with all other local clients disconnected from the router. As suggested by @Ripshod above something else might be interfering on the local network.
If, when, you can access the router GUI check to see if you have enabled the filtering option on who can access the GUI (may be called Enable Access Restrictions on the Administration > System page). Could be the IP address/MAC address on the client you are using to access the router has changed and the router is preventing access. Disable the option and see if the issue persists.

Rebooted router and accessed GUI. Administration > Enable Access Restrictions set to No. Enable SSH was also Lan Only.

 

[Sash2025]

Got this from Chat GPT when I asked it to look at logs. Unsure if right

TL;DR (your root cause)​

This is NOT a memory / conntrack / overload issue
It’s primarily:

WiFi subsystem instability / client deauth spam + ASUS firmware quirks

And possibly contributing to the UI dying.

---

What your log actually shows​

1. This line dominates EVERYTHING:​

WLC_SCB_DEAUTHORIZE error (-30)

This appears hundreds of times

---

What that means​

This is from the Broadcom WiFi driver:

• WLC = Wireless LAN Controller
• SCB_DEAUTHORIZE = client being forcibly disconnected
• error (-30) = failure/invalid state during deauth

Translation:

The router is constantly trying (and failing) to deauthenticate WiFi clients

 

[ColinTaylor]

Are you using a VPN client on your PC?

Got this from Chat GPT when I asked it to look at logs. Unsure if right

The implication from your earlier posts was that you were mainly testing from a wired (ethernet) PC. If that is the case then this is not a wireless issue and the AI response is garbage.

I'd also agree with @Ripshod's idea that this sounds like you have another DHCP server running on your LAN. So when the problem occurs run ipconfig (assuming you're using Windows) and check what IP addresses are being used for the PC and the gateway.

 

[Notconnected]

Um I am not rebooting it now as I know that action itself brings it back. Even if I was willing to do what you ask would that not reset everything?

You should still be able to log into the router at the default IP, it is the admin IP and will still be available.
You could change it though to an IP in the range your router is set to hand out IP's, 50.1 for example.
Did you update the firmware, may be do so, or roll back if this problem was not there before.

 

[Sash2025]

Are you using a VPN client on your PC?


The implication from your earlier posts was that you were mainly testing from a wired (ethernet) PC. If that is the case then this is not a wireless issue and the AI response is garbage.

I'd also agree with @Ripshod's idea that this sounds like you have another DHCP server running on your LAN. So when the problem occurs run ipconfig (assuming you're using Windows) and check what IP addresses are being used for the PC and the gateway.

No VPN clients
Yes Wired PC via CAT 6 to router
Win 11 Pro Machine with Vmware hosting home assistant. Asus IOT with about 8 odd wifi devices, Rest all on Asus 2.4 and 5 G network spread out. Wifi 7 disabled since most devices not supported.

You should still be able to log into the router at the default IP, it is the admin IP and will still be available.
You could change it though to an IP in the range your router is set to hand out IP's, 50.1 for example.
Did you update the firmware, may be do so, or roll back if this problem was not there before.

Firmware is latest and ipconfig was the same previously when it did not work before reboot.
Ethernet adapter Ethernet 4:

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

 

[ColinTaylor]

No VPN clients
Yes Wired PC via CAT 6 to router
Win 11 Pro Machine with Vmware hosting home assistant. Asus IOT with about 8 odd wifi devices, Rest all on Asus 2.4 and 5 G network spread out. Wifi 7 disabled since most devices not supported.


Firmware is latest and ipconfig was the same previously when it did not work before reboot.
Ethernet adapter Ethernet 4:

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

The next thing I would check on the PC (when the problem next happens) is the routing table. Run route print and make sure the default route is correct and that there's an On-Link entry for 192.168.0.0.

 

[Sash2025]

The next thing I would check on the PC (when the problem next happens) is the routing table. Run route print and make sure the default route is correct and that there's an On-Link entry for 192.168.0.0.

Ok will do. How do I do this please?

 

[ColinTaylor]

Ok will do. How do I do this please?

Just run route print from the Command Prompt and post the output here for us to look at.

 

[dave14305]

IPv4 Address. . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

Another test from the Windows Command Prompt would be to test DNS resolution when SSH and HTTP don't seem to work.

nslookup www.asusrouter.com. 192.168.0.1