User Tools

Site Tools


toh:netgear:wndr3700

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
toh:netgear:wndr3700 [2013/02/09 17:38]
mandrawes
toh:netgear:wndr3700 [2015/05/09 23:37] (current)
Bernini [Supported Versions]
Line 1: Line 1:
-FIXME Hardware specific sections according to the [[meta:​template_device|Hardware Template]] wanted --- //​[[xm@subsignal.org|Jo-Philipp Wich]] 2010/03/22 14:18// 
- 
 ====== Netgear WNDR3700 and WNDR37AV ====== ====== Netgear WNDR3700 and WNDR37AV ======
 +The Netgear WNDR3700 has five different versions to date. Versions 1 and 2 are fully supported by OpenWrt and are based on the [[doc:​hardware:​soc:​soc.qualcomm.ar71xx|Atheros ar71xx platform]]. Version 3 uses a [[doc:​hardware:​soc/​soc.broadcom.bcm47xx|Broadcom SoC]] and has preliminar support in trunk (e.g. don't expect working wireless). The fourth version is a 2T2R version of the [[toh:​netgear:​wndr4300|WNDR4300 v1]]. The fifth version uses a MediaTek SoC.
  
 ===== Device Info and Specifics ===== ===== Device Info and Specifics =====
  
-**NOTE:** Netgear has sold a number of these units in boxes marked WNDR37AV This was done for marketing purposes solely, the hardware is exactly identical ​(even to the point of many users finding a router physically labeled "​WNDR3700 or WNDR3700v2"​ inside of a box labeled "​WNDR37AV"​).+==== Hardware Highlights ==== 
 +^ Ver ^ CPU ^ Ram ^ Flash ^ Network ^ Wireless ^ USB ^ Serial ^ JTag ^ Wiki ^ FCC ^ 
 +| v1 | Atheros AR7161 rev 2 680MHz | 64MiB | 8MiB | 1 WAN + 4x LAN (GBit) | AR9220 [an 2x2:2] + AR9223 [bgn 2x2:2] | Yes | Yes | Yes | [[https://​wikidevi.com/​wiki/​Netgear_WNDR3700v1|here]] | [[https://​apps.fcc.gov/​oetcf/​eas/​reports/​ViewExhibitReport.cfm?​mode=Exhibits&​RequestTimeout=500&​calledFromFrame=N&​application_id=278475&​fcc_id='​PY308300092'​|here]] | 
 +| v2 | Atheros AR7161 rev 2 680MHz | 64MiB | 16MiB | 1 WAN + 4x LAN (GBit| AR9220 [an 2x2:2] + AR9223 [bgn 2x2:2] | Yes | Yes | Yes | [[https://​wikidevi.com/​wiki/​Netgear_WNDR3700v2|here]] | [[https://​apps.fcc.gov/​oetcf/​eas/​reports/​ViewExhibitReport.cfm?​mode=Exhibits&​RequestTimeout=500&​calledFromFrame=N&​application_id=290558&​fcc_id='​PY308300092'​|here]] | 
 +| v3 | Broadcom BCM4718A1 | 64MiB | 8MiB | 1 WAN + 4x LAN (GBit) | BCM4331 [an 2x2:2] + BCM4718A1 [bgn 2x2:2] | Yes | ? | ? | [[https://​wikidevi.com/​wiki/​Netgear_WNDR3700v3|here]] | [[https://​apps.fcc.gov/​oetcf/​eas/​reports/​ViewExhibitReport.cfm?​mode=Exhibits&​RequestTimeout=500&​calledFromFrame=N&​application_id=651807&​fcc_id='​PY311200166'​|here]] | 
 +| v4 | Atheros AR9344 560MHz | 128MiB | 128MiB NAND | 1 WAN + 4x LAN (GBit) | AR9582 [an 2x2:2] + AR9344 [bgn 2x2:2] | Yes | Yes | Yes | [[https://​wikidevi.com/​wiki/​Netgear_WNDR3700v4|here]] | [[https://​apps.fcc.gov/​oetcf/​eas/​reports/​ViewExhibitReport.cfm?​mode=Exhibits&​RequestTimeout=500&​calledFromFrame=N&​application_id=847398&​fcc_id='​PY312100186'​|here]] | 
 +| v5 | MediaTek MT7621ST | 128MiB | 128MiB | 1 WAN + 4x LAN (GBit) | ? | ? | ? | ? | ? | FCC ID PY314200275 |
  
-==== Hardware Highlights ==== +<WRAP left round important 80%> 
-^ Version ^ CPU ^ Ram ^ Flash ^ Network ^ USB ^ Serial ^ JTag ^ FCC ^ +Netgear has sold a number of these units in boxes marked WNDR37AV This was done for marketing purposes solely, the hardware is exactly identical to version ​(even to the point of many users finding a router physically labeled "​WNDR3700"​ or "​WNDR3700v2"​ inside of a box labeled "​WNDR37AV"​)
-| V1 | Atheros AR7161 rev 2 680 MHz | 64MiB | 8MiB | 4 x 1 | Yes | Yes | Yes | [[https://​apps.fcc.gov/​oetcf/​eas/​reports/​ViewExhibitReport.cfm?​mode=Exhibits&​RequestTimeout=500&​calledFromFrame=N&​application_id=278475&​fcc_id='​PY308300092'​|here]] | +</WRAP>
-| V2 | Atheros AR7161 rev 680 MHz | 64MiB | 16MiB | 4 x 1 | Yes | Yes | Yes | [[https://​apps.fcc.gov/​oetcf/​eas/​reports/​ViewExhibitReport.cfm?​mode=Exhibits&​RequestTimeout=500&​calledFromFrame=N&​application_id=290558&​fcc_id='​PY308300092'​|here]] | +
-| V3 | Broadcom BCM4718A1 ​ | 64MiB | 8MiB | 4 x 1 | Yes | ? | ? | [[https://​apps.fcc.gov/​oetcf/​eas/​reports/​ViewExhibitReport.cfm?​mode=Exhibits&​RequestTimeout=500&​calledFromFrame=N&​application_id=651807&​fcc_id=%27PY311200166%27|here]] | +
-| V4 | Atheros AR9344 @ 560 MHz | 128MiB | 128MiB | 4x1 | Yes | Yes | Yes | [[https://​apps.fcc.gov/​oetcf/​eas/​reports/​ViewExhibitReport.cfm?​mode=Exhibits&​RequestTimeout=500&​calledFromFrame=N&​application_id=847398&​fcc_id=%27PY312100186%27|here]] |+
  
 ==== Supported Versions ==== ==== Supported Versions ====
-Version/​Model ^ Launchdate ^ S/N OpenWrt Version ​Supported ^ Model Specific ​Notes ^ +Ver ^ Supported ​since ^ Notes ^ 
-| v1 |         ​|  ​| Backfire | aka WNDR37AV-100PES,​ WNDR3700-100PES ​ | +| v1 | Backfire ​10.03.1 ​| aka WNDR37AV-100PES,​ WNDR3700-100PES ​ | 
-| v2 | 2011-01 |  ​| Backfire 10.03.1 | Box side panel lists WNDR3700**v2**,​ aka WNDRMAC-100PES,​ WNDR3700-100prs  ​+| v2 | Backfire 10.03.1 | Box side panel lists WNDR3700**v2**,​ aka WNDRMAC-100PES,​ WNDR3700-100PRS ​
-wndr3800 ​2011-03 ​ | Backfire 10.03.1  | the [[toh:​netgear:​WNDR3800]] is the actual successor board  ​+v3 <color red>Not supported</​color> ​Broadcom SoC, preliminar support in trunkOnly 2,4 GHz wireless supported. YMMV. | 
-v3 2011-09? ​ | ? | WNDR3700**v3** is based on a Broadcom chip, so **completely different architecture than v1 or v2** | +v4 Barrier Breaker 14.07 Atheros platform like v1 and v2, NAND flash, same PCB as [[toh:​netgear:​WNDR4300]],​ but only 2T2R. See also [[https://​forum.openwrt.org/​viewtopic.php?​id=41094|this forum thread]]. May be labeled as WNDR3700-100PES on the packaging'​s side panel (like some v1 models). |  
-| V4 | ? | | WIP? | WNDR3700**v4** is again Atheros-basednow AR9344 with 128MiB RAM and 128MiB ​NAND flash. Same PCB as [[toh:​netgear:​WNDR4300]],​ but only 2T2R. [[https://​forum.openwrt.org/​viewtopic.php?​id=41094|OpenWrt Forum thread]] | +| v5 | <color red>Not supported</​color>​ | See [[https://​forum.openwrt.org/​viewtopic.php?​id=56737|this forum thread]] for info and actual status. ​|
  
-If you want to know what version you have after installing OpenWrt you can run <code>​dmesg | grep m25p80</​code> and then take a look in the hardware table (ver1 has 8 MiB , ver2 has 16 MiB).+<WRAP left round important 80%> 
 +You can not tell the version number by looking at the revision number. V1 and v2 seem to share the same EAN barcodes. [[http://​forum1.netgear.com/​showthread.php?​t=63234|Here]] you can read how to determine your versions within Netgear'​s firmware. Another way is to look at the box your router came in - under "​Package Contents"​ it will say "N600 Wireless Dual Band Gigabit Router ​(WNDR3700**v2**)" for version 2, and plain WNDR3700 for version 1. 
 +</​WRAP>​
  
-You can not tell the version number ​of the router by looking at the revision number as there is no logicand the versions even have the same EAN bar codes The only way to tell from the box which version ​you are buying ​is that on the side panel, under "Package Contents"​ it will say "N600 Wireless Dual Band Gigabit Router (WNDR3700**v2**)"​ for version ​2, and plain WNDR3700 for version 1.+<WRAP left round info 80%> 
 +There are rumours that a certain batch of version 1 routers have problems with the 2,4 GHz radio suddenly dying. These came in boxes marked as -01R14 or -01R15 on the barcode labelIt is also said that -01R21 or -02R01 are expected ​to be working o.k. Board version ​is said to be reliable. If you look at the pictures you may see at least 3 places with some kind of "​version" numbering. ​ See [[http://​spreadsheets.google.com/​pub?​key=0AjNDNODfzgytdEJvZ0N0SkFLejFJZzBHcnFaaUg4OGc&​hl=en&​output=html|this spreadsheet]]. 
 +</​WRAP>​
  
 +===== Downloading =====
  
-{{:toh:netgear:netgearwndr3700v1v2.jpg?800}}+^ Version ^ Download link ^ 
 +| v1 (North America) | http://​downloads.openwrt.org/​barrier_breaker/​14.07/​ar71xx/​generic/​openwrt-ar71xx-generic-wndr3700-squashfs-factory-NA.img | 
 +| v1 (rest of the world) | http://​downloads.openwrt.org/​barrier_breaker/​14.07/​ar71xx/​generic/​openwrt-ar71xx-generic-wndr3700-squashfs-factory.img | 
 +| v2 | http://​downloads.openwrt.org/​barrier_breaker/​14.07/​ar71xx/​generic/​openwrt-ar71xx-generic-wndr3700v2-squashfs-factory.img | 
 +| v3 | http://​downloads.openwrt.org/​barrier_breaker/​14.07/​brcm47xx/​mips74k/​openwrt-wndr3700_v3-squashfs.chk | 
 +| v4 | http://​downloads.openwrt.org/​barrier_breaker/​14.07/​ar71xx/​nand/​openwrt-ar71xx-nand-wndr3700v4-ubi-factory.img |
  
 +The files ending with ''​-sysupgrade.bin''​ are for upgrading existing OpenWrt installations.
  
-**NOTE:** There are rumors that a certain batch of version 1 routers have problems with the 2.4GHz radio suddenly dying. The ones came in boxes marked as -01R14 or -01R15 on the barcode label. It is also said that -01R21 or -02R01 are expected to be working o.k. According to "board verion"​ Ver4 is said to be reliable. If you look at the pictures you may see at least 3 places with some kind of "​version"​ numbering. ​ See [[http://​spreadsheets.google.com/​pub?​key=0AjNDNODfzgytdEJvZ0N0SkFLejFJZzBHcnFaaUg4OGc&​hl=en&​output=html]].+To create your own customized firmware, ​see [[doc:howtobuild:​build.wndr3700]].
  
-Added Notice: +===== Installation =====
-A thread on netgears forum telling how to see firmware and version of a router. +
-http://​forum1.netgear.com/​showthread.php?​t=63234 +
- +
-===== Basic Operation ===== +
- +
-==== Installation ==== +
-=== Support for the different versions of WNDR3700 === +
-  * Version 1 of this device is supported in Backfire 10.03 and above (Attitude Adjustment and trunk). Manually building OpenWrt is not required. Quickest way is to download a precompiled [[http://​downloads.openwrt.org/​backfire/​10.03.1/​ar71xx/​|stable image]], look for wndr3700 factory (SquashFS is recommended):​ +
-    * openwrt-ar71xx-wndr3700-squashfs-factory.img +
-    * openwrt-ar71xx-wndr3700-jffs2-factory.img +
-  * Version 2 is supported since 10.03.1: +
-    * [[http://​downloads.openwrt.org/​backfire/​10.03.1/​ar71xx/​]] +
-  * Version 3 is not yet supported by OpenWrt. +
-  * [[WNDR3800]] is supported since 10.03.1. +
-  * There are separate images for wndr3700, wndr3700v2 and wndr3800 (due to the firmware having to be tagged a different way). The wndr3700v2 will reject the version 1 images. +
- +
-=== Where to get firmware? ​=== +
- +
-  * You can get generic OpenWRT firmware of the [[about:​history#​stable.releases|stable branch]] from the [[http://​downloads.openwrt.org/​|official repository]]. This firmware covers most basic needs of an average user. +
-  * Alternative is a precompiled image from the [[about:​history#​bleeding.edge.trunk|trunk (bleeding edge) branch]]: [[http://​downloads.openwrt.org/​snapshots/​trunk/​ar71xx/​]]. +
-  * An easy way to get a custom firmware with extended functionality is to use a [[toh:​netgear:​wndr3700#​pre-built.customized.firmware|pre-built customized firmware]] based on either [[about:​history#​bleeding.edge.trunk|trunk]] or [[about:​history#​stable.releases|stable]] branch. +
-  * To create your own customized firmware, see this HowTo here: [[doc:​howtobuild:​build.wndr3700]]. +
- +
-:!: Developers recommend the SquashFS versions! Read about differences here: [[doc:​techref:​filesystems]]. And if you are interested, you can read about the differences between img and bin here: .+
  
 === How to flash the firmware to device? === === How to flash the firmware to device? ===
 Please consult ->​[[doc:​howto:​generic.flashing|Installing OpenWrt (generic)]] and additionally read on here for WNDR3700 specifics. Please consult ->​[[doc:​howto:​generic.flashing|Installing OpenWrt (generic)]] and additionally read on here for WNDR3700 specifics.
- 
-There are two different images available for the wndr3700 series: 
-  * **sysupgrade.bin** images are meant for flashing from an existing Openwrt system, either by using LuCI and the sysupgrade script. 
-  * **factory.img** images are otherwise identical, but a short header has been added to the image enabling the original Netgear OEM firmware and the TFTP recovery mode to accept the images. 
  
 == OEM easy installation == == OEM easy installation ==
Line 92: Line 77:
 </​code>​ </​code>​
  
-=== Upgrading ​OpenWrt ​=== +===== Upgrading ​===== 
-->[[doc:​howto:​generic.sysupgrade]]+See [[doc:​howto:​generic.sysupgrade]].
  
-==== Basic configuration ​==== +===== Configuration ===== 
-->[[doc:​howto:​basic.config|Basic configuration]]+See [[doc:​howto:​basic.config]].
- +
-=== Enabling wireless === +
-**NOTE:** For information on possible wireless regulatory issues, please refer to [[toh:​netgear:​wndr3700#​Wireless Regulatory Issues?​|this section]]. +
- +
-At least the Backfire 10.03 image (openwrt-ar71xx-wndr3700-squashfs-factory.img 06-Apr-2010 2424965) does not have working wireless out of the box as some kernel modules are missing for the wireless chipset, however this is easy to remedy. ​ SSH to your router (you will first need to telnet in and set a password, as described in [[doc/​howto/​firstlogin|First Login]], and then run the following commands (assumes the router has Internet access): +
- +
-<​code>​ +
-# opkg update +
-# opkg install kmod-ath9k wpad-mini +
-</​code>​ +
- +
-Now, restart the router.+
  
 ===== Advanced Operation ===== ===== Advanced Operation =====
Line 119: Line 92:
 Typically, these builds are intended to extend functionality and/or to improve performance of the firmware, as well as provide the end-user with a preconfigured setup. Typically, these builds are intended to extend functionality and/or to improve performance of the firmware, as well as provide the end-user with a preconfigured setup.
  
-**Warning**:​ As custom builds are mostly based on the [[about:​history#​bleeding.edge.trunk|trunk (bleeding edge) branch]], they are much more prone to bugs and regressions.+**Warning**:​ As custom builds are mostly based on the [[about:​history#​bleeding_edgetrunk|trunk (bleeding edge) branch]], they are much more prone to bugs and regressions.
  
 In order to address this, some members also release builds based on the [[about:​history#​stable.releases|stable branch]], thus reducing the potential of regressions,​ yet providing the advantages of customization (check out the link to hnyman'​s build below). In order to address this, some members also release builds based on the [[about:​history#​stable.releases|stable branch]], thus reducing the potential of regressions,​ yet providing the advantages of customization (check out the link to hnyman'​s build below).
  
-Specifically for WNDR3700, these are the longer maintained and the more frequently updated builds (as of September24 2012): +Specifically for WNDR3700, these are the longer maintained and the more frequently updated builds (as of January2015):
- +
-[[https://​forum.openwrt.org/​viewtopic.php?​id=27722|Fully featured OpenWrt build for the WNDR3700]] (managed by arokh; trunk-only builds) +
- +
-[[https://​forum.openwrt.org/​viewtopic.php?​id=28392|IPv6 oriented Openwrt build for WNDR3700]] (managed by hnyman; trunk and stable builds)+
  
 +  * [[https://​forum.openwrt.org/​viewtopic.php?​id=28392|IPv6 oriented Openwrt build for WNDR3700]] (managed by hnyman; trunk and stable builds)
 +  * [[https://​forum.openwrt.org/​viewtopic.php?​id=47382|OpenWRT builds (BB) fully featured for various routers]] (managed by mk13139; trunk and stable builds)
 +  * [[https://​forum.openwrt.org/​viewtopic.php?​id=27722|Fully featured OpenWrt build for the WNDR3700]] (managed by arokh; trunk-only builds) (no longer maintained since November 2012)
 +  * [[https://​forum.openwrt.org/​viewtopic.php?​id=50914|Optimized and feature rich trunk build for select routers]] (managed by arokh; trunk-only builds)
 ==== Flash Layout ==== ==== Flash Layout ====
 ->​[[doc:​techref:​flash.layout]] ->​[[doc:​techref:​flash.layout]]
Line 143: Line 116:
  
 === Switch Ports (for VLANs) === === Switch Ports (for VLANs) ===
 +:!: There seems to be an issue with the internal switch. I've observed this with all kinds of laptops and OS's on a dozen access points. The problem is that sometimes traffic with a destination of a wifi client will no longer be routed to it, leading to a non-working wifi client. My advice would be to uncheck '​learning and aging' under Network -> Switch in LUCI, although this effectively may turn your switch into a hub. See https://​dev.openwrt.org/​ticket/​13612
 +
 Numbers 0-3 are Ports 4 to 1 as labeled on the unit, 5 is the internal connection to the router itself. Don't be fooled: Port 1 on the unit is number 3 when configuring VLANs. vlan0 = eth0.0, vlan1 = eth0.1 and so on. Numbers 0-3 are Ports 4 to 1 as labeled on the unit, 5 is the internal connection to the router itself. Don't be fooled: Port 1 on the unit is number 3 when configuring VLANs. vlan0 = eth0.0, vlan1 = eth0.1 and so on.
 ^ Port ^ Switch port ^ ^ Port ^ Switch port ^
Line 173: Line 148:
 Switch port numbering is other way around from physical ports. Switch port numbering is other way around from physical ports.
  
-|''​config interface lan+<​code>​ 
 +config interface lan
  option ifname eth0.1  option ifname eth0.1
  option type bridge  option type bridge
Line 212: Line 188:
  option vlan 4  option vlan 4
  option ports "​0 5t"  option ports "​0 5t"
-''​|+</​code>​ 
 + 
 +**Note:** The VLAN switch configuration in Attitude Adjustment 12.09 has a bug ( https://​dev.openwrt.org/​ticket/​7795 ), so that you need to first disable VLAN trunk and than reenable it like this: 
 + 
 +<​code>​ 
 +# swconfig dev rtl8366s vlan 1 set ports '0 1 2 3t 5' 
 +# swconfig dev rtl8366s vlan 1 set ports '0 1 2 3t 5t' 
 +</​code>​
  
 Note: The switch ports are not properly shown in the Backfire 10.03.1-rc4 Luci-interface,​ unless you add the chip name to the '​config switch'​ line: like '​config switch rtl8366s'​. After making that addition, Luci shows the VLANs properly at the Network/​Switch page. (Reference: https://​dev.openwrt.org/​ticket/​7830 ) Note: The switch ports are not properly shown in the Backfire 10.03.1-rc4 Luci-interface,​ unless you add the chip name to the '​config switch'​ line: like '​config switch rtl8366s'​. After making that addition, Luci shows the VLANs properly at the Network/​Switch page. (Reference: https://​dev.openwrt.org/​ticket/​7830 )
Line 250: Line 233:
  
 Note: The default LED config built into Backfire 10.03.1-rc4 (and earlier) does not match the explanation printed on the router'​s bottom. To make the LED behaviour match the printed explanation (green LED for 1000Mb/s), use mode 6 for port 1, mode 9 for port 2 and mode 2 for port 5. This has later been patched to [[about:​history#​bleeding.edge.trunk|trunk (bleeding edge)]] and Backfire branch. You can either use the swconfig command or directly edit the file '/​etc/​config/​network'​. Reference: https://​dev.openwrt.org/​ticket/​8103 Note: The default LED config built into Backfire 10.03.1-rc4 (and earlier) does not match the explanation printed on the router'​s bottom. To make the LED behaviour match the printed explanation (green LED for 1000Mb/s), use mode 6 for port 1, mode 9 for port 2 and mode 2 for port 5. This has later been patched to [[about:​history#​bleeding.edge.trunk|trunk (bleeding edge)]] and Backfire branch. You can either use the swconfig command or directly edit the file '/​etc/​config/​network'​. Reference: https://​dev.openwrt.org/​ticket/​8103
 +
 +=== Deactivate all LEDs ===
 +Put below in rc.local
 +<​code>​
 +for i in /​sys/​class/​leds/​* ; do echo 0 > "​$i"/​brightness;​ done
 +for i in 0 1 2 3 4; do swconfig dev switch0 port $i set led 0; done
 +</​code>​
  
 === Activate USB LED in Backfire === === Activate USB LED in Backfire ===
Line 256: Line 246:
 Add a USB LED configuration entry to /​etc/​config/​system (you can edit the file manually or use Luci/​System/​LED_Configuration page)  Add a USB LED configuration entry to /​etc/​config/​system (you can edit the file manually or use Luci/​System/​LED_Configuration page) 
  
-|''​config '​led'​+<​code>​ 
 +config '​led'​
  option '​name'​ 'USB LED'  option '​name'​ 'USB LED'
  option '​sysfs'​ '​wndr3700:​green:​usb'​  option '​sysfs'​ '​wndr3700:​green:​usb'​
  option '​default'​ '​0'​  option '​default'​ '​0'​
-''​|+</​code>​
  
 But that still just adds a default state to the LED. The LED will not yet turn itself on. You need to create an entry for the hotplug config: ​ But that still just adds a default state to the LED. The LED will not yet turn itself on. You need to create an entry for the hotplug config: ​
Line 267: Line 258:
  
 Code for the file /​etc/​hotplug.d/​usb/​10-usb :  Code for the file /​etc/​hotplug.d/​usb/​10-usb : 
-|''​#!/bin/sh+<code bash>#!/bin/sh
 # Copyright (C) 2009 OpenWrt.org # Copyright (C) 2009 OpenWrt.org
 case "​$ACTION"​ in case "​$ACTION"​ in
Line 278: Line 269:
         echo "​0"​ >/​sys/​devices/​platform/​wndr3700-led-usb/​leds/​wndr3700:​green:​usb/​brightness         echo "​0"​ >/​sys/​devices/​platform/​wndr3700-led-usb/​leds/​wndr3700:​green:​usb/​brightness
         ;;         ;;
-esac +esac</​code>​
-''​|+
  
 The LED should now react to inserting/​removing USB devices. ​ The LED should now react to inserting/​removing USB devices. ​
Line 381: Line 371:
  
 === Info === === Info ===
-| **[[wp>​Instruction set|Architecture]]:​** ​   | [[wp>​MIPS architecture|MIPS]] | +^ ^ v1 ^ v2 ^ v3 ^ v4 ^ 
-| **Vendor:​** ​         | [[wp>​Qualcomm Atheros]] ​ +| **[[wp>​Instruction set|Architecture]]:​** ​   | [[wp>​MIPS architecture|MIPS]] ​|||
-| **[[doc:​techref:​Bootloader]]:​** ​    | crippled [[doc:​techref:​bootloader:​uboot|U-Boot]] | +| **Vendor:​** ​         | [[wp>​Qualcomm Atheros]] ​| [[wp>​Qualcomm Atheros]] | Broadcom | [[wp>​Qualcomm Atheros]] ​
-| **[[doc:​hardware:​soc|System-On-Chip]]:​** ​ | [[http://​www.qca.qualcomm.com/​networking/​brand.php?​brand=4&​product=68|AR7161 ]] | +| **[[doc:​techref:​Bootloader]]:​** ​    | crippled [[doc:​techref:​bootloader:​uboot|U-Boot]] ​|||
-| **[[doc:​hardware:​cpu|CPU]]/​Speed** ​       | [[http://​www.mips.com/​products/​processor-cores/​mips32-24k/​|MIPS32 24Kc]] V7.4 680 MHz   ​(([[http://​www.mips.com/​secure-download/​index.dot?​product_name=/​auth/​MD00346%2D2B%2D24K%2DDTS%2D04.00.pdf|Datasheet specific to the 24Kc CPU core (free registration required)]])) | +| **[[doc:​hardware:​soc|System-On-Chip]]:​** ​ | [[http://​www.qca.qualcomm.com/​networking/​brand.php?​brand=4&​product=68|AR7161 ]] || Broadcom | AR9344 ​
-| **Flash-Chip:​** ​ | v1: [[http://​www.spansion.com/​Support/​Datasheets/​S25FL064P_00_03_e.pdf|Spansion S25FL064P (FL064PIF)]] or [[http://​www.macronix.com/​QuickPlace/​hq/​PageLibrary4825740B00298A3B.nsf/​$defaultview/​3F21BAC2E121E17848257639003A3146/​$File/​MX25L6405D%2C%203V%2C%2064Mb%2C%20v1.5.pdf?​OpenElement|Macronix MX25L6405DMI-12G]], v2: [[http://​www.macronix.com/​QuickPlace/​hq/​PageLibrary4825740B00298A3B.nsf/​$defaultview/​3F21BAC2E121E17848257639003A3146/​$File/​MX25L12845E%2C%203V%2C%20128Mb%2C%20v1.7.pdf|Macronix MX25L12845EWI-10G]] | +| **[[doc:​hardware:​cpu|CPU]]/​Speed** ​       | [[http://​www.mips.com/​products/​processor-cores/​mips32-24k/​|MIPS32 24Kc]] V7.4 680 MHz   ​(([[http://​www.mips.com/​secure-download/​index.dot?​product_name=/​auth/​MD00346%2D2B%2D24K%2DDTS%2D04.00.pdf|Datasheet specific to the 24Kc CPU core (free registration required)]])) ​| | | 
-| **Flash size:​** ​     | v1 has 8192 KiB, v2 has 16384 KiB | +| **Flash-Chip:​** ​ | v1: [[http://​www.spansion.com/​Support/​Datasheets/​S25FL064P_00_03_e.pdf|Spansion S25FL064P (FL064PIF)]] or [[http://​www.macronix.com/​QuickPlace/​hq/​PageLibrary4825740B00298A3B.nsf/​$defaultview/​3F21BAC2E121E17848257639003A3146/​$File/​MX25L6405D%2C%203V%2C%2064Mb%2C%20v1.5.pdf?​OpenElement|Macronix MX25L6405DMI-12G]] ​|  ​[[http://​www.macronix.com/​QuickPlace/​hq/​PageLibrary4825740B00298A3B.nsf/​$defaultview/​3F21BAC2E121E17848257639003A3146/​$File/​MX25L12845E%2C%203V%2C%20128Mb%2C%20v1.7.pdf|Macronix MX25L12845EWI-10G]] ​| ? | ? 
-| **RAM-Chip:​** ​       | 2X [[http://​www.nanya.com/​NanyaAdmin/​GetFiles.ashx?​ID=116|Nanya NT5DS16M16CS-5T]] | +| **Flash size:​** ​     | 8192 KiB 16384 KiB |8192 KiB | 128 MiB NAND 
-| **RAM:​** ​            | 64 MiB   ​+| **RAM-Chip:​** ​       | 2X [[http://​www.nanya.com/​NanyaAdmin/​GetFiles.ashx?​ID=116|Nanya NT5DS16M16CS-5T]] ​| ? | ? | ? 
-| **Wireless:​** ​       | Atheros AR9223 802.11bgn / Atheros AR9220 802.11an | +| **RAM:​** ​            | 64 MiB ||| 128 MiB 
-| **Ethernet:​** ​       | [[http://​realtek.info/​pdf/​rtl8366_8369_datasheet_1-1.pdf|Realtek RTL8366SR]] ​ +| **Wireless:​** ​       | Atheros AR9223 802.11bgn / Atheros AR9220 802.11an ​| ? | ? | ? 
-| **Internet:​** ​       | n/a  | +| **Ethernet:​** ​       | [[http://​realtek.info/​pdf/​rtl8366_8369_datasheet_1-1.pdf|Realtek RTL8366SR]] ​| ? | ? | ? 
-| **USB:​** ​            | Yes 1 x 2.0    +| **Internet:​** ​       | n/​a  ​|||
-| **Serial:​** ​         | [[#​Serial|Yes]] ​  ​+| **USB:​** ​            | Yes 1 x 2.0 |||
-| **JTAG:​** ​           | [[#​JTAG|Yes]] ​ +| **Serial:​** ​         | [[#​Serial|Yes]] ​|||
-| **Voltage Reg:​** ​    | [[#​VReg|Yes]] ​ | +| **JTAG:​** ​           | [[#​JTAG|Yes]] ​|||
 +| **Voltage Reg:​** ​    | [[#​VReg|Yes]] ||||
  
 === Photos === === Photos ===
Line 600: Line 590:
 === Antenna Mod === === Antenna Mod ===
  
-Need 4 U.FL connector, 4 cable UFL-F/RPSMA-F 13 centimeters long4 Antenna Level One (OAN-0501).+The procedure below covers hardware revision 1. Revision 2 only has U.FL connectors for the 5 GHz antennas (PJ2 and PJ4)while the 2.GHz connectors are replaced with dummy connectors (presumably a Hirose testing connectors used in production). So for revision 2 the PJ5 and PJ6 connectors will have to bypassed and the coax cable soldered directly to the PCB. 
 + 
 +You will need: 
 +  * 4 cable U.FL-F (female) to RPSMA-F ​(female) app. 13 centimeters long 
 +  * 4 Antenna ​(preferably 2 2.4 GHz and 2 5 GHz antenna), e.g. Level One (OAN-0501).
  
 On board removes: On board removes:
Line 628: Line 622:
 {{:​toh:​netgear:​img_1205.jpg?​243x162|Netgear WNDR3700 v1 Antenn Mod}} {{:​toh:​netgear:​img_1205.jpg?​243x162|Netgear WNDR3700 v1 Antenn Mod}}
 {{:​toh:​netgear:​img_1209.jpg?​243x162|Netgear WNDR3700 v1 Antenn Mod}} {{:​toh:​netgear:​img_1209.jpg?​243x162|Netgear WNDR3700 v1 Antenn Mod}}
- 
  
 ===== Troubleshooting and Recovery ===== ===== Troubleshooting and Recovery =====
Line 634: Line 627:
 ==== Wireless Regulatory Issues? ==== ==== Wireless Regulatory Issues? ====
 Unless you are American, BOTH 2.4GHz and 5GHz will likely not be fully available on OpenWrt 10.03 Backfire (you will experience loss of channels 12, 13 and 14 if these are available where you are, as well as potentially incorrect 5GHz channel availability. Power output levels may be incorrect for your country as well). Unless you are American, BOTH 2.4GHz and 5GHz will likely not be fully available on OpenWrt 10.03 Backfire (you will experience loss of channels 12, 13 and 14 if these are available where you are, as well as potentially incorrect 5GHz channel availability. Power output levels may be incorrect for your country as well).
 +
 +FIXME Does this problem still exist in version 12.x? I'm using Barrier Breaker r36692+ and I don't have to manually download any sort of file as mentioned below. Just be sure to configure your country in the web interface (LUCI) under Network -> Wifi -> your wifi (EDIT) -> Advanced settings -> Country code, or manually set wireless.radio0.country and wireless.radio1.country and restart wifi. If I choose '​NL'​ for The Netherlands it makes channel 13 available perfectly fine.
  
 To sum up the background for this: To sum up the background for this:
Line 642: Line 637:
  
 Personally, I think this is a ridiculous situation, but there seem to be issues with fixing it. You can do the job yourself as follows: Personally, I think this is a ridiculous situation, but there seem to be issues with fixing it. You can do the job yourself as follows:
 +
 +=== Backfire ===
  
 You may partially fix this by compiling a custom image with CONFIG_ATH_USER_REGD set in the Ath9k driver. This will, however, take a significant time to compile and result in a restriction to 20dBm max power output across all channels (this is apparently due to a bug according to my reading, but it's not fixed yet as far as I can tell). A much better option that will allow you to use the full legal power output in your country would be to follow the instructions here: You may partially fix this by compiling a custom image with CONFIG_ATH_USER_REGD set in the Ath9k driver. This will, however, take a significant time to compile and result in a restriction to 20dBm max power output across all channels (this is apparently due to a bug according to my reading, but it's not fixed yet as far as I can tell). A much better option that will allow you to use the full legal power output in your country would be to follow the instructions here:
Line 685: Line 682:
  
 4. If you want to see what settings I put in the regulatory DB (they'​re as per the article I linked at the beginning) you can get them here: https://​rapidshare.com/​files/​458836748/​db.txt . If for some reason you want to use this to set the proper regulatory settings for the USA, you need to use UX as the country code...otherwise all country codes are still correct. 4. If you want to see what settings I put in the regulatory DB (they'​re as per the article I linked at the beginning) you can get them here: https://​rapidshare.com/​files/​458836748/​db.txt . If for some reason you want to use this to set the proper regulatory settings for the USA, you need to use UX as the country code...otherwise all country codes are still correct.
 +
 +=== Attitude Adjustment ===
 +SSH to the router and run the following:
 +
 +<​code>​
 +cd /tmp/
 +wget http://​luci.subsignal.org/​~jow/​reghack/​old/​reghack.mips.elf
 +chmod +x reghack.mips.elf ​
 +cp /​lib/​modules/​*/​ath.ko .
 +cp /​lib/​modules/​*/​cfg80211.ko .
 +./​reghack.mips.elf ath.ko
 +./​reghack.mips.elf cfg80211.ko
 +mv *.ko /​lib/​modules/​*/​
 +reboot
 +</​code>​
 +
 +=== OpenWrt Trunk ===
 +SSH to the router and run the following:
 +
 +<​code>​
 +cd /tmp/
 +wget http://​luci.subsignal.org/​~jow/​reghack/​reghack.mips.elf
 +chmod +x reghack.mips.elf ​
 +cp /​lib/​modules/​*/​ath.ko .
 +cp /​lib/​modules/​*/​cfg80211.ko .
 +./​reghack.mips.elf ath.ko
 +./​reghack.mips.elf cfg80211.ko
 +mv *.ko /​lib/​modules/​*/​
 +reboot
 +</​code>​
 +
 +==== Known problems/​issues (stability) ====
 +While the WNDR3700 (and WNDR3800) are great routers, there have been a number of issues with them. Some have been recently fixed, others are still present. Note that most of these issues are related to the Atheros chipset and are not unique to the WNDR3700.
 +Here's a short list of major issues:
 +  * Wifi stopped working after a while (fixed in AA 12.09 in April 2013, https://​dev.openwrt.org/​ticket/​11894)
 +  * Problems with internal switch causing traffic to a particular wifi client to be ignored (workaround present, https://​dev.openwrt.org/​ticket/​13612)
 +  * Failed to stop TX DMA messages in syslog (in AA 12.09 and later these are likely harmless and can be ignored, https://​dev.openwrt.org/​ticket/​11862)
 +  * For more issues, you can search on tickets at http://​dev.openwrt.org/​ for "​wndr3700"​ or the chipset (usually "​ar71"​)
 +
 +:!: Previous versions had major trouble with regards to stability in an office environment. Starting with AA 12.09 however, combined with the internal switch workaround mentioned above, these access points seem finally stable. I (Syzop) use around 20 of these on a high school which are used intensively with many associate/​disassociate events.
  
 ==== Recovery flash in failsafe mode ==== ==== Recovery flash in failsafe mode ====
Line 740: Line 777:
  
 ---- ----
 +
 +===== Resources =====
 +  - OEM source code and toolchain: ftp://​downloads.netgear.com/​files/​GPL/​
 +
 +===== Custom OpenWrt image with LuCi integrated =====
 +
 +http://​www.superwrt.eu/​en/​firmware/​netgear-wndr3700/​
 +
 +
  
 ===== Tags ===== ===== Tags =====
 [[meta:​tags]] [[meta:​tags]]
-{{tag>​GigabitEthernet 5Port 2PHY USB 1USB JTAG 802.11abgn 802.11abgn_simultan ath9k 4Ant DetachableAntenna 64RAM 16Flash MIPS MIPS32 24Kc}}+{{tag>​GigabitEthernet 5Port 2NIC USB 1USB JTAG 802.11abgn 802.11abgn_simultan ath9k 4Ant DetachableAntenna 64RAM 16Flash MIPS MIPS32 24Kc}}
toh/netgear/wndr3700.1360427918.txt.bz2 · Last modified: 2013/02/09 17:38 by mandrawes