Netgear WNDR3300v1

Netgear WNDR3300 v1
Availability: EoL

Manuf (OEM/ODM): Foxconn U12H093

FCC approval date: 02 January 2008
UPC: 606449055078 (UPC DB, On eBay)
Country of manuf.: China

Amazon image

ASIN
B0017TFVUW (, On Amazon, On CCC)
multiple revisions of this device, use caution

Type: wireless router

FCC ID: PY307300072, PY308100078
IC ID: 4054A-07300072

Power: 12 VDC, 1.5 A
Connector type: barrel
Conn. measurements: 5.5 mm (OD), 2.1 mm (ID), 9.5 mm (LEN)

CPU1: Broadcom BCM4704 (264 MHz)
FLA1: 4 MiB4,194,304 B <br />32,768 Kib <br />4,096 KiB <br />32 Mib <br />0.00391 GiB <br /> (Macronix MX29LV320DBTI-70G)
RAM1: 16 MiB16,777,216 B <br />131,072 Kib <br />16,384 KiB <br />128 Mib <br />0.0156 GiB <br /> (Nanya NT5DS8M16FS-5T)

Expansion IFs: none specified
Serial: yes

WI1 chip1: Broadcom BCM4321
WI1 chip2: Broadcom BCM2055
WI1 802dot11 protocols: abgn
WI1 MIMO config: 2x2:2
WI1 antenna connector: none
WI2 chip1: Broadcom BCM4318
WI2 802dot11 protocols: bg
WI2 antenna connector: none

ETH chip1: Broadcom BCM4704
Switch: Broadcom BCM5325F
LAN speed: 100M
LAN ports: 4
WAN speed: 100M
WAN ports: 1

abgn

TPFirmware supported: DD-WRT • (List), OpenWrt • (List | Dev | DLs)

Flags: DFS

Default SSID: NETGEAR-DualBand-N (1 addl. devices)
, NETGEAR-2.4-G (1 addl. devices)
Default IP address: 192.168.1.1
the IP 192.168.1.1 is used by 1304 additional devices
of which 106 are Netgear devices
Default login user: admin
Default login password: password
admin:password credentials used by 423 additional devices
of which 304 are Netgear devices

802dot11 OUI: 00:1F:33 (8 E, 12 W), 00:22:3F (10 E, 12 W), 00:24:B2 (14 E, 16 W), 00:26:F2 (10 E, 10 W), C0:3F:0E (14 E, 12 W)
Ethernet OUI: 00:1F:33 (8 E, 12 W), 00:22:3F (10 E, 12 W), 00:24:B2 (14 E, 16 W), 00:26:F2 (10 E, 10 W), C0:3F:0E (14 E, 12 W)

	CPU1 brand	WI1 chip1 brand	WI2 chip1 brand
Netgear WNDR3300v1	Broadcom	Broadcom	Broadcom
Netgear WNDR3300v2	Broadcom	Broadcom	Broadcom

For a list of all currently documented Broadcom chipsets with specifications, see Broadcom.

---

RangeMax Dual Band Wireless-N Router

 • Support page

• Manuf. by Foxconn / Hon Hai / Ambit, model U12H093T00

The default SSIDs are NETGEAR-DualBand-N for the 5GHz N radio

and NETGEAR-2.4-G for the 2.4GHz b/g radio.

The device has multiple FCC IDs..

but the router with the FCC ID of PY308100078 has an IC ID of 4054A-07300072.

There does not appear to be any obvious difference between the filings.

The power adapter included with the device is a NETGEAR P/N: 332-10114-01

Model: AD661F (12V, 1.5A). ID/OD/Len measurements are approximate.

Links

• On the DD-WRT wiki
• On the OpenWrt wiki

Links of Interest

This is a work in progress!

Credits to many posters in the various WNDR3300 threads as some material here is cut and pasted.

Note that most of the information posted here is valid as of 02/01/2010.

• New Netgear WNDR3300 support - one of the original main support threads.
  • It is locked and is available for historical reference.
  • Please start a new thread for any support requests not already active.
• Peacock Thread READ THIS FIRST - YES IT IS OVER EMPHASIZED FOR A REASON
• Firmware Recommendations - look here for the most recent and reasonably known stable release information
• OpenWrt wiki information about this router - (note: external link) additional hardware level information about the router
• WLAN available channels - (note: external link) list of channels for 2.4 GHz and 5 GHz bands along with country availability
• 2.4 GHz Wireless-N Configuration
• Netgear WNDR3300 5 GHz Support
• WNDR 3300 - how to get max speed on 5 GHz?
• Wireless-N Throughput Testing
• How to add external. ant
• WNDR3300 specific K26 k2.6
• WNDR3300 Brick - Will not take tftp flash (SOLVED!!)
• Commands WNDR3300
• VLAN trunk question

DD-WRT Common questions

Can I use NEWD or NEWD2 builds?

1. In general it has been recommended to stay with NEWD builds for most users as of Feb 2010.
2. Both builds can support 802.11n on the routers.
3. If you need to use both radios (wl0 and wl1), you should stay with NEWD builds.
4. NEWD2 has newer wireless drivers for Broadcom based routers that support 11n and posts on the forum indicate a performance advantage when using N. However, it appears you lose the ability to use the wl1 radio on these builds:
   • reference wiki entry: dd-wrt-wiki:NEWD2 Support on some models NEWD2 Support on some models (if this changes, someone should update this item)
   • be sure to research if it is still appropriate to use NEWD2 releases as DD-WRT is constantly evolving with updates

