Posted: Wed Dec 12, 2018 6:40 Post subject: After reset and update to Kong latest, Wifi is very unstable
I usually only upgrade my Netgear R7000 once or twice every year. My last install was from May and was super stable and working perfectly even 100 days without reboot. I did a reset and flashed Kong's latest (3 december) and are having very weird issues regarding wifi. Every now and then the speed (when doing speedtest) is reduced to 0.5 Mbit/s. However if I turn off and on the wifi on the client (phone for example) I got my 100 Mbit/s back again, for a little while. Mind you that I would still have a "Excellent" connection to the network, its just the speed that is reduced.
It seems to me that wifi has gotten very unstable and maybe more specifically, the radios.
Is this the famous VAP bug I have encountered? I have read a little about it but I don't understand its consequences.
Joined: 18 Mar 2014 Posts: 12840 Location: Netherlands
Posted: Wed Dec 12, 2018 9:07 Post subject:
Have you erased NVRAM and put settings in manually?
The VAP bug only has an effect on a VAP besides Kong has gone back to different drivers in the 37900 build which should be better.
in the build thread there is no one else reporting this (yet, which does not mean it is not real and maybe a bug ) _________________ Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399 Install guide R7800/XR500:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614 Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
Have you erased NVRAM and put settings in manually?
The VAP bug only has an effect on a VAP besides Kong has gone back to different drivers in the 37900 build which should be better.
in the build thread there is no one else reporting this (yet, which does not mean it is not real and maybe a bug )
Alright, no I just used the Reset option when updating firmware in the UI. I will do a NVRAM reset tonight and try again and report back.
@Kong thanks for this, I tried both not long ago and both were resetting to default.
Correct me if I am wrong but does "erase nvram" not erases the nvram partition?
Which although resets but is not safe to use on all routers.
And what does "nvram erase" do? Is it just iterating through all the nvram parameters and set them to ""?
Is this safe to use on all routers?
Just curious
How did you verify, that nvram was erased?
If you call erase nvram then nvram mtd gets erased, but on reboot or any other action nvram is saved to mtd from ram. Thus unless you power off via button right after you called erase nvram you have not cleared anything. nvram erase however clears nvram in ram and then writes to flash. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
root@R6400v2:~# erase nvram
Flash is NAND
erase[1572864]
root@R6400v2:~# reboot
On reboot my settings where all gone and the router starts with asking for username/password, so that leds me to the conclusion that nvram was erased, but I did not check all nvram parameters.
root@R6400v2:~# erase nvram
Flash is NAND
erase[1572864]
root@R6400v2:~# reboot
On reboot my settings where all gone and the router starts with asking for username/password, so that leds me to the conclusion that nvram was erased, but I did not check all nvram parameters.
But I will do and advise to do "nvram erase" in the future.
Thanks again for all your work.
The only thing with 'nvram erase' it will not show --
Flash is NAND
erase[xxxxxx]
but after reboot it should be clean so might as well just do 'nvram erase && reboot'
root@R6400v2:~# erase nvram
Flash is NAND
erase[1572864]
root@R6400v2:~# reboot
On reboot my settings where all gone and the router starts with asking for username/password, so that leds me to the conclusion that nvram was erased, but I did not check all nvram parameters.
No only some of your settings where gone, the ones that don't get read very often. In RAM there is a certain amount of reserved space for nvram vars/keys, when reads/writes occur, they get cached and flushed out when a commit is called, e.g. reboot now calls a commit. That's also the reason why you have to call a commit to make a setting permananent:-) _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Joined: 16 Nov 2015 Posts: 6414 Location: UK, London, just across the river..
Posted: Thu Dec 13, 2018 0:10 Post subject:
Kong is it on all the routers or only those you support?
thanks _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 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 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 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