Has anyone flashed it? If so, did you go back to stock then go to the BS version? Can a Kong release be flashed to a BS release? If so, is a reset required?
On a side note: I miss the simple Kong changelog...
EDIT: changed the link to point to the generic directory instead of the R7000 specific one.
MOD EDIT:
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. (eg: 25139_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. 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.
Last edited by smapdi on Wed Oct 22, 2014 19:11; edited 1 time in total
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Wed Oct 22, 2014 18:49 Post subject:
redhawk0 wrote:
Running K3.x big build on my RT-N16 unit. All is working but the Country Regulatory Domain can not be changed from Europe to anything else.
Other than this...its working fine in Repeater mode.
redhawk
interesting. thats not supposed as it should be _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Joined: 25 Dec 2010 Posts: 295 Location: Twin Cities, MN
Posted: Wed Oct 22, 2014 20:35 Post subject:
upgraded from 25090 to 25139..dnsmasq must not be updated to 2.72? need for ipv6 and enable-ra's.. _________________ NETGEAR R9000 | RT | 40134 NETGEAR R7800 | AP | 40134
Posted: Wed Oct 22, 2014 20:50 Post subject: Linksys E3000
Router: Linksys WRT610N-V2 modded to E3000
was running: Kong 22000++
Am a long time lurker on these forums (i think 10+ years ), and DD-wrt user since like forever.
This is the first time i'm running into completely broken code.
First upgraded to dd-wrt.v24-25139_NEWD-2_K3.x_mega-e3000.bin, after reboot the router showed up as a Linksys WRT54G/GL/GS, with 2* 2.4GHZ wireless (instead of 1*2.4ghz and 1*5ghz). nvram reset did not cure this issue.
Afterwards upgraded to dd-wrt.v24-25139_NEWD-2_K2.6_mega-nv60k.bin
Router was no longer reachable via LAN afterwards, did a 30-30-30. Router was still not reachable via lan afterwards, but now did show up via WIFI. Via WIFI i could see that the LAN mac-addresses were lost (showing 00:00:00:00:00:02 on both wan and lan).
There is definitively something seriously broken with this build for the E3000.
Flashed the router back to Kong 22000++ for now.
If wanted i can supply screenshots from the status and wifi pages of the builds tested.
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Wed Oct 22, 2014 21:01 Post subject:
NiTrus wrote:
upgraded from 25090 to 25139..dnsmasq must not be updated to 2.72? need for ipv6 and enable-ra's..
dnsmasq cannot be upgraded so easy since they also removed features i need. for ipv6 you dont need dnsmasq since everything else like dhcpv6 etc is included (see ipv6 tab) _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Wed Oct 22, 2014 21:02 Post subject: Re: Linksys E3000
JohnnySL wrote:
Router: Linksys WRT610N-V2 modded to E3000
was running: Kong 22000++
Am a long time lurker on these forums (i think 10+ years ), and DD-wrt user since like forever.
This is the first time i'm running into completely broken code.
First upgraded to dd-wrt.v24-25139_NEWD-2_K3.x_mega-e3000.bin, after reboot the router showed up as a Linksys WRT54G/GL/GS, with 2* 2.4GHZ wireless (instead of 1*2.4ghz and 1*5ghz). nvram reset did not cure this issue.
Afterwards upgraded to dd-wrt.v24-25139_NEWD-2_K2.6_mega-nv60k.bin
Router was no longer reachable via LAN afterwards, did a 30-30-30. Router was still not reachable via lan afterwards, but now did show up via WIFI. Via WIFI i could see that the LAN mac-addresses were lost (showing 00:00:00:00:00:02 on both wan and lan).
There is definitively something seriously broken with this build for the E3000.
Flashed the router back to Kong 22000++ for now.
If wanted i can supply screenshots from the status and wifi pages of the builds tested.
if it shows up as wrong detected router, then your homebrew modification likelly run wrong. the router model is detected by the nvram parameters specific for the device. wrong detection means, wrong nvram settings _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
upgraded from 25090 to 25139..dnsmasq must not be updated to 2.72? need for ipv6 and enable-ra's..
dnsmasq cannot be upgraded so easy since they also removed features i need. for ipv6 you dont need dnsmasq since everything else like dhcpv6 etc is included (see ipv6 tab)
Not sure if that info got lost somewhere, according to:
the upgrade is impossible due to missing isc-lease file support, but isc-lease file support is not compiled in at least not in public repo. This should not be a reason to not upgrade.
But, size of new dnsmasq is 200k instead of 100k, this would be a problem for older models and their limited flash size.
Posted: Wed Oct 22, 2014 21:33 Post subject: Re: Linksys E3000
JohnnySL wrote:
BrainSlayer wrote:
if it shows up as wrong detected router, then your homebrew modification likelly run wrong. the router model is detected by the nvram parameters specific for the device. wrong detection means, wrong nvram settings
Ok, strange. As it shows up fine (Linksys E3000) when flashing (back) to Kong firmware.
Mod to E3000 was done exactly via CFE flash-procedure as described on this forum.
nvram show| grep WRT54 shows up nothing. Can you guide me what parameter(s) might be wrong?
edit:
a complete walk through the nvram settings shows:
boot_hw_model=E300
DD_BOARD=Linksys E3000
I might be missing a 0 there, which would make your analysis correct. will try to verify the value with a native e3000. thanks!
I have same problem on every 23xxx/24xxx K3.X build, I put on 21676 build without problem.
[Edit]: I have E1000, E2000 and E3000(converted from 610NV2). I backup CFE from E1000 and E2000 and open on Hex Editor, I found something interested. E1000 CFE shows boot_hw_model=e100, e2000 CFE shows boot_hw_model=E2000 and e3000 CFE(downloaded from DD-wrt post) shows boot_hw_model=e300.
so it looks like original CFE of E1000 and E3000 are missing one "0" in the boot_hw_model. Is this the parameter that dd-wrt gets model name during startup?
e3000.PNG
Description:
Filesize:
10.9 KB
Viewed:
25318 Time(s)
e2000.PNG
Description:
Filesize:
15.54 KB
Viewed:
25318 Time(s)
e1000.PNG
Description:
Filesize:
14.75 KB
Viewed:
25318 Time(s)
Last edited by newnews on Wed Oct 22, 2014 22:25; edited 1 time in total
Joined: 13 Mar 2014 Posts: 856 Location: Montreal, QC
Posted: Wed Oct 22, 2014 21:55 Post subject:
NiTrus wrote:
upgraded from 25090 to 25139..dnsmasq must not be updated to 2.72? need for ipv6 and enable-ra's..
here's what I did to use the 2.72 ipv6 enabled version of dnsmasq with build 25139
copy 2.72 from kong build 25090 to your opt partition on external storage /usr/sbin/dnsmasq to /opt/usr/sbin/dnsmasq
make sure the copy is executable
add the following to admin->commands->startup
stopservice dnsmasq
mount --bind /opt/usr/sbin/dnsmasq /usr/sbin/dnsmasq
startservice dnsmasq
this will effectively bind 2.72 version until you unmount or delete the command and reboot.
*** note i have not tested stop / start part as i use a script to kill process, modify conf file and restart it. I do the mount in admin->commands->startup.
The above should work just fine though. let me know if you have issues
*** edit changed order to stop,bind,start
**** edit 2. If you are having issues check your syslog
cat /tmp/var/log/messages
And make sure that the attempt to bind and restart dnsmasq happens AFTER your external storage has been mounted. See Nitrus's follow up as an example.
Last edited by JAMESMTL on Thu Oct 23, 2014 1:35; edited 1 time in total
Joined: 25 Dec 2010 Posts: 295 Location: Twin Cities, MN
Posted: Wed Oct 22, 2014 23:21 Post subject:
JAMESMTL wrote:
NiTrus wrote:
upgraded from 25090 to 25139..dnsmasq must not be updated to 2.72? need for ipv6 and enable-ra's..
here's what I did to use the 2.72 ipv6 enabled version of dnsmasq with build 25139
L
copy 2.72 from kong build 25090 to your opt partition on external storage /usr/sbin/dnsmasq to /opt/usr/sbin/dnsmasq
make sure the copy is executable
add the following to admin->commands->startup
stopservice dnsmasq
mount --bind /opt/usr/sbin/dnsmasq /usr/sbin/dnsmasq
startservice dnsmasq
this will effectively bind 2.72 version until you unmount or delete the command and reboot.
*** note i have not tested stop / start part as i use a script to kill process, modify conf file and restart it. I do the mount in admin->commands->startup.
The above should work just fine though. let me know if you have issues
*** edit changed order to stop,bind,start
doesnt work..dnsmasq wont re-start..
****edit*** GOT IT WORKING!!
if the above doesn't work, add sleep 5
stopservice dnsmasq
sleep 5
mount --bind /opt/usr/sbin/dnsmasq /usr/sbin/dnsmasq
startservice dnsmasq
*** edit2*** added dnsmasq 2.72 from Kong-Build for download