Joined: 19 Nov 2008 Posts: 274 Location: Madison, CT, US
Posted: Tue Oct 14, 2014 21:38 Post subject:
sm2707 wrote:
Malachi - One more question, please
What file I should pick for NETGEAR AC1450 router. I read the following from 'supported Models' file, but it doesn't talk about what I specific file I need to pick for this specific router. Thanks in advance.
dd-wrt.v24-K3_AC_ARM_STD_OLDD.bin -> Standard Build with older but more stable wireless drivers
dd-wrt.v24-K3_AC_ARM_BT_OLDD.bin -> Standard Build without Zabbix but Transmission Client
dd-wrt.v24-K3_AC_ARM_STD_NEWD.bin -> Standard Build with latest wireless drivers
dd-wrt.v24-K3_AC_ARM_BT_NEWD.bin -> Standard Build without Zabbix but Transmission Client
I use the BT_OLDD.bin and it's been stable for me. I do not have newer AC clients, but 2.4 and 5 GHz are stable. _________________ Netgear R7800(2), R7500v2(2) WDS, Asus RT-AC68R (2)
What file I should pick for NETGEAR AC1450 router. I read the following from 'supported Models' file, but it doesn't talk about what I specific file I need to pick for this specific router. Thanks in advance.
dd-wrt.v24-K3_AC_ARM_STD_OLDD.bin -> Standard Build with older but more stable wireless drivers
dd-wrt.v24-K3_AC_ARM_BT_OLDD.bin -> Standard Build without Zabbix but Transmission Client
dd-wrt.v24-K3_AC_ARM_STD_NEWD.bin -> Standard Build with latest wireless drivers
dd-wrt.v24-K3_AC_ARM_BT_NEWD.bin -> Standard Build without Zabbix but Transmission Client
Kong has ceased development and has pulled his builds.
What a shame!!! Great loss for the community.
He is back.
Sorry for mentioning it here, but since it was brought up about the EX6200, since Kong doesn't have that page with his builds anymore, is there an updated ddwrt.K3_EX6200.chk file somewhere else? I looked on the ddwrt ftp in the beta folder for ex6200 and in there is a 7.8MB (right size) .bin file (wrong file type for a stock-to-ddwrt flash). Any ideas? or should i just use the old one and update the bin once I have ddwrt?
Hey thanks! If there was a thumbs up or thanks button, I'd do that.
A couple questions:
1. I did flash the original chk file for the EX6200 and it worked, then i did a reset, then I flashed the latest beta from 10-27 which was a bin file, but after that was loaded, the date of the build is the same as before, it didn't change (June or July something, basically whatever it was for the original chk file). is something wrong or are they just not updating the ex6200 in their builds?
2. on the AC1450, Kong used to post the OLDD and NEWD, but now that we need to go to the beta folder in the FTP site, it just gives the one option. Do you know whether that is considered OLDD or NEWD? and is there a way to get OLDD for new features and builds?
Brainslayers builds for ex-6200 are way too big to fit in 8MB flash so you'll have to stay at the revision you are on until he has fixed the size by removing some features.
Brainslayers builds are always based on the latest wl driver provided to him by Broadcom.
The builds are test builds/betas and Broadcom is not interested in test result from old drivers. _________________ Kernel panic: Aiee, killing interrupt handler!
Brainslayers builds for ex-6200 are way too big to fit in 8MB flash so you'll have to stay at the revision you are on until he has fixed the size by removing some features.
Brainslayers builds are always based on the latest wl driver provided to him by Broadcom.
The builds are test builds/betas and Broadcom is not interested in test result from old drivers.
Thanks for the great feedback!
So, since Kong is no longer building and everything is going to be based on Brainslayer's builds, I imagine it'll take a bit to get things like the EX6200 build updated and all? (However, the *.bin build for the latest (Oct 27) beta for EX6200 was 7.8MB as listed on the FTP site, so shouldn't that have worked? I figured it was a simple case of it being the same data as the original *.chk file, just with bin instead of chk. Is that not the case?)
With respect to the old/new drivers, I guess working on the beta line might lead to some unstable drivers, where as Kong built some builds with old stable drivers for people who wanted that, but that was more like a bonus?
I have the AC1450 and EX6200 and what I'd like to do is have the EX6200 connected to one of the output ports of the AC1450 and basically extend the WiFi reach using the same wifi network that AC1450 is outputting. I guess that's called a wired access point? The EX6200 would be located in a place where it wouldn't see the WiFi signal (or it would have a very very low signal) of the AC1450. Therefore, having it wired and then transmit the same signal for the wifi, thereby "extending" it. .... How exactly do I set that up so that devices can be connected to either router and have it be like its all the same network (shares, ip address, etc.)?
I'm certainly missing something, as I am relatively new to DD-WRT, though not to networking.
With the NetGear factory image at 1.0.0.22_1.0.10, I was able to get "N" rates up to 450 Mbps, on my NewEgg refurb AC1450.
I flashed the "OLD" and "NEW" DD-WRT images. Both images transferred and booted fine, was able to config them, etc.
dd-wrt.v24-K3_AC_ARM_STD_OLDD.bin
dd-wrt.v24-K3_AC_ARM_STD_NEWD.bin
After the intial load of:
dd-wrt.K3_AC1450.chk
I tried all manner of mixed and N-only selections on both wireless interfaces. But I can't get N-based connectivity at all on DD-WRT, only G or A. Client is a late 2011 MBP.
I'm probably missing something simple, any ideas. Many thanks in advance for the expert guidance that abounds in here, it's really amazing!!!
Joined: 22 Apr 2014 Posts: 31 Location: Washington State
Posted: Sun Nov 30, 2014 23:40 Post subject: Kong Build 24045 has been solid on my AC1450
I bought the AC1450 at Costco when it was on-sale last March. The stock Netgear firmware was horrible - it crashed at least once per day, the DHCP server frequently got lost and stopped assigning addresses, and it has no useful guest network implementation. So I was motivated to move to DD-WRT.
After some weeks of discussion on another thread in this forum last April-May (2014), Kong posted a DD-WRT build for the AC1450 that I've been happily using since then. That thread is titled support for the R6300V2, but on pages 14-15 there's a lot of data on the AC1450.
You will see that you can't just flash the R6300V2 firmware - it is not reliable on the AC1450 (I know - I've tried it)
Kong Build 24045 is the first one that ran reliably. I have not tried any later builds.
I use both 2.4 and 5GHz bands, I have a guest vlan where multiple guests can interact but they're firewalled off of my primary LAN (a capability missing from Netgear firmware, which means with stock Netgear, you can't even use a smartphone to control a ROKU box if your ROKU is on your guest LAN where it belongs). I also use the USB port for a 3Tb NAS drive on my LAN via DD-WRT Samba implementation (I have both EXT4 and NTFS partitions). The only thing I wanted that I've not had time to troubleshoot is the DLNA server.
But I've seen over 80 days with no reboot. (80 days is about as long as our Eastside of Seattle area power company can ever keep the lights on without some problem)
INSTALLING DD-WRT ON THE AC1450
1) Backup your CFE file. Your flash is composed of three parts. The CFE file, which is the program that boots the router and is specific to your router, the NVram which is the memory for settings (simplistic explanation, I know) and the kernel which is the firmware. You can erase the nvram. You can reflash the kernel But if you don't have a CFE file FOR your specific model of router, you are hosed. Instructions for doing this are here:
http://www.dd-wrt.com/wiki/index.php/CFE_backup
NOTE: ADVISE TO CLEAR YOUR BROWSER CACHE BEFORE FLASHING
2) Using the stock AC1450, flash the initial / transition DD-WRT firmware file
dd-wrt.K3_AC1450.chk (seems the more current file name on Kong's ftp site is: factory-to-dd-wrt.chk)
then reset the router. When you boot up, you'll see a generic DD-WRT has now replaced the Netgear firmware. Don't waste time configuring this transition firmware -- move on to flash the "real" firmware.
3) Using this initial DD-WRT firmware upgrade screen, you need to flash the actual Build 24045 (or whatever later build you have chosen). I am using this file name from Bld 24045:
dd-wrt.v24-K3_AC_ARM_STD_NEWD.bin
4) Reset the router again. Boot up and verify that you are in the desired build by looking at the upper right of the DD-WRT firmware home page (after you've logged into DD-WRT)
5) At this point, configure the router as you need to for your network.
It appears that the last one posted there (Build 25408) includes support for the AC1450. (open the Netgear ac1450 folder to get the firmware files you need)
I've downloaded it for (perhaps) future testing, but at the moment, Build 24045 ain't broke (for the way I'm using it), so I'm not inclined to "fix" it. _________________ Netgear AC1450
Kong DD-WRT
Thank you so much for the helpful information. I have a Netgear AC-1450 purchased at Costco. I was using the 1.0.0.22 firmware that came with it, flashed to 1.0.0.34, but noticed very few changes with options. Using the info on this page, I downloaded r25139 and r27506 from the ftp site (ftp://ftp.dd-wrt.com/betas/2015/) (betas/2014 and betas/2015 respectively). Within each release I went into the Netgear AC1450 folder and downloaded both files.
Using IE, I upgraded to the interim factory-to-dd-wrt.chk firmware using the stock firmware upgrade feature. Restarted browser (because it was acting funny, probably needed to clear cache). Then upgraded to netgear-ac1450-webflash.bin using the interim DD-WRT upgrade feature.
I'm currently running "DD-WRT v3.0-r27506 (07/09/15) std". I did no "hard resets" (30/30/30), but I'm not saying that's the right thing to do. Just wanted to share what I did in case it helps anyone else. If someone wants to chime in and say what I did was bad and why, please do, to help others
Now to figure out how to restrict bandwidth consumption of certain devices, reduce torrent downloads (throttle speed or block all P2P), and track usage by device (if possible).
I would reset to factory defaults before you configure, just to make sure anything from the stock firmware is gone.
Also, for usage by device, check out YAMon2 (Yet Another Monitor 2) http://www.dd-wrt.com/phpBB2/viewtopic.php?t=259806. Read the first post that Al always updates with the latest version, and the last 4-5 pages and you should be good. _________________ R7800 Nighthawk - DD-WRT v3.0-r58850 std (Primary)
R7800 Nighthawk - DD-WRT v3.0-r58389 std (Cold Secondary)
▲ ACTIVE / INACTIVE ▼
R7000 Nighthawk - DD-WRT v3.0-r58850 std (Still works great after running for 10 years solid)
R7000 Nighthawk - DD-WRT v3.0-r58850 std (Cold Secondary)
R7000 Nighthawk - DD-WRT v3.0-r58389 std (Extra)
~~~~~~~~~~Dismantled for learning opportunities~~~~~~~~~~
WRT54Gv2
WRT54Gv8.2
~~~~~~~~~~Other Settings~~~~~~~~~
https://nextdns.io/?from=2d3sq39x https://pi-hole.net/ https://github.com/DNSCrypt/dnscrypt-proxy
Had a bit of a scare when trying to go from default NETGEAR firmware to DD-WRT.
I first used factory-to-dd-wrt.chk from ftp://ftp.dd-wrt.com/betas/2015/12-10-2015-r28493/netgear-ac1450/ by uploading it via the NETGEAR UI. My AC1450 would then get stuck with the power light blinking (green). I could still ping 192.168.1.1, so it wasn't dead.
After almost an hour of waiting, I learned that if you tftp the .chk file over, it should eventually start working again, which it did. This was my tftp command (after cd'ing CMD's directory to where the file was located):
Code:
tftp -i 192.168.1.1 put factory-to-dd-wrt.chk
Within a few minutes, I was at DD-WRT's main screen. I then used the built-in updater to flash netgear-ac1450-webflash.bin (from the same link above) that version (opting for it to automatically reset settings after the flash).