There are a gazillion different build versions. Which ones can I use?

1. Remember this router has a 4mbit flash chip. You can use most of the "std" (standard/generic) or "mini" builds and most of their sub variants from brainslayer or eko. *NEVER* use any of the micro or mega builds on this router - you will either neuter or brick it.
   1. It is now being reported that .bin files must be smaller than approximately 3648kb (3735552 bytes) in size, otherwise they will fail to flash. This means that Brainslayer builds released since about Dec 2009 will likely be too large.
2. if you are still using the factory Netgear firmware, there really is only one initial firmware you can load first. After that you can load other certain versions. See the separate section on flashing the WNDR3300 further down in this wiki entry.
3. WARNING! Even though the builds listed are classified as known to work, some versions (old and new) may not load due to the actual firmware bin file size. Please see the FLASHING section of this entry for more information.
4. if you like the brainslayer builds (search the wiki about the specific differences)
   1. dd-wrt.v24_std_generic.bin
      • suggested for most users as it has all the standard options included
   2. dd-wrt.v24_nokaid_generic.bin
      • for those that do not need xbox/kaid support and to save a little space on the flash
5. if you like eko builds, suggestions are:
   1. NEWD_std-nokaid.bin
      • NEWD builds for users who do not need xbox/kaid but like to have all of the other standard options. This will also save some space on your flash if you want to use jffs
   2. NEWD_std-nokaid_nohotspot_nostor.bin
      • NEWD builds for users who do not need xbox, hotspot or external/CIFS storage options to save space on your flash. This build leaves the most free flash space for JFFS in standard releases without having to step down to mini builds.
   3. NEWD_openvpn_jffs_small.bin
      • similar to the std nokaid_nohotspot_nostor version but with JFFS and OpenVPN support

I see builds for K24 and K26. What are the differences?

1. Basically that means builds are using the Linux kernals v2.4 (aka K24) or v2.6 (K26).
2. DD-WRT has been built on the K24 platform for many years and is proven quite stable. It is recommended that general users stay with these builds for the immediate future.
3. There is a movement to get DD-WRT on the more modern and supported 2.6 kernal recently - starting around late 2009. This will take some to get it fully stable. Note that only certain recent routers will be able to support these versions.
   1. If you have time and are will to help test these K26 versions, please do!
      • WARNING! Note that you should be an "advanced user" of DD-WRT if you plan to try K26 builds. Meaning, you know how to handle the router if you brick it.
      • As of Feb 2010, the possibility exists that some K26 builds may brick your router and require serial console access to recover. If you do not know what that means, DO NOT TRY the K26 builds.
   2. You can follow these threads for additional information:
      1. K26 Build Supported Router List
      2. WNDR3300 13575M NEWD-2 K2.6 Eko

The router is advertised as having dual radio support. What are my options on using them?

1. the main wireless radio dubbed "wl0" in DD-WRT supports two wireless bands: 2.4 GHz *or* 5 GHz (or disable it). You can pick from the following configuration for the wl0 radio:
   1. Disabled: radio is powered off
   2. Mixed: supporting 802.11b/g (11Mbps and 54Mbps on the 2.4 GHz band)
   3. B only: supporting 802.11b (11Mbps on the 2.4 GHz band)
   4. G only: supporting 802.11g (54Mbps on the 2.4 GHz band)
   5. N only-2.4: supporting 802.11n (up to 130Mbps on the 2.4 GHz band depending on the channel and width you pick)
   6. A only: supporting 802.11a (54Mbps on the 5 GHz band)
   7. NA-Mixed: supporting 802.11a and 802.11n (standard 54Mbps *and* up to 270Mbps on the 5 GHz band depending on the channel and width you pick)
   8. N only-5: supporting 802.11n (up to 270Mbps on the 5 GHz band depending on the channel and width you pick)
2. secondary wireless radio dubbed "wl1" in DD-WRT supports only one band: 2.4 GHz (or disable it)
   1. Disabled: radio is powered off
   2. Mixed: supporting 802.11b/g (11Mbps and 54Mbps on the 2.4 GHz band)
   3. B only: supporting 802.11g (11Mbps on the 2.4 GHz band)
   4. G only: supporting 802.11g (54Mbps on the 2.4 GHz band)

There are many posts about stability. What about it?

1. There are MANY users running this router in a variety of different environments and most have no or minimal issues. To be fair, some versions of DD-WRT have been better than others. However, the most recent firmware revisions have been stable in most typical setups. Exotic setups, like using WDS and client bridging, require additional care that may be discussed in other sections of this wiki entry.
2. Many posts with problems can be traced to not fully completing the flashing procedures - specifically the reset handling.
3. If your WAN port is dropping connections - this is not normal and would require troubleshooting that may generally apply to any router running DD-WRT
4. If the wireless connections are not stable (eg, regularly drops connections), there are any number of reasons for this that MAY NOT BE related to this router or DD-WRT itself.
5. I've tried all sorts of things and it still is not "stable"! This does not mean the refurb unit you bought from a link on a deal site is bad. Please review potential sections like power supply information, spend time and read through the various forum posts as someone may have had your issue before asking for help.

What kind of performance can I get from N on this router?

1. Some users have performed iperf testing. Results indicate N over 5 GHz looks very reasonable depending on the configuration and surrounding environment. Watch for future separate section in this wiki entry for benchmark information.
2. Remember that this router, by default, has internal antennas and that affects performance greatly for either band, but especially for N over 5 GHz.

Flashing

Flashing DD-WRT

