Netgear R6700v3

From DD-WRT Wiki

Jump to: navigation, search


[edit] Hardware Specs

Nearly identical to Netgear R6400v2 but with the following changes:

  • Reduce the Heatspreader's size from 226x127 to 196x90.
  • Remove 2 shielding can on bottom PCBA.
CPU Broadcom BCM4708A0
CPU Speed 1 GHz (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 External
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

Supported in DD-WRT since build: 36995

KONG builds may also be used. (K3-AC-ARM folder)

Use the .chk file first and the webflash file to upgrade to a newer version of dd-wrt.

See Where do I download firmware? for links to both Kong and regular brainslayer builds. (located in the Netgear R6700v3 folder for brainslayer builds).

[edit] Debricking

See the second post in this thread: Netgear R6400v2 de-bricking

[edit] DO NOT 30-30-30 Reset ARM Devices 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)
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).