Posted: Tue Apr 14, 2020 17:22 Post subject: r7800 web interface response is non-existent
In the past had been running the old Kong r7800 build with no issues. After Kong switched teams over to OpenWRT I started experimenting with OpenWRT as Access Points only on one EA8500 and the R7800. I’ve always kept one EA8500 on dd-wrt for our VPN service. Fast forward to when mrjcd advised us that BS did a makeover on the EA8500 builds shortly thereafter I return my second EA8500 to dd-wrt and never looked back. I also tried to do the same for the R7800 but the web interface is useless after the set password page slowly appears. Accessing and changing tabs using a browser is basically impossible for the R7800, so I sidelined a few months ago.
Yesterday I figured had some extra time with the Covid-19 lockdown so I dug out the r7800 and wanted to see if I could get dd-wrt functioning again. It takes an extended period before the web interface appears for the password setup after flash or reset to enter the entering username/password. Once the username/password is applied the web interface is basically unworkable.
Response times on the R7800 are normal with Stock, OpenWRT and Voxel's firmwares. I’ve erased the nvram, reloaded the FW from tftp. I tried MS Edge, FireFox (my default) and a portable version of PaleMoon and the result is the same with dd-wrt even after clearing ALL browser history, cache and cookies. I’ve even tried private mode in FF. The only time dd-wrt seems to run sort of normal is if I install an older build like r38150M but after moving up the current dd-wrt release(s) it makes the device return to a snail pace making it unusable by the web interface. If I select any tab it takes 60 to 90 seconds to open the next tab if the tab opens at all. I could telnet in with no problem but not sure what to look for once in. Anyone see anything like this before? Thanks in advance.
Joined: 18 Mar 2014 Posts: 12877 Location: Netherlands
Posted: Tue Apr 14, 2020 17:50 Post subject:
That is a really strange problem, you did all the right things, yes some browsers (Chrome) are sometimes acting up, yes sometimes clearing the nvram is necessary (nvram erase && reboot from CLI) but you already did that so I am also stumped.
Sometimes if you have bad flash chips the router can behave erratically and Voxel and stock will check for bad blocks but OpenWRT does not so you would expect that OpenWRT also had problems but it has not.
So the only advice I can give (which you actually already have done), from CLI:
nvram erase && reboot
upgrade via internet explorer (yes I know)
after setting password again do from CLI: nvram erase && reboot
Joined: 16 Nov 2015 Posts: 6435 Location: UK, London, just across the river..
Posted: Tue Apr 14, 2020 18:00 Post subject:
hmmm yep have something similar with my R7000, since
i experimented with a block Countries by country code script, it became sluggish, it takes 4 min to boot even when i erased nvram....even worst since 42054 it never boots normally even after 10 min, unless there is no WAN request, and takes min 4-5 min to boot, GUI is snail mode too...tried anything tftp back to stock, reset, manually rebuild step by step and so...
now it works with that WAN event gimmick...only, you can see what i run on it in my sig
apart of that weirdo, i know Voxel FW can screw CFE
but im not that acquainted to fix it...nor im entirely sure what cause it...on R7800
my R7800 is snappy and works well i even have second one as a spare to play with it..
i mostly use cli flash... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55779 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
@ AlozarosThanks for the reply back. I think you’re on to something there. Early on when I first got the r7800 I used the older Voxel and Stock and had no problem returning to dd-wrt. Let’s say 3 ~ 4 months ago I tried both the newer Voxel and Stock FW and that’s when I noticed the issues with dd-wrt.
Just thinking out loud here, since Voxel is just a spin-off of the Stock FW perhaps the new NG stock version could have been the offender?? IIRC when I flashed a few months back with the stock fw and it was a labeled "beta". I guess no more dd-wrt for the r7800
(the current firmware needs to boot a little longer, BS has raised a hardware timeout / and after changing the configuration (save + apply WLAN) it also takes a little before all services are restarted, the WebIF also hangs 60sec)
Usually when all services are started, the current WebIF is fucking fast, switching between tabs may take ~0.5 seconds
you can also see which bootloader is on it now.
The "U-Boot" version was always the same / ancient .. didn't know that it was updated
The last attempts for the evening were tftp’ing up current dd-wrt build and same result, its unusable. So last move for tonight was sending up Kong’s r33010M from 09 August 2017 and it working perfectly with regards to response times.
Its not connected to anything at the moment but it completely accessible from any web browser and very quick response time. Tomorrow will dig thought my archives of old Kong builds and see how from I could advance. Looks like next build up will be r38150M.
Joined: 21 Jan 2017 Posts: 1783 Location: Illinois Moderator
Posted: Thu Apr 16, 2020 5:31 Post subject:
05dyna wrote:
The last attempts for the evening were tftp’ing up current dd-wrt build and same result, its unusable. So last move for tonight was sending up Kong’s r33010M from 09 August 2017 and it working perfectly with regards to response times.
Its not connected to anything at the moment but it completely accessible from any web browser and very quick response time. Tomorrow will dig thought my archives of old Kong builds and see how from I could advance. Looks like next build up will be r38150M.
At some point didn't he move to K4 and then back to k3.18 and then back to k4? Just watch the NVRAM...I know somewhere in that transition you had to erase NVRAM to make it work right...that was 2 years ago now....MRJCD might know by looking at his repository/secret stash of wealth... _________________ FORUM RULES
Joined: 15 May 2013 Posts: 243 Location: The Nederlands
Posted: Thu Apr 16, 2020 9:12 Post subject:
Something I noticed over the years. Everyone is always talking about issues with the webinterface and I never had any issues. Well when I had to reset NVRAM I found the same issues as people had always said existed.
So why did I never have them before? Well very likely had to do with me using 192.168.0.1 rather than 192.168.1.1. This at least was my conclusion back then. I had a lot of issues until I changed the routers ip.
You can try but it really depends on your needs. _________________ Hi
2x Netgear R7800
Something I noticed over the years. Everyone is always talking about issues with the webinterface and I never had any issues. Well when I had to reset NVRAM I found the same issues as people had always said existed.
So why did I never have them before? Well very likely had to do with me using 192.168.0.1 rather than 192.168.1.1. This at least was my conclusion back then. I had a lot of issues until I changed the routers ip.
You can try but it really depends on your needs.
you may have a point
I have never had issues with the webif on any of my routers --- then again, I have NEVER used 192.168.1.1 or anything in the 192.168.1.x subnet
also NO problem using Chromium from the Debian OS
and I use Chrome from the WIN10 for installs lots of times and it has never caused me any problems like many report
Thanks but can’t view at this time, one of the block list in DNSBL preventing me from viewing. Will whitelist later and look then..
msoengineer wrote:
At some point didn't he move to K4 and then back to k3.18 and then back to k4?
I may be wrong but I think Kong was actually supporting both at some point. Don’t remember where it crossed over but here’s the latest.
I went one by one thru my Kong archive. From r33010M to r38150M and it was OK but going from there to r39575M crashed the router so started back at r33010M then installed the following builds in the following sequence, probably not the preferred method but was up and running with dd-wrt and the response times were as they should be, no hesitation whatsoever.
and all was good at r40270M but I gambled and went for broke and installed r42910 and if you guessed r42910 hosed it you’d be correct. Later today will return to old Kong build r40270M and put it back in service to see if it remains stable.
ps
for the record changed the local net address to 172.x.x.x and it made no difference. looks like it might be Kong of bust for my r7800
