Happy Holliday to all, R7000 is router top of a line right now, but it has minor issues on wifi chipset if your router already was installed ddwrt then you can flash r7000_cfe_upgrade.bin to get full feater and improver wifi.
code:
dd if=/tmp/mnt/sda1/r7000_cfe_upgrade.bin of=/dev/mtdblock0
warning: do know how to flash and upgrade cfe otherwise stay away from it.
pros: no more issues on wifi, enjoin test all ddwrt fw or any tomato...xvortex.
cons: from installed ddwrt ready, do know how to flash.
note:
*cfe from xvortex.
*nvram vars from most collection routers.
*30 minutes assembly and put all together.
Happy and enjoin the best router in Holliday season. and do not forget thanks to Kong made all thing possible.
What is the advantage of flashing r7000_cfe_upgrade.bin?
What problem does it solve? Just curious before taking the risk.
So since i have disabled the radio time restrictions the router has not crashed and has been running well.
I have noticed though from time to time and this morning i could not connect to the 5Ghz band, i could see the SSID on my client devices but as soon as i attempted to connect it just kept retrying and then eventually "authentication error" occurred. Turned off the router and back on and i could then connect successfully.
Unfortunately this did not work. When i checked at 8:10AM this morning the WiFi was off on both 2.4 and 5 Ghz bands. I could not connect to my OpenVPN server from my mobile phone. I then switched on my PC (connected via ethernet) and my IP was a 169.** IP address, completely different to the IP subnet i'm using. Could not access the DD-WRT config page consequently.
I had to switch off the modem and turn back on. Once again everything is now fine until it reoccurs tomorrow. Either the Radio scheduler is causing the issue or there may be some sort of bug? causing the router to become inaccessible after a period of time.
Anyone else having this issue? I think i will revert to an earlier Kong release and see how it goes.
Use the same Con Job and reboot and test. And if doesn't work, I have one more up my sleeve.
I ended up creating two scripts, one to turn off WiFi and one to turn on WiFi and used cron jobs to schedule the execution of these.
The WiFi Off script uses startservice radio_off -f whilst the WiFi on script uses startservice radio_on -f. These commands work fine when executed within Administration>Commands in the DD WRT config page (Wifi turns off and turns on)
With the cron jobs the WiFI turned off successfully as per cron schedule at 11PM. When i woke up this morning the WiFi had not turned back on, ethernet connections were also lost. So this is the exact same issue as when using the Radio Time Restrictions method (i wonder if this used the same commands as i manually configured to turn on/off the radios?)
In conclusion the router seems to crash at some stage during the next 9 hours after the WiFI is turned off by the cron job at 11PM. The issue doesn't happen immediately after the WiFI is off so no idea whats happening here.
