Your reports for Broadcom units are greatly appreciated !
Router:
Firmware:
Kernel:
Status:
Reset:
Errors:
This build thread is for reporting successes and problem with loading this experimental test build. This is important info for developers and users. Always state your hardware and SPECIFIC build (e.g. 29440_NEWD-2_K2.6_mega-nv64k.bin). Do not ask questions about your specific router or how to configure it in this thread; create your own thread to discuss any specific problems you have or need resolved. Please also do not respond to such questions. This thread is to report info, not to seek it. Posts that do not add to understanding this build will be deleted. Make sure you know how to flash properly and the risk before using this build. It is important to adhere to these requirements, to keep this thread from becoming impossibly long and useless. If you don't know what build to flash and how to flash properly and have a means of recovery if things should go wrong, do NOT flash this experimental test build. _________________ Unofficial Kong's release repository : http://ddwrt-kong.clonevince.fr/
Posted: Sun Jun 12, 2016 7:15 Post subject: Re: New Kong's build: DD-WRT 29875M - 2016/06/11
Router: R7000
Firmware: DD-WRT v3.0-r29875M kongac (06/11/16)
Kernel: 3.10.101 #10 SMP Sat Jun 11 23:17:16
Status: running
Reset: no, ddup update without reset
Errors: so far no errors guess this release will be as stable as 29620 as this is again on 3.10 Kernel
Router: R7000
Firmware: DD-WRT v3.0-r29875M kongac (06/11/16)
Kernel: Linux 3.10.101 #10 SMP Sat Jun 11 23:17:16 CEST 2016 armv7l
Status: Running
Reset: No reset > ddup --flash-latest
Errors: None so far
Posted: Sun Jun 12, 2016 9:22 Post subject: DD-WRT v3.0-r29875M Netgear R7000 recursive DNS not working
Router: Netgear R7000
Firmware: DD-WRT v3.0-r29875M kongac (06/11/16)
Kernel: Linux 3.10.101 #10 SMP Sat Jun 11 23:17:16 CEST 2016 armv7l
Status: running
Reset: yes, through webinterface bs build
Errors: recursive DNS not working
Could this error be provider dependent? _________________ IT Crowd - Have You Tried Turning It Off And On Again?
Whew, glad I got a copy of 29850 before Kong gave up on K4 and went back to K3 again.
That reminds me. I'd like to propose a change in the formatting of threads here. The first post in these threads should have the firmware and kernel version filled in. The ones following should just have "Router Model", "Status", "Reset", and "Errors". There's no need to repeat "firmware" and "kernel" in every post but it should be shown in the first post so that we don't have to wait several posts for someone to fill it in to know what kernel is in this version. Just a thought.
R8500 is working with this build ( 29875 ).
R7000 is working too
IMHO ... last one ( 29850 K4 ) R8500 works fine for 24 hours , but R7000 dont ...
There does seem to be a difference with R7000 versus R8500. I'm still on R29850 with my R8500 and it's been up with no problems for 38 hours now. I'm kinda "scared" to go back to K3 builds on my R8500 because on every K3 build I've tried, the R8500 drops all 2.4Ghz clients after some hours and has to be rebooted to regain 2.4Ghz. Maybe that's been fixed but I'm trying to stick with K4 builds on the R8500 because I've yet to have a problem with those.
Whew, glad I got a copy of 29850 before Kong gave up on K4 and went back to K3 again.
That reminds me. I'd like to propose a change in the formatting of threads here. The first post in these threads should have the firmware and kernel version filled in. The ones following should just have "Router Model", "Status", "Reset", and "Errors". There's no need to repeat "firmware" and "kernel" in every post but it should be shown in the first post so that we don't have to wait several posts for someone to fill it in to know what kernel is in this version. Just a thought.
Mike
+1! On Atheros forum is already like you say!
[offtopic]Anyway my R7000 is on BS r29837 with K4, if I flash straight from web interface to try this Kong build with K3, this will reset my settings?
Thanks![/offtopic]
R8500 is working with this build ( 29875 ).
R7000 is working too
IMHO ... last one ( 29850 K4 ) R8500 works fine for 24 hours , but R7000 dont ...
There does seem to be a difference with R7000 versus R8500. I'm still on R29850 with my R8500 and it's been up with no problems for 38 hours now. I'm kinda "scared" to go back to K3 builds on my R8500 because on every K3 build I've tried, the R8500 drops all 2.4Ghz clients after some hours and has to be rebooted to regain 2.4Ghz. Maybe that's been fixed but I'm trying to stick with K4 builds on the R8500 because I've yet to have a problem with those.
Mike
In K4.4 builds there is a new dhd driver for the R8000/R8500 thus I would expect it to be better and fix a few things that are not working in the previous driver.
4.4 will be back once I fixed the issues, that I found. I just fell for those everything is OK comments from you guys and BrainSlayer.
Lesson learned, don't trust anything except my systematic tests.
Want an example:
constantly ping the routers lan ip and then run command "ifconfig br0 down"
now you have your kernel crash, does not happen on 3.10:-)
R8500 is working with this build ( 29875 ).
R7000 is working too
IMHO ... last one ( 29850 K4 ) R8500 works fine for 24 hours , but R7000 dont ...
There does seem to be a difference with R7000 versus R8500. I'm still on R29850 with my R8500 and it's been up with no problems for 38 hours now. I'm kinda "scared" to go back to K3 builds on my R8500 because on every K3 build I've tried, the R8500 drops all 2.4Ghz clients after some hours and has to be rebooted to regain 2.4Ghz. Maybe that's been fixed but I'm trying to stick with K4 builds on the R8500 because I've yet to have a problem with those.
Mike
In K4.4 builds there is a new dhd driver for the R8000/R8500 thus I would expect it to be better and fix a few things that are not working in the previous driver.
4.4 will be back once I fixed the issues, that I found. I just fell for those everything is OK comments from you guys and BrainSlayer.
Lesson learned, don't trust anything except my systematic tests.
Want an example:
constantly ping the routers lan ip and then run command "ifconfig br0 down"
now you have your kernel crash, does not happen on 3.10:-)
There is a big gap between it is "working here" and "it makes it through a series of tests".
Very well said Kong. Building on that what would be helpful for everyone is an executable script that runs a set series of tests, and have us post the results of the tests. So much more meaning full than our current personal opinion of "Status: Working" and "Errors: No"
I would be willing to put my time towards development an official router testing script for testing dd-wrt builds _________________ Location (urban) - 1x Linksys EA8500 (AP wlan0 & wlan1 enabled)
1x Asus 68u (Repeater Bridge w/VAP) - wl0 disabled
1x Asus 87u (Client Bridge) - wl1 disabled
Router: Asus RT-AC68U
Firmware: DD-WRT v3.0-r29875M kongac (06/11/16)
Kernel: Linux 3.10.101 #10 SMP Sat Jun 11 23:17:16 CEST 2016 armv7l
Status: Running
Reset: No reset
Errors: None _________________ Netgear R7000 on Build 55109
Asus AC-AC68U rev. C1 (AP) on Build 55109
Asus AC-68U rev. A1 on Build 54604
Asus AC-68U rev. A1 on Build 53339
Router: Dlink-DIR860L-A1
Firmware: DD-WRT v3.0-r29875M kongac (06/11/16)
Kernel: Linux 3.10.101 #10 SMP Sat Jun 11 23:17:16 CEST 2016 armv7l
Status: Stable so far
Reset: yes via WebGUI
Errors: none
Thank you Sir Kong _________________ Dlink-DIR860L-A1
DD-WRT v3.0-r30560M kongac (09/05/16)