• Netgear WNDR3300

IMPORTANT FLASHING PREREQUISITES

1. DO YOUR RESEARCH BEFORE BLINDLY FLASHING WITH ANY VERSION OF DD-WRT. THIS WIKI ENTRY IS JUST A STARTING POINT.
2. STOP! If you have not read the Peacock Thread, do so now before reading the rest of the wiki entry or asking for help in the forums.
3. WARNING! Confirm the file size of the *.bin file you are planning to use.
   • Although router has 4mb of flash, but no one has exactly listed what the approx threshold was for the firmware size you can use. Based on the OpenWRT wiki flash ROM partition sizing for this router, the max size bin firmware you can load should be:
   • 3735552 bytes or about 3648kb (the available partition size for linux and rootfs combined which equal what the firmware is)
   • If you try to load a *.bin file larger than this, the flash will fail and the router will remain in TFTP recovery mode. You can then load another smaller bin file.
     • eg, recent std-generic.bin files from Dec 2009 to Feb 2010 are over 30k too large to load
   • Some routers may have larger flashable space for firmware, however, this router has slightly reduced space then other 4mbit Broadcom units due to the flash partitioning the manufacturer is using

If you are running the factory Netgear firmware

1. you need to download a special dd-wrt "trailed" firmware package for this router: the *.chk file.
   • DO NOT USE THE 12-28-09 r13525 brainslayer chk build. This has been found by a user to have a bad checksum and will leave your router in recovery/tftp mode - see page 71 in the main support thread. Note that the regular (std/mini/generic/etc) *.bin files for this release appear to be fine though.
   • A known confirmed flashable version as of Feb 2010: 01-16-10-r13637/broadcom/dd-wrt.v24_std-wndr3300.chk
2. it is recommended you perform a reset to factory defaults (eg, 30/30/30 reset)
3. be sure to perform all firmware updates from a wired ethernet connection. Do not perform a firmware upgrade over the wireless.
4. hook up the router from one of the four available ethernet ports (do NOT use the WAN port) and connect the ethernet cable to a NIC (fast ethernet or gigabit) port on your computer.
5. if you have reset the Netgear firmware to factory settings, it is recommended you use a static IP address on the NIC:
   • IP address: 192.168.1.2
   • subnet mask: 255.255.255.0
   • gateway: 192.168.1.1
6. log in to the Netgear Web GUI. If you are running a Microsoft Windows OS, it is recommended you use Internet Explorer to perform the initial firmware upgrade to DD-WRT. You can use any other browser there after. Once you log in...
   • Click on "Router Upgrade" in the LEFT navigation side bar
   • Click on "Browse..." and select the .chk file firmware you wish to load or manually type in the filename
   • Click on "Upload"
   • You will get a prompt to "Continue? All existing Internet connections will be terminated"
   • Click on "OK" to proceed.
   • You will see the following screen appear:
     -----------------------
     Router Upgrade
     Warning! You are trying to upload a world wide firmware which is different from the NA firmware you had.
     Do you still want to continue?
     Current Version V1.0.XX_1.0.XXNA
     Uploaded Version V1.0.14_1.0.14
     -----------------------
   • Where "XX" is a version number. Typically 29 for most refurbs or 45 for fresh retail models.
   • Ignore the Uploaded Version "V1.0.14_1.0.14" string, this is just the version the original DD-WRT chk file uses so the Netgear firmware will accept the file.
   • Click on "Yes" to initiate the update.
   • You will see the following message:
     Note:It will take about 1.5 minutes for firmware upgrade.
     Please don't turn off the power or press reset button.
7. WAIT until the Power LED stops flashing and allow the router to reboot. BE SURE YOU ALLOW SUFFICIENT TIME FOR THE PROCESS TO COMPLETE. Follow appropriate recommendations in the Peacock thread.
8. If the Power LED flashes for more than 10–15 minutes, something is probably wrong. Check on how to revert back to factory firmware and try and other .chk file.
9. Check for recommended builds here.

If you are running dd-wrt

• See Upgrading

After flashing

1. ABSOLUTELY RECOMMENDED: perform the 30/30/30 reset per the Peacock thread
2. HIGHLY SUGGESTED: to ALSO do a full power cycle after the 30/30/30 reset
3. these steps are important to help clear old settings and provide some level of stability
4. if you just upgraded from the Netgear original firmware, you can now re-flash with any specific DD-WRT version/variant you require

Flashing OpenWrt

• Netgear WNDR3300

Firmware: http://downloads.openwrt.org/snapshots/trunk/brcm47xx/openwrt-wndr3300_v1-squashfs.chk

Steps to flash:

1: Do a 30/30/30 reset.

2: Flash the build from the web interface. TFTP will also work.

3: Do a 30/30/30 reset.

Upgrading

Updating DD-WRT

If dd-wrt is already on the router follow these instructions. If stock firmware is on the router follow the flashing instructions.

1. Check for recommended builds here first.
2. Set your computer to a static IP of 192.168.1.7. (or to whatever subnet the router is on) Disable all firewalls and security. Disable wireless on your computer and only have the router connected to the flashing computer by the ethernet cable between the two.
3. Hard reset or 30/30/30 (If the router supports it, if not, reset to defults in the GUI) prior to flashing. Wait. Check for password page on re-login and change password.
4. Flash firmware. You can use the webgui except if you have a belkin router. (For belkin use tftp.exe to flash)
5. Wait...at least three minutes. Lights should return to normal. See important2, below. Failing to wait is how most people brick their routers.
6. Do a power cycle of the router. (Unplug the cord, count to 30 and plug it back in.)
7. Wait for the lights to return to normal usually about 2 minutes.
8. Hard reset or 30/30/30 again (If the router supports it, if not, reset to defults in the GUI). Wait. Check for the password page and re-login to change the password. Then you can reconfigure your settings manually.
9. Once configured set your computer back to autoIP and autoDNS.
   

