This device is NOT RECOMMENDED for future use with OpenWrt due to low flash/ram.
DO NOT BUY DEVICES WITH 4MB FLASH / 32MB RAM if you intend to flash an up-to-date and secure OpenWrt version onto it! See 4/32 warning for details.

1) This device does not have sufficient resources (flash and/or RAM) to provide secure and reliable operation.
This means that even setting a password or changing simple network settings might not be possible any more, rendering the device effectively useless. See OpenWrt on 4/32 devices what you can do now.

2) OpenWrt support for this device has ended in 2022.
19.07.10 was the last official build for 4/32 devices.

Note: Official images are too large as of 17.XX. Use the Community Builds in the forum topic URL below for the latest 17.XX, 18.XX, and 19.XX images.

WNR1000-100PES - very similar to WNR2000v3 / WNR612v2

WNR1000v2 also exists as WNR1000v2h2 - instructions for WNR1000v2 also work for WNR1000v2h2 without modification.

Install OpenWrt (generic explanation)

Note: Ready-to-install firmware images for OpenWrt 17.01.7 and 18.06.8 and 19.07.3 are available as of June 2020 via OpenWrt Community Builds. These are customized builds that do include opkg due to inadequate flash size that cause stock, official OpenWrt builds to bootloop or not retain settings upon reboot.

Updated Installation Instructions

- - -

I tried web-interface upload of v2.img linked above, router complained 2x about image, using ambiguous language about cause of failure; filename pattern violation, or image content, or checksum..

1. alert/modal/popup “Firmware upload failed, please check your file” I dismiss that, and click ok/yes 2. another error, now inserted into web-page <div>, text refreshes away before I can copy-paste it

Upgrade WNR1000v2 to the latest factory firmware: Otherwise, the power LED may not behave properly.

You need to place the device into failsafe mode. For booting into failsafe mode, you need to power up the device while holding the reset button with a pin. The power LED should have an amber colour. Hold the button until it is starting to flash green. It starts to flash green after it flashes the amber LED for six times. After that, the device is in failsafe mode, accepting a firmware via its TFTP server. The device should respond to pings at, although the responses may be malformed.

Configure your ethernet interface with a IP address. I use with netmask but it should work with any free address from that block.

You need a TFTP client for this purpose. You may check the OpenWrt wiki for more information if you aren't familiar with the procedure. You need openwrt-ar71xx-generic-wnr1000v2-squashfs-factory-barrier-breaker-r44095.img, download can be found at It's only image what can be flashed sucseesfuly, later images stuck at bootloop.

put openwrt-ar71xx-generic-wnr1000v2-squashfs-factory-barrier-breaker-r44095.img

After boot you can upgrade openwrt to a newer version with sysupgrade.

port.serial general information about the serial port, serial port cable, etc.

The serial port is found at JP2. Pin 1 is marked with dot.

Pin Description
2 RX
3 TX

GPIO LEDs and buttons on this device are connected to GPIO controllers on AR7240 SoC and AR9285 wireless chip.

Controlled by AR7240 SoC (18 GPIOs total, LAN LEDs shared with built-in Ethernet switch) :

Type Function GPIO Polarity Notes
LED WAN AMBER 0 (0, 0) active low
LED POWER AMBER 1 (0, 1) active low aka TEST AMBER - see note [3]
LED LAN1 AMBER 6 (0, 6) active low shared with JTAG - see note [0]
LED LAN2 AMBER 7 (0, 7) active low shared with JTAG - see note [0]
LED LAN3 AMBER 8 (0, 8) active low shared with JTAG - see note [0]
LED POWER GREEN 11 (0, 11) active low
LED LAN4 AMBER 12 (0, 12) active low
LED LAN1 GREEN 13 (0, 13) active low link activity - see note [1]
LED LAN2 GREEN 14 (0, 14) active low link activity - see note [1]
LED LAN3 GREEN 15 (0, 15) active low link activity - see note [1]
LED LAN4 GREEN 16 (0, 16) active low link activity - see note [1]
LED WAN GREEN 17 (0, 17) active low link activity - see note [1]

Controlled by AR9285 wireless chip (12 GPIOs total) :

Type Function GPIO Polarity Notes
LED WLAN BLUE 53 (1, 1) active low not all triggers work - see note [2]
LED WPS GREEN 57 (1, 5) active low
Button WPS 58 (1, 6) active low
Button RESET 59 (1, 7) active low
Button RFKILL 60 (1, 8) active low


  • [0] - needs reprogramming of SoC to deallocate GPIO pins from JTAG
  • [1] - needs reprogramming of SoC to deallocate GPIO pins from built-in Ethernet switch; required for different link speed colors
  • [2] - 'phy0radio' trigger does not work, use default 'phy0tpt' or 'wlan0' netdevice instead
  • [3] - this is amber light on power LED (labelled TEST in u-boot sources)

GPIO in OpenWrt

# cat /sys/kernel/debug/gpio
GPIOs 0-17, ath79:
 gpio-0   (netgear:amber:wan   ) out hi    
 gpio-1   (netgear:amber:test  ) out hi    
 gpio-6   (netgear:amber:lan1  ) out hi    
 gpio-7   (netgear:amber:lan2  ) out hi    
 gpio-8   (netgear:amber:lan3  ) out hi    
 gpio-11  (netgear:green:power ) out lo    
 gpio-12  (netgear:amber:lan4  ) out hi    
 gpio-13  (netgear:green:lan1  ) out lo    
 gpio-14  (netgear:green:lan2  ) out lo    
 gpio-15  (netgear:green:lan3  ) out lo    
 gpio-16  (netgear:green:lan4  ) out lo    
 gpio-17  (netgear:green:wan   ) out lo    

GPIOs 52-63, ath9k-phy0:
 gpio-53  (netgear:blue:wlan   ) out hi    
 gpio-57  (netgear:green:wps   ) out hi    
 gpio-58  (wps                 ) in  hi    
 gpio-59  (reset               ) in  hi    
 gpio-60  (rfkill              ) in  hi    

There is a project allowing to build custom u-boot image It could be used if flash memory chip was replaced or to obtain additional functionality.

This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
  • Last modified: 2024/02/12 08:58
  • by