since I already on DD-WRT i assume i install the K3.X NV64 Bin Build over the 2.6 Build and from there i can just install the normal builds without the NV64 flag right?
I do recall that, but wasn't sure if that was new or old info, so I still always use the nv64k for my WNDR4000.
XxUnkn0wnxX wrote:
also is the WAN to LAN still around 75Mbps on the K3.X builds (why slower then the K2.6)
My service is 75mbps, so I can't say; didn't see much difference. I will say...since I'm now using k2.6 w/ 27600, my wireless is much more stable, esp. 5ghz. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
You guys with these netgear routers that required a K2.6_nv64 you still have to use the K3.x_nv64 also applies to the E1200v2 and I assume the other nv64 boxes.
Routers such as the E2500 that required a K2.6_nv60 can use the regular K3.x_mega
Thanks, I guess i should have been more specific. I was using the mega-nv64 build. Also if you tftp the WNDR3400 K3X chk file, it, too, bricks the router.
Thanks, I guess i should have been more specific. I was using the mega-nv64 build. Also if you tftp the WNDR3400 K3X chk file, it, too, bricks the router.
Yea, I don't have that box so can't help you much with that.
I was generally referring to this
Quote:
since I already on DD-WRT i assume i install the K3.X NV64 Bin Build over the 2.6 Build and from there i can just install the normal builds without the NV64 flag right?
from few posts up.... Didn't want a misunderstanding.
Just a side note - - - the only way to get a K3.x build on a E1200v2 is first install a K2.6_mini
I have NO idea if that would help on your box.
I'm also trying to find path to upgrade k2.6 to k3.x on rt-n16.
I've done it a long time ago and stayed on k3.x for a while.
Unfortunately I just downgraded to k2.6 last night, but now I can't upgrade to k3.x. I wish I wrote it down how I did it.
I read all 49 pages of this thread mentioning r-n16, and tried many different combination including frequently mentioned 21530 k3.x, but keep bricking the router.
When I recover the brick, I restored:
dd-wrt.v24-13297_NEWD-2_K2.6_mini_RT-N16.trx
Then go to
dd-wrt.v24-21676_NEWD-2_K2.6_mega.bin
Then go to
dd-wrt.v24-21530c_NEWD-2_K3.x_big.bin
Then the router bricks
Any suggestion?
Thanks,
MS
callihn wrote:
I haven't had any luck testing on the rt-n16, anyone have a working upgrade path from 2.6? Couldn't find the 2.6 version mentioned in the forums and the version below and above caused me to use recovery mode.
Also are there any known bandwidth or throughput issues and will it break my umurmur server? Which BTW took a lot of scavenging to get the next to latest version going.
I'm also trying to find path to upgrade k2.6 to k3.x on rt-n16.
I've done it a long time ago and stayed on k3.x for a while.
Unfortunately I just downgraded to k2.6 last night, but now I can't upgrade to k3.x. I wish I wrote it down how I did it.
I read all 49 pages of this thread mentioning r-n16, and tried many different combination including frequently mentioned 21530 k3.x, but keep bricking the router.
When I recover the brick, I restored:
dd-wrt.v24-13297_NEWD-2_K2.6_mini_RT-N16.trx
Then go to
dd-wrt.v24-21676_NEWD-2_K2.6_mega.bin
Then go to
dd-wrt.v24-21530c_NEWD-2_K3.x_big.bin
Then the router bricks
Any suggestion?
Thanks,
MS
Don't reset router to defaults and don't erase NVRAM. _________________ 2 times APU2 Opnsense 21.1 with Sensei
2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)
3 times Asus RT-N16 shelved
E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)
3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)
Don't reset router to defaults and don't erase NVRAM.
I tried both resetting the router, and without resetting from "After flashing, reset to", but no luck. I'm not sure how to erase NVRAM, so probably I didn't do that.
Any other suggestion?
Otherwise on some WNR3500L boarddata is not read correctly and the wireless driver cannot get the correct parameters.
In case anyone with WNR3500L stumbles across this thread (this build 21605 appears to be the only K3.x build that fits WNR3500L flash) ... I was able to get the radios working with this build following this method: http://www.dd-wrt.com/phpBB2/viewtopic.php?p=983621&highlight=#983621
Router Model
Netgear WNDR3700v3
Firmware Version
DD-WRT v24-sp2 (05/14/13) mega - build 21605
Kernel Version
Linux 3.9.2 #83 Tue May 14 12:42:05 CEST 2013 mips
CPU Model
Broadcom BCM4716 chip rev 1
Solid! Thanks man,
p2p performance is much better than jan 11 2015 mini version.
Posted: Tue Sep 29, 2015 0:00 Post subject: WRT320N with K3.X
Router Model
Linksys WRT320N
Firmware Version
dd-wrt.v24-27805_NEWD-2_K3.x_mega_wrt320n
Kernel Version
Linux 3.10.87 #9671 Fri Sep 11 08:33:27 CEST 2015 mips
CPU Model
Broadcom BCM4716 chip rev 1
Flashed up from K2.6 build 21061. Besides a duplicate LAN and WIFI MAC address, no problems so far.
Installed K3x latest version, recommended version, and some of the older version to Asus RT-N66u.
Set as pure access point and nothing else.
But all version somehow got same problem with MAC Filtering.
Once i enable MAC filtering "Permit only clients listed to access the wireless network ", then all the clients cannot connect. Tested with My Jelly Bean android, error "authentication problem"
ONLY if i disable the MAC filtering, then can connect without any problem.
Btw i put many MAC Addresses, total 75 MACs.
Old router Linksys WRT310N with DD_WRT and exact same setting can work nicely with same qty of MAC Addresses. but of course it is not using K3x
Once i enable MAC filtering "Permit only clients listed to access the wireless network ", then all the clients cannot connect. Tested with My Jelly Bean android, error "authentication problem"
ONLY if i disable the MAC filtering, then can connect without any problem.
Btw i put many MAC Addresses, total 75 MACs.
Check the free memory and nvram memory. Since that is stored in NVRAM, Maybe you are over running part of the firmware.
Try it with only 1 mac address and see if it works.
That would eliminate the quantity being the problem.
Brian
i experienced the problem month´ ago with the same router with only 1 mac address _________________ RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