Important1: This Hard reset or 30/30/30 works fine for Asus router, but you do have to power cycle after the reset.

Important2: After you flash the firmware, and before you do the hard reset, the router will be building some nvram settings. YOU MUST WAIT FOR THIS TO FINISH PRIOR TO DOING ANYTHING WITH THE ROUTER INCLUDING A HARD RESET. Usually, you can tell when this process is completed by the WAN light coming on, but it does take several minutes. Go have a beer. There are starting to be more and more people who BRICK their routers by not waiting until the nvram is rebuilt, PRIOR to doing a hard reset. YOU NEED TO WAIT!

Reverting

Reverting to OEM Firmware from DD-WRT

• Reported by buddee: The reversion guide in the wiki will apply if you are running CFE 1.3, if they sent you a 1.5, the wiki method will not work, or at least for some, giving problems due to an improper board_id.

If you have DD-WRT installed and need to re-install the Netgear firmware for some reason, or just put the router in to tftp acceptance mode...

1. ssh or telnet to the router
2. enter the following command at the shell prompt (this effectively deletes the OS causing the router to go in to recovery mode on the next reboot/power cycle):
   • "erase linux"
3. you should see a message similar to:
   • Unlocking linux ...
     Erasing linux ...
4. wait until you are returned back to the shell prompt
5. power cycle the router
6. allow the router to finish booting (the Power LED will be lit solid for 10–15 seconds)
7. there after the Power LED should be flashing
8. you should be able to ping the router IP, generally 192.168.1.1
9. if you get a ping response the router is in tftp recovery mode
10. you should now be able to tftp an appropriate *.chk file to the router
    • you can upload either an original Netgear firmware OR a known working DD-WRT chk file for this router

• This wiki entry does NOT cover how to use tftp.
  • There are plenty of other entries and forum posts that cover this topic.
  • A good reference: TFTP Flash for information about this tool.

Also on a side note, i would suggest instead of "mtd erase linux" that you use "erase linux" (no quotes) as the mtd is leaving the 3300 in a perpetual state of tftp mode -buddee

JTAG-Serial Info

Does this router support serial TTL console?

1. Yes
2. Do not hook up your serial cable/wiring to the header used for the dome LEDs
3. The serial connectors (JP1) are next to the dome LED header. Most production/refurb units will not have a pin header mounted on the PCB for the serial connections (probably to save manufacturing costs)
4. The FCC photos of the internals show a header for both the dome LED and serial port
5. Reference: OpenWrt WNDR3300 wiki
6. Reference thread for a photo with the pin outs: WNDR3300 serial pinouts

Serial Pinouts

JP1 = 3.3v TTL Serial, 115200/8/N , 1 row of six pins

 GND 6 o
  TX 5 o
 N/C 4 o
 N/C 3 o
  RX 2 o
 VCC 1 o

Hyper terminal Setup in Windows XP

In Windows XP, Click Start Button - All Programs - Accessories - 
   Communication - HyperTerminal
Enter a name for the connection, Click ok
Choose com port you adapter is plugged into, Click ok
Set:
 Bits per second = 115200
 Data Bits = 8
 Parity = none
 Stop bits = 1
 Flow control = none
Click ok
Click File - Save As, and select a place to save it to so you 
             don't have to enter the settings again.

Putty Setup in Windows XP

After installing putty, run it
 Serial line = The COM port your using for serial (ie. COM3)
 Speed = 115200
Click on Serial under Connection
 Serial line to connect to = same as above (Serial line)
 Speed (baud) = 115200
 Data bits = 8
 Stop bits = 1
 Parity = none
 Flow control = none
Click Session
 Enter a name for your connection under saved sessions
Click Save
Click Open

Serial Recovery

Modified Redhawk0 instructions

1. Connect Serial cable
2. Start one of the programs from above
3. Get TFTP ready with file selected
4. Use dd-wrt.v24_std-wndr3300.chk
5. Connect power to the router
6. start a rapid fire Cntl-C as you plug the router to power
7. type "nvram erase" w/o quotes
8. type "tftpd" w/o quotes, this starts the tftp daemon
9. but have tftp.exe ready
10. Click go or start on TFTP
11. give it 5 minutes after it finishes
12. then power cycle....hard reset...then config
13. when it stops spitting out txt in the serial consol....hit the enter key...you should get a login prompt...at that point, power cycle it, hard reset...then config
14. you'll see it boot up

• WNDR3300 Brick - Will not take tftp flash (SOLVED!!)

• • A good reference thread is: Everything you Ever Wanted to know about Serial - TTL

Does this router support JTAG?

1. No
2. The mounted pin header on the PCB is for the dome LEDs. Do not use this for JTAG or serial TTL.
3. If your unit has another header mounted next to the right of the dome LED header, that is for serial TTL console.

MTD Flash RAM partitions

Flash device: 0x400000 at 0x1c000000
Boot partition size = 131072 (0x20000)

