Posted: Fri Jul 18, 2014 9:53 Post subject: Kong R7000 Configuration Best Practices or Working Solutions
The below thread contains best practices and working solutions for the KONG R7000. Thanks for all the time put into this thread by slider mike, RjG, and many others.
NO QUESTIONS PLEASE
OrNow that the main R7000 thread is closed, how about consolidating the working solutions for configuration in one short thread? This could address WIFI configuration, ddup, privoxy, optware, NAS, IPV6 and RjG/Frater's recovery script?
This would be a short thread with cleaned up/updated solutions
Last edited by ghengis5 on Wed Nov 01, 2017 23:26; edited 3 times in total
**last updated October 30 2016** **as of Feb 2015** BrainSlayer & Kong now have a newer/working Broadcom driver that corrects the issue many users experienced with random router reboots due to certain 2.4ghz clients.
BS builds are all labeled "beta" so your a tester if you install it. Report your findings in the forums but do not complain about free beta software.
Kong builds are personal test builds (also referred to as PTB) so again please report your findings in the forums but do not complain about free beta software.
**WDS MAC BRICKING** :
routers are recoverable through the serial interface. The WDS bricking problem has been known about for months, but was not widely advertised. A trouble ticket was opened in TRAC (a development and bug tracking system), but was closed with no resolution. If you must have WDS then don't use any firmware newer than 25974 which uses older Broadcom drivers.
With the newer firmware Kong has noted the need to do a command line nvram erase to ensure a full reset to default for proper router operations on all Netgear routers.
The default var init behavior in dd-wrt is to only initialize vars with defaults, if they do not exist. And since some vars on several units need to be protected they will not even be cleared with factory defaults from webif.
Over Clock router cpu (thanks to Magnetron1.1)
nvram get clkfreq (get current clock rate)
nvram set clkfreq=1200,800 (OC cpu/ram stock)
nvram commit && reboot (write change & reboot)
Changing ram speeds to anything other than 800 appears to default the ram to 400. CPU OC is dependent upon you hardware.
Some get 1400/800 stable, some 1200/800.
Stock is 1000/800.
OC at your own risk.
Transmission on R7000 - how to (thanks to ddaniel51)
First you load the firmware build with BT included.
Then mount a usb drive to /opt.
Go to Services/NAS, enable Transmission, set the path to /opt/transmission, Save, Apply.
Open a browser, go to 192.168.1.1:9091 (router ip address if not default) to access the transmission GUI.
Search on the web for transmission tutorials. You'll find a bunch to choose from.
^^^ dd-wrt to stock firmware ^^^
(from Kongs read me)
To go back to netgear just flash netgear firmware from my build. I implemented this method and this is not always supported for other vendors.
^^^ Reset to default via GUI ^^^
For a reset just use the webif Administration->Factory defaults.
^^^ Reset to default via telnet ^^^
mtd -r erase nvram (this will reset & reboot it)
^^^ clear admin password via command line ^^^
By the way if you don't want to remember the cryptic password you can just set an empty password before flashing, at least this works when flashing back to netgear firmware you can then login without password.
nvram set http_passwd=""
^^^ restart gui interface from command line ^^^
HMM I see transmission guide in OP states to put it in /OPT partition, but mine has been running from the /JFFS one, since thats what the browser gui had it set to standard, would that be lead to any issues?
Rather than just delete my previous post which didn't belong here, I thought I'd share a working solution that is working for me...
I believe I may have found a working solution (or at least partial work-around) to the reboot problem for those of us that have reboots with NEWD versions after 24345. After making the following changes, I've not gotten any reboots on 24800. Interestingly, it appears that disabling WMM might be the major factor since when I re-enable WMM, I get a reboot after just a few hours. With the following settings however, I've gone 7 days with no reboots (so far) which is longer than any previous attempt. Maybe these will help:
On Wireless main tab:
- Disabled TurboQAM (I was already on 20Mhz width)
On WL0 and WL1 Advanced tab:
- Set Beacon Interval to 200
- Set DTIM interval to 5
- Set shortslot override to LONG
- Disabled WMM support
- If you are running QOS: disable that too
As stated above, these are the settings I'm running but it is possible that just disabling WMM would do the trick for many of us having reboots. Worth a try as others have reported at least limited success. You can leave feedback in the other thread: specific to the cause for reboots.
Last edited by mchaney on Tue Aug 19, 2014 18:49; edited 5 times in total
Summary of Poketix's post:
1. Use a USB flash drive. Create one or two ext3/ext4 partitions on it. Second partition might be useful if you decide to install some extra SW packages (check http://www.dd-wrt.com/wiki/index.php/Optware) If not then one partition is enough. You can use the free EaseUS Partition Master to create and format the partitions from Windows.
2. Disable DLNA via WebUI
3. Plug the formatted flash disk into the rear USB2 connector.
4. Configure JFFS as explained there: http://www.dd-wrt.com/wiki/index.php/JFFS
(Note that Kong's WebUI allows mounting of the partition to JFFS from the Services->USB page. JFFS2 configuration is on the Administration page.)
5. Enable DLNA and clear database. After your media disk is scanned minidlna stores database on the external flash disk.
Posted: Sun Oct 05, 2014 4:37 Post subject: Kong Build R7000 multiple routers
Like many, I've had the multi reboot issue with DD-wrt and specifically with the kong builds. However, if I take two routers, turn one into wireless only and the other into router only (wireless off), then connect one to the other, I get all functionality and no reboots. This doesn't make sense to me, but thought I'd throw that out there to see if it helps anyone