cancel
Showing results for 
Search instead for 
Did you mean: 

Zyxel NR5103E stops working till reboot

Hello1024
Regular

I'm having trouble with my Zyxel NR5103E.   Obviously it was fine in the 14 day return period, then started playing up immediately afterwards!

 

Each time, the symptoms seem a bit different, but here are the sorts of things I've been seeing:

* Everything continues to work fine, except DNS lookups all time out.   All clients (wifi or wired) can't lookup anything over DNS, but pinging the internet or using a third party DNS server works fine.    Resolved by a reboot.

*  Wifi won't let new clients connect.    Wifi and wired is working fine for anything connected to it, but any new device tries to connect, it cannot.   The wifi still is broadcasting beacon packets, but does not reply to auth or association requests, on either the main or guest wifi.   If a client disconnects or tries to migrate from 2.4G to 5G or vice versa, then that client cannot reconnect either.  Resolved by a reboot.

* Wifi stops working entirely (but keeps sending beacon packets), while wired works fine.   Just stops sending out any packets.   Resolved by a reboot.

* The router works fine, but the admin panel gets really really slow.   Like 30 seconds to load a page slow.

* I sometimes see insane packet queueing - like ping times going up to 15,000 milliseconds.   Not sure if this is happening in the router or somewhere on Threes network, but it again seems to be resolved by a reboot.

 

I'm seeing issues about once or twice a day.   I have about 20 wifi devices connected and about 4 on wired - which should be comfortably below the 64 device limit.

 

It feels like the system might be running out of RAM or something that might explain all these issues.   Haven't managed to log in to a root shell to properly debug - hopefully some engineer at Three can log in at a root shell and knows how to use kgdb to debug a system that has gotten in a stuck state.

1 REPLY 1
Spud
Involved

I agree 24 connected devices shouldn't be excessive. Could you turn off wireless on the NR5103E and connect just a spare router by ethernet? Use the spare router to connect your devices wired and wirelessly. If the NR5103E has a bridge mode then use that, otherwise a bit of double NATting shouldn't hurt too much while you test.

Hopefully that will identify if the NR5103E has a problem and you can get it replaced.