0x00000000-0x00020000 : "boot"
0x00020000-0x003b0000 : "linux"
0x000927f8-0x003b0000 : "rootfs"
0x003b0000-0x003c0000 : "T_Meter1"
0x003c0000-0x003d0000 : "T_Meter2"
0x003d0000-0x003e0000 : "POT"
0x003e0000-0x003f0000 : "board_data"
0x003f0000-0x00400000 : "nvram"

DD-WRT Configuration suggestions

For now here are some threads that discuss possible configuration settings for new users:

1. Netgear WNDR3300 HELP
2. How to set up wireless WNDR3300?
3. Netgear Wndr3300 CPU loading problems slow wireless

For more advanced users, we will be posting more information shortly. eg, WDS and client bridge concerns

Pin Short Recovery

Works—short pins 16 & 17 while plugging in the power cable. Ping constantly with 'ping -t -w 1 192.168.1.1', and when you start to see TTL=100, remove the short and tftp a basic *.chk file to the router. Give it a few mins to figure out what happened, and hopefully the WLAN lights should come back on. If you're still pinging, things are good if you see a TTL=64, DD-WRT's signature.

Per usual, please read the Peacock Thread before attempting this.

Model and Revision Differences

1. WNDR3300 vs WNDR3300-100NAR? The latter is just a refurbished model with the serial number removed from the bottom label on the unit.
2. There is only one known version of this model.
   • If anyone has any confirmed revision information, please update this thread.
   • As of 2/1/2010, units bought in 2009 and 2010 opened up by one user has "Rev 1" etched on the PCB.

Power supply information

Initial refurbs sold in 2008 and early 2009 had potential issues with their power supplies. This caused stability issues with the routers.

Most recent models (new and refurbs from mid 2009 on wards) come with a switching power supply:

• voltage: 12 vDC
• amp: 1500mA
• plug size:
  • 2.1mm ID (confirmed with digital caliper)
  • 5.5mm OD (confirmed with digital caliper)
  • Center=Positive (center pin)
  • Shield=Negative

• kill-a-watt reported power usage:
  • 3 watts on initial boot up or with all radios disabled (idle)
  • 5 watts with just one radio (with default TX power) - idle
  • 6 watts with both radios (with default TX power on each radio) - idle

Power supplies for this router are manufactured by two vendors (according to FCC information and based on purchases from 2009 and 2010):

• DVE - units from this manufacturer have been known to be bad or inconsistent from the early batches of routers sold in 2008 to mid 2009. Please read the main support thread for more information about this.
• ITE

It has been recommended to go with a non-switching transformer for those wanting to increase the power to the radios beyond the default mW per radio. However, some have found it difficult to find such power supplies (transformer based above 1500mA). A suggestion is to use a *quality* regulated 12vdc 2000mA (or higher amperage) switching power supply. If you believe to have stability issues that a 30/30/30 reset + full power cycle may not be not solving... try another power supply if you have one available.

Be sure to review the additional discussions links in the Peacock and main support thread regarding power supplies and bad capacitors. There have been no known reports regarding the router itself suffering from bad capacitors.

Antenna (internal and external) information

Internal antennas

1. Netgear advertises the router with 8 internal antennas. While this is true in the sense there are eight antennas etched on the PCB, even the official FCC information lists only 5 active antennas.
2. three of the five active antennas are for the wl0 radio (supporting 2.4 GHz or 5 GHz bands)
3. the remaining two of the five active antennas are used for the wl1 radio (supporting only the 2.4 GHz band)

External antennas

1. the router does not have any external antennas without performing some kind of modification that would result in voiding your factory warranty
2. Current thread topic: How to add external. ant
3. How to: Netgear WNDR3300 Antenna Mod
4. Some users have parts on order from digikey.com to follow twinmos on adding external antennas. We will update this section with the specific part numbers (it is buried in the topic thread) later.
5. The Hirose connectors on the PCB are MS-156 RF test switches. There are NO CHEAP solutions currently available to convert/adapt to SMA type cabling and antennas. According to digikey.com, the cheapest solution is a locking MS-156 to SMA adapter which is about $29USD per switch. You need at least 3 of these for the WL0 radio and 2 more for the WL1 radio.
   • It is recommended to either do the pigtail mod or install Hirose u.fl pads like twinmos did in the thread.

5 GHz (and N over 5 GHz) information

(work in progress)

The primary advantage some users of this router believe is the ability to use 802.11n over the less crowded 5 GHz band. However, there are many considerations. We will try to list some of those here over time.

1. from a forum post, read this article about Improve Wi-Fi Performance in the 5 GHz Band
2. as noted several times in this wiki entry, the internal antennas reduce the potential range of using the 5 GHz band on this router. It is still usable for many depending on router placement and possible usage requirements.

How do I get "270 mpbs" 802.11n?

1. you can only obtain this advertised connection speed on the wl0 radio through the 5 GHz band (N only-5). The 2.4 GHz band on this specific router only supports 20MHz wide for a maximum of "130 Mbps" connection speeds.
2. you need to set your channel width to 40MHz. If you set to 20MHz you'll get the 130 mpbs rated connection speed.
3. it is recommended to NOT set the channel and/or channel width to AUTO as it may not guarantee that the router will select a channel or width your wireless NIC or WDS/bridge may support.
4. note that although the router and/or your wireless NIC may say connected at 270 Mbps (for 40MHz channel width users) or 130 mpbs (for 20MHz users on either the 2.4 GHz or 5 GHz band)... THAT DOES NOT MEAN YOU WILL GET THOSE ACTUAL TRANSFER SPEEDS IN REAL WORLD USAGE. If you doubt that, read the article above about 5 GHz performance and use google to learn why.

