What's new

RT-AC68P stops giving out DHCP and can't login to Admin GUI randomly

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

mjonis

New Around Here
OK, I've got a:
RT-AC68P router.
It seems to have gotten worse lately with the issue which is:
Devices (not NEW ones, one that have been on and are on my network for some time) will no longer get a DHCP IP from the router. For example, my desktop (I shut it off at night, but it's on every day), suddenly can't get on the network (same with wireless devices like my iPhone if I'm returning home). I'm unable to login to the Admin GUI (the login page comes up but you enter your credentials and it just sits there and eventually times out). I'm using two other routers (different models) from ASUS as Access Points.

If I power cycle the router, all is well again.

It did this like a year ago and only to find out I'd run out of IP's (OK THAT I can understand) as I have my LAN setup as:
10.10.x.x/255.255.0.0 network starting DHCP at: 10.10.1.25 - 10.10.1.250 (originally I'd had it 10.10.1.50 - 10.10.1.150).

Anyway, lately it's been doing this about every 3-4 weeks.

My signature version is: 2.226 Updated : 2021/04/16 02:00
My Firmware version is: 3.0.0.4.385_20632-gfc5326d

Ideally I'd like to figure out what's going on, but when I check the logs, there's nothing really to see that I can tell. For example, it last did this on 4/13/21 sometime between say 9:00 a.m. and 6:00 p .m.

The logs are weird. I say that because it's like:
Feb 9 11:49:06 syslog: WLCEVENTD wlceventd_proc_event(500): eth2: Auth 4C:17:44:3D:E6:93, status: Successful (0)
Feb 9 11:49:06 syslog: WLCEVENTD wlceventd_proc_event(529): eth2: Assoc 4C:17:44:3D:E6:93, status: Successful (0)
May 5 01:05:00 kernel: klogd started: BusyBox v1.25.1 (2020-07-21 13:58:58 CST)
May 5 01:05:00 kernel: Linux version 2.6.36.4brcmarm (root@asus) (gcc version 4.5.3 (Buildroot 2012.02) ) #1 SMP PREEMPT Tue Jul 21 14:08:11 CST 2020
May 5 01:05:00 kernel: CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c53c7f


I'm THINKING the fast forward in time is the router booting up and then getting current date/time from NTP?

IF that's the case, then 4/13 is when it last had issues, I see a bunch of "May 5" stuff right before that, and right before that is 4/5/21 stuff, so that would mean that sometime between 4/5 and 4/13 it had issues (although given my PC daily startup was fine until 4/13 when PC #2 couldn't get DHCP)...



It *seems* symptomatic of when I had Time Warner/Road Runner (I have Verizon FIOS now) where their cable modem/router (this was a LONG time ago) had a hard-coded 6 MAC address or something and the table would fill up and you'd have to power cycle to get rid of old/stale entries.

Is there a way to enable better/debug logging? I suppose I could leave my regular PC on all the time and have it function as a syslog server.

Thanks for any ideas/suggestions.
 
I'm THINKING the fast forward in time is the router booting up and then getting current date/time from NTP?
That is correct.

I suggest that you update the firmware to the current 386 version, 386.41994. Follow that with a factory reset and manually configure it (do not reload a saved backup file).

Your netmask is 255.255.0.0. Do you really need a subnet of 65536 addresses (given your current DHCP pool is only 225 addresses)? If possible go back to the default of 255.255.255.0 because the GUI's network map function doesn't support larger subnets.
 
Similar threads

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top