Netgear AC1450
From DD-WRT Wiki
Current revision
Contents |
[edit] Hardware Specs
Same as the Netgear R6300v2. Software crippled.
CPU | Broadcom BCM4708A0 |
---|---|
CPU Speed | 800 MHz (2 Cores) |
Flash ROM | 128 MB |
RAM | 256 MB |
Radios | BCM4360 5 GHz & BCM4331 2.4 GHz |
WLAN Support | a/n+ac 3x3:3 & b/g/n 3x3:3 |
WLAN Max Speed | 450 Mb/s (2.4Ghz), 1300 Mb/s (5Ghz) |
Antenna Location | Internal |
Switch | 4x GigE LAN + 1 GigE WAN |
USB | 1x USB 3.0 + 1x USB 2.0 |
Power Adapter | 12VDC 2.5A wall wart |
[edit] Installation
The OEM software-crippled Costco AC1450 hardware has the same FCC ID as the v2. Kong added support for it (build 25139), use the netgear-ac1450 directory.
DO NOT use burnboardid to convert to a R6300v2, per Kong:
"I'm pretty sure init params for the 1450 are different and you may experience strange problems"
Kong or brainslayer builds can be used, after 25139.
See Where do I download firmware? for links to newer versions.
[edit] DO NOT 30-30-30 Reset ARM Devices
...in addition to the reset button as described above...
From the GUI:
If you need to reset (clear historical NVRAM settings) select factory reset option from drop down on firmware upload web gui page. or use the reset to default settings WEBIF.
Administration > Factory Defaults (select radio button, then apply settings)
or
Administration > Firmware Upgrade (after browsing to your firmware file, select "reset to defaults" from dropdown, then click upgrade button)
From the Command Line Interpreter (CLI):
Telnet over to the device and pass the following command (without quotes): "nvram erase && reboot"
Reset notes: We all know to reset after initial flash. In early Feb. 2015 Kong announced a reset is required for certain upgrades as well, summary HERE. While not always necessary, resetting and re-configuring manually is also a best practice for upgrades. In Q1 2015 it was noted that users that reset from the CLI and MANUALLY RECONFIGURED after upgrading avoided issues (do NOT restore a NVRAMBAK from previous build it basically will undo your CLI reset).