2.4 GHz (and N over 2.4 GHz) information

• 2.4 GHz Wireless-N Configuration

LED information

Front LEDs

1. Can I control the front LEDs?
   1. it does not appear that end user gpio LED access is allowed via the /sbin/gpio binary
   2. see separate section on known GPIO information
2. What do the front LEDs mean and how do they indicate status?
   1. reference WNDR3300 one activity LED flashes infrequently (credit for partial paste for below)
      • Power (not directly labeled) - The power light blinks when it is starting up or the restore factory settings button is pressed.
      • 2.4 GHz Mode - This light will blink if there are data transmitted wirelessly in this mode
      • 5 GHz Mode - This light will blink if there are data transmitted wirelessly in this mode
      • Internet (not directly labeled, looks like an lower case "i")- This light will blink if an IP address has been received and data is being transmitted and received
      • LAN 1-4 (labeled with actual numbers "1" "2" "3" and "4") - This will blink if there is traffic or data passing on this port.

Dome LEDs

1. How are the dome LEDs handled?
   1. the original Netgear firmware flashed the dome lights based on various activities on the wireless radios, etc.
   2. DD-WRT automatically turns off the dome lights on boot up with code changes since builds around Nov 2008
      1. reference Changeset 10994
2. Can I control the dome LEDs?
   1. it does not appear that access to the dome lights are easily exposed to end users
   2. reference thread: WNDR3300 Dome Lights
3. What if the dome LEDs come back on after I've flashed with a good known version of DD-WRT?
   • back up your settings using the hardware independent backup script (search the wiki and forums)
   • try performing a full 30/30/30 reset per Peacock, and do a full power cycle
   • if the dome does not turn off, either your unit is going bad or you can physically unplug the ribbon cable inside the unit to permanently disable it

GPIO information

(credit to original poster from main support thread: rafale12)

Known GPIO pin support:

• gpio 0: using it crashes router
• gpio 1: 01, cannot change it with disable. Suspect WPS (top orb related)
• gpio 2: constantly changing: 00/01/00 so WAN or LAN
• gpio 3: 00 ??
• gpio 4: 00 ??
• gpio 5: powerled
• gpio 6: 01 disabling seems to be a reset to default.
• gpio 7: 01 ??
• gpio 8: 00 ??

Hardware information

• Official FCC information

• MTD Flash RAM partitions
Flash device: 0x400000 at 0x1c000000 Boot partition size = 131072 (0x20000) 0x00000000-0x00020000 : "boot" 0x00020000-0x003b0000 : "linux" 0x000927f8-0x003b0000 : "rootfs" 0x003b0000-0x003c0000 : "T_Meter1" 0x003c0000-0x003d0000 : "T_Meter2" 0x003d0000-0x003e0000 : "POT" 0x003e0000-0x003f0000 : "board_data" 0x003f0000-0x00400000 : "nvram"

• Boot Messages

