I'm getting reboots every few hours with this build on my R8500. If I had to guess, I'd say it was NVRAM filling up. I'm sitting well above 55KB (max 64KB). I need to try a full reset and rebuild from scratch to see if maybe I did something initially that got it SO high.
I didn't come across the issue you did upgrading to Kong 28600M. It's been stable for more than 24 hours. I did restore factory defaults (via GUI) when I upgraded. I will install the latest Kong build later today. He mentioned there are updated drivers included for the R8500.
I can see that Kong had also released a new dd-wrt.v24-K3_AC_ARM_R8X00.bin on 31st.
For me, I understand that the X made that .bin good for both R8000 and R8500.
So what is the advantage to use the STD as you advise instead of the R8X00?
R8000/R8500 have dedicated arm cores for the radios and therefore require a firmware that is uploaded to the arm core at boot time. Therefore the R8x build comes with a firmware and the build is larger.
Still experiencing VAP instability on 2.4ghz ... Clients cannot connect ... Only way to fix is delete and recreate the VAP followed by reboot
In <28600 build I noticed a problem where my physical AP did not broadcast, VAP was fine for both radios.
Right now I have a guest setup for both 2.4/5G and it is working fine, not tested without a radio schedule though. I setup radio schedules for both radios on my router.
I'm getting reboots every few hours with this build on my R8500. If I had to guess, I'd say it was NVRAM filling up. I'm sitting well above 55KB (max 64KB). I need to try a full reset and rebuild from scratch to see if maybe I did something initially that got it SO high.
I didn't come across the issue you did upgrading to Kong 28600M. It's been stable for more than 24 hours. I did restore factory defaults (via GUI) when I upgraded. I will install the latest Kong build later today. He mentioned there are updated drivers included for the R8500.
Indeed. The previous (12/31) build got stable as soon as I cleaned up NVRAM with this command:
That (for me) brings usage down to about 50KB and things stayed quite stable. I updated to the new R8500 driver build (1/1/16) this morning (and then ran the aforementioned command). Things have been stable for 6 hours now.
Clearly I need to clean up my NVRAM with a factory reset and a manual configuration again.
I seem to be having a lot of issues with access the WebGui with the latest build. I can bin the device, and get to the shell via telnet, but not the UI.
Router: R8000
Build: r28600
Noticed a new version on 12/31 and then on 1/1 .. have tried them both.
Also seems to have an issue with getting a WAN address from my satellite modem (but that could be a separate issue).
If I can ever get back in I will try to flash DOWN to the the previous build. But its not looking good.
I seem to be having a lot of issues with access the WebGui with the latest build. I can bin the device, and get to the shell via telnet, but not the UI.
Router: R8000
Build: r28600
Noticed a new version on 12/31 and then on 1/1 .. have tried them both.
Also seems to have an issue with getting a WAN address from my satellite modem (but that could be a separate issue).
If I can ever get back in I will try to flash DOWN to the the previous build. But its not looking good.
Roy
Try a reboot. I experienced the same issue and this has worked for me.
Still experiencing VAP instability on 2.4ghz ... Clients cannot connect ... Only way to fix is delete and recreate the VAP followed by reboot
In <28600 build I noticed a problem where my physical AP did not broadcast, VAP was fine for both radios.
Right now I have a guest setup for both 2.4/5G and it is working fine, not tested without a radio schedule though. I setup radio schedules for both radios on my router.
Do you have more than one VAP per radio?
No VAP on 5G, two VAPs on 2.4G (a guest (isolated subnet) and another hidden one) ... also VLAN tagging between two r7000 ... both r7000s experience instability with 2.4g VAP (during config changes, upgrades, etc)
Try a reboot. I experienced the same issue and this has worked for me.
Have done that. Sometimes it takes 4 or 5 reboots and I can get in. Once I am in its good until I reboot again. Then I have to start over until it lets me in.
Still experiencing VAP instability on 2.4ghz ... Clients cannot connect ... Only way to fix is delete and recreate the VAP followed by reboot
In <28600 build I noticed a problem where my physical AP did not broadcast, VAP was fine for both radios.
Right now I have a guest setup for both 2.4/5G and it is working fine, not tested without a radio schedule though. I setup radio schedules for both radios on my router.
Do you have more than one VAP per radio?
No VAP on 5G, two VAPs on 2.4G (a guest (isolated subnet) and another hidden one) ... also VLAN tagging between two r7000 ... both r7000s experience instability with 2.4g VAP (during config changes, upgrades, etc)
Did you reset? If you had more then one VAP, then your vap macs were incorrect and they will be only corrected if you reset your config.
I did the aforementioned factory/30-30-30 reset on my R8500 and rebuilt my configuration from scratch in an effort to get my NVRAM under control (from both a size and data perspective).
Even my freshly-reset R8500 uses 48KB of its 64KB of NVRAM with DD-WRT. That seems about 10-12KB higher than the other DD-WRT routers I have, but perhaps that has to do with the configs for the 3rd radio? Adding in various parameters with a dozen-or-so static leases and the same amount of port forwards gets me back up to 55-58KB used. Is that normal?