The link given to you above are Kong's personal test builds and are used at your own risk. It is also assumed you already have a version of dd-wrt installed.
Read thru the R7000 sticky for more info.
This location now contains my personal test builds." _________________ Segment 1 XR700 10Gb LAN, 1Gb WAN ISP BS
Wired AP 1 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 2 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 3 Unifi Wifi 6 LR US 1Gb LAN
Syslog Services Asustor 7110T NAS 10GB
NetGear XS716T 10GB Switch
download1.dd-wrt.com/dd-wrtv2/downloads/betas/ (Brain Slayer)
YAMon https://usage-monitoring.com/index.php
Posted: Thu Jan 15, 2015 21:22 Post subject: Re: Some Important Questions About R7000, Kongs Firmware
Keomas wrote:
...
I wonder if this firmware (kongs) is still being updated? I also wonder if I have the latest firmware version of Kongs r7000 firmware?
First off just have to say thanks to Kong for all the great work/firmware...
Thanks Kong!
Here is how I wrap my tiny peanut brain around this topic... Feel free to correct me & point out my errors. This is just based on my point of view with the hardware I've had experience with. YMMV and I could be dead wrong.
That said, I've tried to do a good job of reading up on the forums to understand what has transpired on this subject in recent months
Kong is still active.
He is contributing to the main "Slayer" builds now. Downloads found here: ftp://ftp.dd-wrt.com/betas
If you don't believe me you can check the SVN timeline here: http://svn.dd-wrt.com/ (might have to expand the # of days in the search, he appears to push changes sporadically, as of this moment here is his last contribution http://svn.dd-wrt.com/changeset/25736)
^^ that said/understood.
KongMOD:
He is NOT maintaining a separate kong mod firmware any longer (at least not at this time).
Kong Mod in my little bubble means his tweaks for firmware like KongAC/VPNKong/KingKong, etc.
He maintained these K26 builds for hardware like the E3000/E4200/Asus RT-N16/
He even branched into K3 builds for newer AC draft hardware.
My understanding for KongMod was he wanted to add functionality to certain builds/devices. Given hardware limitations of those devices he had to strip out "standard" functionality in order to make his feature additions.
He was kind/gracious enough to even go back and push some k26 updates after he had started upgraded to newer hardware. (i.e. his heartbleed fix in June 2014 branded 22200++)
Well my guess is that these personal builds are just for Kong's PERSONAL testing... i.e. before he plugs it into the main "slayer" tree via formal SVN changes.
In my tiny peanut brain these are no longer a "KongMod" for example do you see KingKong, VPN Kong, or MiniDLNA builds in the K26 folder? Nope! (at least not right now/yet/maybe ever?)
Personally I don't think I will be flashing a lot of Kong's "personal testing" builds. Unless of course there is a very specific thing I am working with the developer on and I've been asked to test a personal build.
I'd also be careful just flashing things we find in the test location just because we got comfortable using his historically stable builds.
Discliamer: Assumptions were made ^^above^^, I'm also just some random, crazy guy from the internet.
My personal opinion/observations appear below...
In summary NO MORE KONGMOD.
The days of having a change log spoon fed to us in plain english are over. But this isn't necessarily bad!
Also you certainly can't blame Kong. He has graduated onto new devices and decided to contribute exclusively to the DD-WRT Main SVN.
I guessing that when he had/owned/was using some of the old K26 KONGMOD devices he was enjoying what he was doing...
I assume he still enjoys what he is doing, but now he is concentrating on newer devices.
With these newer hardware he doesn't have to pull out functionality to work on/add the things he wanted/enjoyed/needed in his personal router deployment. As such he has made the decision to not maintain a separate build.
We as the community will now have to adapt.
While we are at it, we should all thank him for his past, current and continued contributions. _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
Welcome,
No you are confused.
The url you pointed to is not the latest R7000 dd-wrt firmware.
Also, the term stable is relative. Each version of code still posted has been stable for enough of the community (no glaring bug to get it pulled by dev) that it is considered stable in some environments.
When your dealing with 3rd party/free firmware it is all BETA.
Initial firmware is what you load onto a router FIRST when migrating from stock firmware.
After that you load which ever version of dd-wrt you find for your needs.
Kong is no longer releasing his own firmware to the community with support. He does have a "at your own risk" url where he keeps his newest firmware.
You can find it here: http://www.desipro.de/ddwrt/
BrainSlayer (or BS for short)is the primary dd-wrt developer. You can find his latest (includes initial in the same folder) here: ftp://ftp.dd-wrt.com/betas/
I hope that helps clarify the basics of which firmware is available, where & the terms.
If your looking for stable, stick to stock. 3rd party firmware is for people who want more AND are WILLING to learn/figure things out. Stock firmware protects the basic user who just wants a router to do its job. 3rd party firmware allows you to control your router to do more but you have to understand what you are telling it to do.
Note the importance that article^^ places on wiki/forum research. Got to know what you are doing PRIOR to straying from stock/vendor firmware. (Also router db is NOT a good source.)
Initial builds are typically only used to get from vendor stock firmware to dd-wrt. You linked to Kong's initial builds... Slayer keeps a "factiry-to-dd-wrt.chk" initial build on the ftp along with the standard .bin files...
i.e. ftp://ftp.dd-wrt.com/betas/2015/01-17-2015-r25948/netgear-r7000/
Wiki on R7000 with install instructions section:
http://dd-wrt.com/wiki/index.php/DD-WRT_on_R7000 _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
Welcome,
He does have a "at your own risk" url where he keeps his newest firmware.
You can find it here: http://www.desipro.de/ddwrt/
BrainSlayer (or BS for short)is the primary dd-wrt developer. You can find his latest (includes initial in the same folder) here: ftp://ftp.dd-wrt.com/betas/
Word of caution. Unless you are working with Kong directly testing/squashing bugs I wouldn't consider this "his newest"...
This is his work in progress. Perhaps he is working with someone else (i.e. not your average user that finds the web share)... Someone with specific hardware that kong doesn't own...
Anything worthwhile that comes out of this testing will get loaded up into the slayer builds via svn.
^^speculation,but unless youbare specifically invited, or Kong announces he is forking again... I would shy away from those personal builds. Kist see the readme.
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
I would have kept the stock firmware if my connection didn't kept disconnected each time i used a bittorrent client. The solution was to turn off the SPI firewall each time i use the bittorrent client, at least that's what i read in a forum.
I would have kept the stock firmware if my connection didn't kept disconnected each time i used a bittorrent client. The solution was to turn off the SPI firewall each time i use the bittorrent client, at least that's what i read in a forum.
Yeah, once you go dd-wrt you never go back, haha. I started playing with DD-WRT for the TX Power boost in a WDS repeater setup.
<Disclaimer>
note my advice below might be useless, YMMV, I'm just a random crazy person from the internet
</Disclaimer>
Your R7000 seems to be quite the popular model, so plenty of people are writing about it on the forums. Here is how I'd keep an eye out for new firmware...
Sometimes you get cut living on the bleeding edge:
Also if the build you are using is working there might be a "if it isn't broke don't fix it" factor to consider.
Personally, I still plan to use Kong's K26 22200++ build from June 2014 for a good long while. Hell, I still use 14929 on several older devices.
Many users simply don't' need to live on the "bleeding edge"... It is like on my smartphone, settling on a CM11 snapshot vs. keeping up on researching/flashing the nightlies. _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
I would have kept the stock firmware if my connection didn't kept disconnected each time i used a bittorrent client. The solution was to turn off the SPI firewall each time i use the bittorrent client, at least that's what i read in a forum.
Yeah, once you go dd-wrt you never go back, haha. I started playing with DD-WRT for the TX Power boost in a WDS repeater setup.
<Disclaimer>
note my advice below might be useless, YMMV, I'm just a random crazy person from the internet
</Disclaimer>
Your R7000 seems to be quite the popular model, so plenty of people are writing about it on the forums. Here is how I'd keep an eye out for new firmware...
Sometimes you get cut living on the bleeding edge:
Also if the build you are using is working there might be a "if it isn't broke don't fix it" factor to consider.
Personally, I still plan to use Kong's K26 22200++ build from June 2014 for a good long while. Hell, I still use 14929 on several older devices.
Many users simply don't' need to live on the "bleeding edge"... It is like on my smartphone, settling on a CM11 snapshot vs. keeping up on researching/flashing the nightlies.
Dd-wrt made it possible to turn off the SPI firewall. But i can't use the vpn function of the dd-wrt now, i would like to connect my pptp vpn but it just doesn't work.
Dd-wrt made it possible to turn off the SPI firewall. But i can't use the vpn function of the dd-wrt now, i would like to connect my pptp vpn but it just doesn't work.
Other than pointing you to the VPN flavored WIKI tutorials, I'm not your guy...
Someone might be able to help you if you confirm what build of the firmware you are running on your R7000 (i.e. r25760) and if it is Kong's or Slayer's build. _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
25100 was the same thing just with some debugging added back in.
Also Kong's last on the R7000 was still in process (waiting on a driver update to fix reboot issues, etc.). I.e. not the "stable" level of maturity his builds achieved for older K26 devices
Hope this shorter summary of the thread detail ^^up there^^ helps. _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