* boot messages from bootloader and Linux loading Netgear firmware v1.0.30NA Decompressing..........done Decompressing..........done WNDR3300 Boot code V1.0.2 Build date: Thu Sep 20 13:11:58 CST 2007 Initializing Arena Initializing Devices. Boot partition size = 131072(0x20000) et0: Broadcom BCM47xx 10/100 {{abbr|Mbps|Megabits per second}} Ethernet Controller 4.150.10.5 et1: Broadcom BCM47xx 10/100 {{abbr|Mbps|Megabits per second}} Ethernet Controller 4.150.10.5 CPU type 0x29006: 264{{abbr|MHz|megahertz}} Total memory: 16384 KBytes Device eth0: hwaddr 00-1E-2A-5C-2F-CD, ipaddr 192.168.1.1, mask 255.255.255.0 gateway not set, nameserver not set CPU revision is: 00029006 Primary instruction cache 16kb, linesize 16 bytes (2 ways) Primary data cache 16kb, linesize 16 bytes (2 ways) Linux version 2.4.20 (builder@dev2) (gcc version 3.2.3 with Broadcom modifications) #33 Fri Jan 11 12:58:25 CST 2008 Setting the PFC to its default value Determined physical RAM map: memory: 01000000 @ 00000000 (usable) On node 0 totalpages: 4096 zone(0): 4096 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200 CPU: BCM4704 rev 9 at 264 {{abbr|MHz|megahertz}} Calibrating delay loop... 262.96 BogoMIPS Memory: 14584k/16384k available (1254k kernel code, 1800k reserved, 104k data, 56k init, 0k highmem) Dentry cache hash table entries: 2048 (order: 2, 16384 bytes) Inode cache hash table entries: 1024 (order: 1, 8192 bytes) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table entries: 4096 (order: 2, 16384 bytes) Checking for 'wait' instruction... unavailable. POSIX conformance testing by UNIFIX PCI: Initializing host PCI: Fixing up bus 0 PCI: Fixing up bridge PCI: Fixing up bus 1 Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au) devfs: boot_options: 0x1 Squashfs 2.2-r2 (released 2005/09/08) (C) 2002-2005 Phillip Lougher Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled ttyS00 at 0xb8000300 (irq = 3) is a 16550A ttyS01 at 0xb8000400 (irq = 0) is a 16550A PPP generic driver version 2.4.2 Amd/Fujitsu Extended Query Table v1.1 at 0x0040 number of CFI chips: 1 Flash device: 0x400000 at 0x1c000000 Physically mapped flash: squashfs filesystem found at block 585 Creating 8 MTD partitions on "Physically mapped flash": 0x00000000-0x00020000 : "boot" 0x00020000-0x003b0000 : "linux" 0x000927f8-0x003b0000 : "rootfs" 0x003b0000-0x003c0000 : "T_Meter1" 0x003c0000-0x003d0000 : "T_Meter2" 0x003d0000-0x003e0000 : "POT" 0x003e0000-0x003f0000 : "board_data" 0x003f0000-0x00400000 : "nvram" NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 1024 bind 2048) Linux IP multicast router 0.06 plus PIM-SM NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. NET4: Ethernet Bridge 008 for NET4.0 802.1Q VLAN Support v1.7 Ben Greear <greearb@candelatech.com> All bugs added by David S. Miller <davem@redhat.com> VFS: Mounted root (squashfs filesystem) readonly. Mounted devfs on /dev Freeing unused kernel memory: 56k freed Algorithmics/MIPS FPU Emulator v1.5 Reading board data... WSC UUID: 0x450a40ee3f68bd4033ee9a405928c362 Using /lib/modules/2.4.20/kernel/drivers/net/et/et.o insmod: bcm57xx.o: no module by that name found Using /lib/modules/2.4.20/kernel/drivers/net/wl/wl.o Hit enter to continue...Reading board data... WSC UUID: 0x450a40ee3f68bd4033ee9a405928c362 WARNING: console log level set to 1 eth2: Numerical result out of range eth2: Operation not supported eth2: Invalid argument eth2: Operation not supported eth2: Operation not supported eth3: Numerical result out of range eth3: Operation not supported eth3: Invalid argument eth3: Invalid argument eth4: No such device ifconfig: Illegal seek ********************************************* Wi-Fi Simple Config Application - Intel Corp. Version: Build 1.0.5, November 19 2006 ********************************************* Initializing stack...button monitor start...! apLockDownLog_init, counttion = 300, duration = 300! OK Now starting stack get mac = 00 1E 2A 5C 2F CC DEVICE PIN: 63204810 eth2: ignore i/f due to error(s) eth3: ignore i/f due to error(s) Reading board data... WSC UUID: 0x450a40ee3f68bd4033ee9a405928c362 Using /lib/modules/2.4.20/kernel/net/ipv4/acos_nat/acos_nat.o info, udhcp server (v0.9.8) started error, unable to parse 'option wins ' error, unable to parse 'option domain ' Info: No FWPT default policies. POT integrity check OK. POT time is up. Start DHCP client daemon info, udhcp client (v0.9.8) started UTX 0x01 URX 0x01 DTX 0x01 DRX 0x01 eth1: No such process Hit enter to continue... ******* MODE: Access Point ******* DEVICE PIN:63204810 WSC: In unconfiged AP mode, wait for start command.... tlvPtrChar* : func CMasterControl_InitiateRegistration line 656 allocating memory 0x10003680 for 0x10003668 Waiting for Registrar to connect... BusyBox v0.60.0 (2008.01.11-04:58+0000) Built-in shell (msh) Enter 'help' for a list of built-in commands.

• NVRAM

board_id=U12H093T00_NETGEAR boardtype=0x0472 boardnum=01 boardrev=0x23 boardflags=0x10 pci/1/1/boardvendor=0x14e4 pci/1/1/boardtype=0x49C pci/1/1/boardrev=0x13 pci/1/1/boardflags=0x0A00 pci/1/1/boardflags2=0x0014 wl_corerev= wl0_corerev=12 wl1_corerev=9 pci/1/1/aa2g=7 pci/1/1/aa5g=7 pci/1/1/ag0=2 pci/1/1/ag1=2 pci/1/1/ag2=2 pci/1/1/antswitch=2 pci/1/1/boardflags=0x0A00 pci/1/1/boardflags2=0x0014 pci/1/1/boardtype=0x49C pci/1/1/boardrev=0x13 pci/1/1/boardvendor=0x14e4 pci/1/1/bw40po=0 pci/1/1/bwduppo=0 pci/1/1/ccdpo=0 pci/1/1/cck2gpo=0x1111 pci/1/1/ccode=0 pci/1/1/devid=0x4328 pci/1/1/itt2ga0=0x3E pci/1/1/itt2ga1=0x3E pci/1/1/itt5ga0=0x3C pci/1/1/itt5ga1=0x3C pci/1/1/ledbh0=11 pci/1/1/ledbh1=11 pci/1/1/ledbh2=11 pci/1/1/ledbh3=11 pci/1/1/ledbh4=11 pci/1/1/ledbh5=5 pci/1/1/ledbh6=0x82 pci/1/1/ledbh7=11 pci/1/1/leddc=0xFFFF pci/1/1/macaddr=00:00:00:00:00:00 pci/1/1/maxp2ga0=0x4A pci/1/1/maxp2ga1=0x4A pci/1/1/maxp5ga0=0x4A pci/1/1/maxp5ga1=0x4A pci/1/1/maxp5gha0=0x4A pci/1/1/maxp5gha1=0x4A pci/1/1/maxp5gla0=0x3C pci/1/1/maxp5gla1=0x3C pci/1/1/mcs2gpo0=0x2000 pci/1/1/mcs2gpo1=0x4422 pci/1/1/mcs2gpo2=0x2000 pci/1/1/mcs2gpo3=0x4422 pci/1/1/mcs2gpo4=0 pci/1/1/mcs2gpo5=0 pci/1/1/mcs2gpo6=0 pci/1/1/mcs2gpo7=0 pci/1/1/mcs5ghpo0=0x4200 pci/1/1/mcs5ghpo1=0x6664 pci/1/1/mcs5ghpo2=0x4200 pci/1/1/mcs5ghpo3=0x6664 pci/1/1/mcs5ghpo4=0 pci/1/1/mcs5ghpo5=0 pci/1/1/mcs5ghpo6=0 pci/1/1/mcs5ghpo7=0 pci/1/1/mcs5glpo0=0x4200 pci/1/1/mcs5glpo1=0x6664 pci/1/1/mcs5glpo2=0x4200 pci/1/1/mcs5glpo3=0x6664 pci/1/1/mcs5glpo4=0 pci/1/1/mcs5glpo5=0 pci/1/1/mcs5glpo6=0 pci/1/1/mcs5glpo7=0 pci/1/1/mcs5gpo0=0x4200 pci/1/1/mcs5gpo1=0x6664 pci/1/1/mcs5gpo2=0x4200 pci/1/1/mcs5gpo3=0x6664 pci/1/1/mcs5gpo4=0 pci/1/1/mcs5gpo5=0 pci/1/1/mcs5gpo6=0 pci/1/1/mcs5gpo7=0 pci/1/1/pa2gw0a0=0xFEFC pci/1/1/pa2gw0a1=0xFF03 pci/1/1/pa2gw1a0=0x14EA pci/1/1/pa2gw1a1=0x13DB pci/1/1/pa2gw2a0=0xFB24 pci/1/1/pa2gw2a1=0xFB47 pci/1/1/pa2gw3a0=0 pci/1/1/pa2gw3a1=0 pci/1/1/pa5ghw0a0=0xFEE8 pci/1/1/pa5ghw0a1=0xFF72 pci/1/1/pa5ghw1a0=0x11C2 pci/1/1/pa5ghw1a1=0x1375 pci/1/1/pa5ghw3a0=0 pci/1/1/pa5ghw3a1=0 pci/1/1/pa5glw0a0=0xFEFB pci/1/1/pa5glw0a1=0xFF5B pci/1/1/pa5glw1a0=0x120E pci/1/1/pa5glw1a1=0x13BE pci/1/1/pa5glw2a0=0xFBA2 pci/1/1/pa5glw3a0=0 pci/1/1/pa5glw3a1=0 pci/1/1/pa5glw2a1=0xFBC7 pci/1/1/pa5gw0a0=0xFF3C pci/1/1/pa5gw0a1=0xFFEC pci/1/1/pa5gw1a0=0x1238 pci/1/1/pa5gw1a1=0x13A4 pci/1/1/pa5gw2a0=0xFBD2 pci/1/1/pa5gw2a1=0xFC13 pci/1/1/pa5gw3a0=0 pci/1/1/pa5gw3a1=0 pci/1/1/pa5ghw2a0=0xFBB5 pci/1/1/pa5ghw2a1=0xFBC0 pci/1/1/ofdm2gpo=0x00000000 pci/1/1/ofdm5glpo=0x20000000 pci/1/1/ofdm5ghpo=0x20000000 pci/1/1/ofdm5gpo=0x20000000 pci/1/1/regrev=0 pci/1/1/rxchain=3 pci/1/1/sromrev=4 pci/1/1/stbcpo=0 pci/1/1/txchain=3 pci/1/1/txpt2g=0x48 pci/1/1/txpt5g=0x3C pci/1/1/txpt5gh=0x3C pci/1/1/txpt5gl=0x30 pci/1/1/txpid2ga0=60 pci/1/1/txpid2ga1=46 pci/1/1/txpid5ga0=35 pci/1/1/txpid5ga1=32 pci/1/1/txpid5gha0=35 pci/1/1/txpid5gha1=29 pci/1/1/txpid5gla0=20 pci/1/1/txpid5gla1=24 pci/1/1/venid=0x14e4 pci/1/3/boardflags=0xAA48 pci/1/3/ag0=0x02 pci/1/3/ccode=0 pci/1/3/aa0=0x03 pci/1/3/devid=0x4318 pci/1/3/macaddr=00:00:00:00:00:00 pci/1/3/pa0b0=0x14D0 pci/1/3/pa0b1=0xFADA pci/1/3/pa0b2=0xFE99 pci/1/3/pa0itssit=62 pci/1/3/pa0maxpwr=0x004E pci/1/3/opo=8 pci/1/3/wl0gpio0=11 pci/1/3/wl0gpio1=11 pci/1/3/wl0gpio2=11 pci/1/3/wl0gpio3=0x82 pci/1/3/sromrev=2

USB Info

NO USB

vlan Info

DD-WRT vlan Info

• WikiDevi:DD-WRT/VLAN Support

WNDR3300's ports are mapped like this:

 4 3 2 1 | case labels
 3 2 1 0 | nvram port numbers

The VLAN GUI page should show up if you've enabled it. With the test build(15042_NEWD_mini) you need to run these commands.

 nvram set force_vlan_supp=enabled
 nvram commit
 reboot

Images

Retail Images

• 

  WNDR3300 (A)

• 

  WNDR3300 (B)

DarkShadow's Unit

• 
• 
• 
• 
• 
• 

M86's Unit

• 

  board top

• 

  board bottom

FCCID PY308100078 & PY307300072

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

Notes

  DarkShadow   talk    contribs   - Of the 2 units I have one is marked "NGR-WNDR3300 (B)". I am not sure the significance of this, both units appear to be identical hardware wize.

Hardware Modification

• Netgear WNDR3300 USB Port

See also

• Netgear WNDR3300v1
• Netgear WNDR3300v2