NETGEAR WN604

Under Construction!
This page is currently under construction. You can edit the article to help completing it.

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 will end after 2019.
19.07 will be the last official build for 4/32 devices. After 19.07, no further OpenWrt images will be built for 4/32 devices. See OpenWrt on 4/32 devices what you can do now.

Write a short, relevant description of the device. Include a technical overview, but avoid marketing buzzwords/useless stuff. Two to four sentences is about right. A picture is good, too. Edit the page to see how to add pictures.

Any text with a light background (like this one) provides instructions for creating the Details Page. When you have filled in correct/useful information (instead of any template that's there) remove the instructions, as well as the <WRAP> that encloses it.

This is an empty template that suggests the information that should be present on a well-constructed Device Page. This means, that you have to fill it with life and information.
There are several “fixme” tags with text on a light background (like this text) throughout this template. As you fill in the page, remove those tags so that people can judge its completeness.
When there are no more “fixme” tags left, delete this one too, along with the <WRAP> that encloses it.

Keep the articles modular

Please include only model specific information, omit bla,bla and put everything generic into separate articles
If you have no time to write certain stuff, link to docs
base-system should lead the way, do not explain this again
DO NOT provide a complete howto here! Instead groom the general documentation.

Brand	Model	Version	Current Release	OEM Info	Forum Topic	Technical Data
NETGEAR	WN604			http://www.netgear.com/business/products/wireless/soho-wireless/wn604.aspx	https://forum.openwrt.org/t/netgear-wn604-information/6460/21?u=tmomas	View/Edit data

Model	Version	SoC	CPU MHz	Flash MB	RAM MB	WLAN Hardware	WLAN2.4	WLAN5.0	100M ports	Gbit ports	Modem	USB
WN604		Atheros AR7240	340	4	32	Atheros AR9285	b/g/n	-	4		-	-

Model	Version	Supported Current Rel	Firmware OpenWrt Install URL	Firmware OpenWrt Upgrade URL	Firmware OEM Stock URL
WN604					http://www.downloads.netgear.com/files/GDC/WN604/WN604_V3.3.2_firmware.zip

→ Install OpenWrt (generic explanation)

Find out flash layout, then add the flash layout table here (copy, paste, modify the example).

Please check out the article Flash layout. It contains examples and explanations that describe how to document the flash layout.

The instructions below are for Broadcom devices and only serve as an example. Remove / modify them if they do not apply to this particular device!

This section deals with

How you install OpenWrt from a device freshly opened
The steps required such as reset to factory defaults if the device has already been configured

Note: Reset router to factory defaults if it has been previously configured.

Browse to http://192.168.1.1/Upgrade.asp
Upload .bin file to router
Wait for it to reboot
Telnet to 192.168.1.1 and set a root password, or browse to http://192.168.1.1 if LuCI is installed.

→ generic.flashing.tftp

Specific values needed for tftp

Enter values for “FILL-IN” below

Bootloader tftp server IPv4 address	FILL-IN
Bootloader MAC address (special)	FILL-IN
Firmware tftp image	Latest OpenWrt release (`NOTE:` Name must contain “tftp”)
TFTP transfer window	FILL-IN seconds
TFTP window start	approximately FILL-IN seconds after power on
TFTP client required IP address	FILL-IN

→ generic.sysupgrade

These are generic instructions. Update with your router's specifics.

Browse to http://192.168.1.1/cgi-bin/luci/mini/system/upgrade/ LuCI Upgrade URL
Upload image file for sysupgrade to LuCI
Wait for reboot

If you don't have a GUI (LuCI) available, you can alternatively upgrade via the command line. There are two command line methods for upgrading:

sysupgrade
mtd

Note: It is important that you put the firmware image into the ramdisk (/tmp) before you start flashing.

sysupgrade

Login as root via SSH on 192.168.1.1, then enter the following commands:

cd /tmp
wget http://downloads.openwrt.org/snapshots/trunk/XXX/xxx.abc
sysupgrade /tmp/xxx.abc

mtd

If sysupgrade does not support this router, use mtd.

Login as root via SSH on 192.168.1.1, then enter the following commands:

cd /tmp
wget http://downloads.openwrt.org/snapshots/trunk/XXX/xxx.abc
mtd write /tmp/xxx.abc linux && reboot

→ generic.debrick

→ failsafe_and_factory_reset

→ Basic configuration After flashing, proceed with this.
Set up your Internet connection, configure wireless, configure USB port, etc.

Please fill in real values for this device, then remove the EXAMPLEs

The default network configuration is:

Interface Name	Description	Default configuration
br-lan	EXAMPLE LAN & WiFi	EXAMPLE 192.168.1.1/24
vlan0 (eth0.0)	EXAMPLE LAN ports (1 to 4)	EXAMPLE None
vlan1 (eth0.1)	EXAMPLE WAN port	EXAMPLE DHCP
wl0	EXAMPLE WiFi	EXAMPLE Disabled

Please fill in real values for this device, then remove the EXAMPLEs

Numbers 0-3 are Ports 1-4 as labeled on the unit, number 4 is the Internet (WAN) 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
Internet (WAN)	EXAMPLE 4
LAN 1	EXAMPLE 3
LAN 2	EXAMPLE 2
LAN 3	EXAMPLE 1
LAN 4	EXAMPLE 0

→ hardware.button on howto use and configure the hardware button(s). Here, we merely name the buttons, so we can use them in the above Howto.

Please fill in real values for this device, then remove the EXAMPLEs

The Netgear WN604 has the following buttons:

BUTTON	Event
EXAMPLE Reset	reset
EXAMPLE Secure Easy Setup	ses
EXAMPLE No buttons at all.	-

General
Brand	NETGEAR
Model	WN604
Versions
Device Type	WiFi Router
Availability	Discontinued
Comments - general	Access Point with similar hardware to WPN824N
OpenWrt Support
Supported Since Commit
Supported Since Release
Supported Current Release
Unsupported
Hardware
Bootloader	U-Boot
Target	ar71xx
System-On-Chip
CPU MHz	340
Flash MB	4
RAM MB	32
Network
Ethernet 100M ports	4
Ethernet 1Gbit ports
Switch	Atheros AR7240
Modem	-
VLAN	Yes
Comments - network ports

Wireless
WLAN 2.4GHz	b/g/n
WLAN 5.0GHz	-
WLAN Hardware
Detachable Antennas	-
Comments - WLAN	1x1
Interfaces
USB ports	-
SATA ports	-
Serial	Yes
JTAG	Yes
Comments - USB & SATA ports
Misc
LED count	¿
Button count	¿
Power supply
Links
Forum Topic URL
WikiDevi URL	https://wikidevi.wi-cat.ru/Netgear_WN604
OEM device homepage URL	http://www.netgear.com/business/products/wireless/soho-wireless/wn604.aspx
Firmware OEM Stock URL	http://www.downloads.netgear.com/files/GDC/WN604/WN604_V3.3.2_firmware.zip
Firmware OpenWrt Install URL
Firmware OpenWrt Upgrade URL
Edit the underlying data	View/Edit data

Front:
Insert photo of front of the casing

Back:
Insert photo of back of the casing

Backside label:
Insert photo of backside label

Note: This will void your warranty!

Describe what needs to be done to open the device, e.g. remove rubber feet, adhesive labels, screws, ...

To remove the cover and open the device, do a/b/c

Main PCB:
Insert photo of PCB

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

How to connect to the Serial Port of this specific device:
Insert photo of PCB with markings for serial port

Replace EXAMPLE by real values.

Serial connection parameters for Netgear WN604 @@Version@@	EXAMPLE 115200, 8N1

→ port.jtag general information about the JTAG port, JTAG cable, etc.

How to connect to the JTAG Port of this specific device:
Insert photo of PCB with markings for JTAG port

→ bootloader

None so far.

U-Boot 1.1.4-g12193fce-dirty (Dec 14 2009 - 13:39:19) WN604 (ar7240) U-boot dni7 V0.8 DRAM: sri #### TAP VALUE 1 = b, 2 = c 32 MB Top of RAM usable for U-Boot at: 82000000 Reserving 278k for U-Boot at: 81fb8000 Reserving 192k for malloc() at: 81f88000 Reserving 56 Bytes for Board Info at: 81f87fc8 Reserving 36 Bytes for Global Data at: 81f87fa4 Reserving 128k for boot params() at: 81f67fa4 Stack Pointer at: 81f67f88 Now running in RAM - U-Boot at: 81fb8000 id read 0x100000ff flash size 4194304, sector count = 64 Flash: 4 MB In: serial Out: serial Err: serial Net: ag7240_enet_initialize... Fetching MAC Address from 0x81fe9690 Fetching MAC Address from 0x81fe9690 : cfg1 0xf cfg2 0x7014 eth0: 00:24:b2:db:3f:55 eth0 up : cfg1 0xf cfg2 0x7214 eth1: 00:24:b2:db:3f:54 ATHRS26: resetting s26 ATHRS26: s26 reset done eth1 up eth0, eth1 Manu data is valid! Trying eth1 eth1 link down FAIL Trying eth0 eth0 link down FAIL Client starts...[Listening] for ADVERTISE...TTT Retry count exceeded; boot the image as usual nmrp server is stopped or failed ! Hit any key to stop autoboot: 0 ## Booting image at 9f050000 ... Image Name: Linux Kernel Created: 2015-06-26 9:14:04 UTC Image Type: MIPS Linux Kernel Image (lzma compressed) Data Size: 655360 Bytes = 640 kB Load Address: 80002000 Entry Point: 801b8000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK No initrd ## Transferring control to Linux (at address 801b8000) ... ## Giving linux memsize in bytes, 33554432 Starting kernel ... Booting AR7240(Python)... ^@Linux version 2.6.15--LSDK-7.3.0.387-WN604_V3.3.2 (root@ng-build) (gcc version 3.4.4) #199 Fri Jun 26 14:41:28 IST 2015 flash_size passed from bootloader = 4 arg 1: console=ttyS0,115200 arg 2: rootfstype=squashfs arg 3: root=31:03 arg 4: init=/sbin/init arg 5: mtdparts=ar7240-nor0:256k(u-boot),64k(u-boot-env),704k(kernel),2624k(rootfs),320k(var),64k(manufacturing-data),64k(ART) arg 6: mem=32M CPU revision is: 00019374 Determined physical RAM map: memory: 02000000 @ 00000000 (usable) User-defined physical RAM map: memory: 02000000 @ 00000000 (usable) Built 1 zonelists Kernel command line: console=ttyS0,115200 rootfstype=squashfs root=31:03 init=/sbin/init mtdparts=ar7240-nor0:256k(u-boot),64k(u-boot-env),704k(kernel),2624k(rootfs),320k(var),64k(manufacturing-data),64k(ART) mem=32M Primary instruction cache 64kB, physically tagged, 4-way, linesize 32 bytes. Primary data cache 32kB, 4-way, linesize 32 bytes. Synthesized TLB refill handler (20 instructions). Synthesized TLB load handler fastpath (32 instructions). Synthesized TLB store handler fastpath (32 instructions). Synthesized TLB modify handler fastpath (31 instructions). Cache parity protection disabled PID hash table entries: 256 (order: 8, 4096 bytes) Using 170.000 MHz high precision timer. Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Memory: 30472k/32768k available (1448k kernel code, 2280k reserved, 299k data, 120k init, 0k highmem) Mount-cache hash table entries: 512 Checking for 'wait' instruction... available. NET: Registered protocol family 16 PCI init:ar7240_pcibios_init Returning IRQ 48 AR7240 GPIOC major 0 squashfs: version 3.3 (2007/10/31) Phillip Lougher squashfs: LZMA suppport for slax.org by jro JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc. Initializing Cryptographic API io scheduler noop registered io scheduler deadline registered Serial: 8250/16550 driver $Revision: #1 $ 1 ports, IRQ sharing disabled serial8250.0: ttyS0 at MMIO 0x0 (irq = 19) is a 16550A 7 cmdlinepart partitions found on MTD device ar7240-nor0 Creating 7 MTD partitions on "ar7240-nor0": 0x00000000-0x00040000 : "u-boot" 0x00040000-0x00050000 : "u-boot-env" 0x00050000-0x00100000 : "kernel" 0x00100000-0x00390000 : "rootfs" 0x00390000-0x003e0000 : "var" 0x003e0000-0x003f0000 : "manufacturing-data" 0x003f0000-0x00400000 : "ART" NET: Registered protocol family 2 IP route cache hash table entries: 512 (order: -1, 2048 bytes) TCP established hash table entries: 2048 (order: 1, 8192 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes) TCP: Hash tables configured (established 2048 bind 2048) TCP reno registered TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com> All bugs added by David S. Miller <davem@redhat.com> wls dev success reset dev success ar7240wdt_init: Registering WDT success VFS: Mounted root (squashfs filesystem) readonly. Freeing unused kernel memory: 120k freed Mounting etc to ramfs. [DONE] Mounting var to jffs2. [DONE] Checking for run file. [DONE] Checking Manufac. data [DONE] Checking board file. [CREATED] Loading Ethernet module. [GENMAC] [DONE] Multiple SKU supported. [DONE] Current SKU is [WN604] Checking database. sh: !=: argument expected [DONE] Verifing checksum. [DONE] Loading Bridge module. sh: yes: unknown operand [DONE] Loading wlan modules. [DONE] Creating vap interface. [DONE] Creating wds interface. [DONE] Starting configd. [DONE]ESC[1;29mStarting web server. ESC[1;0mESC[1;32m[DONE]ESC[1;0m Starting Translator... start-stop-daemon: cannot start /usr/bin/log_ro: No such file or directory [syslog] Starting Translator... [password] EStarting Translator... [dns] Starting Translator... set cascaded bridge failed: Operation not supported [bridge_and_vlan_translator] Starting Translator... [hostapd_tr] Starting Translator... [nmbd_tr] Starting Translator... [ntp] Starting Translator... kill: cannot kill pid 319: No such process kill: cannot kill pid 320: No such process [timezone] Starting Translator... [sc_radio] l2_packet_receive - recvfrom: Network is down l2_packet_receive - recvfrom: Network is down l2_packet_receive - recvfrom: Network is down l2_packet_receive - recvfrom: Network is down l2_packet_receive - recvfrom: Network is down Sending ARPing l2_packet_receive - recvfrom: Network is down ARPING to 192.168.1.135 from 192.168.1.135 via brtrunk Sent 1 probe(s) (1 broadcast(s)) Received 0 reply (0 request(s), 0 broadcast(s)) ARPING to 192.168.1.135 from 192.168.1.135 via brtrunk Sent 1 probe(s) (1 broadcast(s)) Received 0 reply (0 request(s), 0 broadcast(s)) ARPING to 192.168.1.135 from 192.168.1.135 via brtrunk Sent 1 probe(s) (1 broadcast(s)) Received 0 reply (0 request(s), 0 broadcast(s)) ARPING to 192.168.1.135 from 192.168.1.135 via brtrunk Sent 1 probe(s) (1 broadcast(s)) Received 0 reply (0 request(s), 0 broadcast(s)) ARPING to 192.168.1.135 from 192.168.1.135 via brtrunk Sent 1 probe(s) (1 broadcast(s)) Received 0 reply (0 request(s), 0 broadcast(s)) ARPING to 192.168.1.135 from 192.168.1.135 via brtrunk Sent 1 probe(s) (1 broadcast(s)) Received 0 reply (0 request(s), 0 broadcast(s)) ARPING to 192.168.1.135 from 192.168.1.135 via brtrunk Sent 1 probe(s) (1 broadcast(s)) Received 0 reply (0 request(s), 0 broadcast(s)) System initilization is .. [DONE...] Welcome to SDK. Have a lot of fun... netgearC018C0 login:

COPY HERE THE BOOTLOG ONCE OPENWRT IS INSTALLED AND RUNNING

Space for additional notes, links to forum threads or other resources.

...

How to add tags

AR7240, 4Flash, 32RAM

ar7240 4Flash 32RAM

NETGEAR WN604

Getting started with a new Device Page

Keep the articles modular

Supported Versions

Hardware Highlights

Installation

Flash Layout

OEM easy installation

OEM installation using the TFTP method

Specific values needed for tftp

Upgrading OpenWrt

LuCI Web Upgrade Process

Terminal Upgrade Process

sysupgrade

mtd

Debricking

Failsafe mode

Basic configuration

Specific Configuration

Network interfaces

Switch Ports (for VLANs)

Buttons

Hardware

Info

Photos

Opening the case

Serial

JTAG

Bootloader mods

Hardware mods

Bootlogs

OEM bootlog

OpenWrt bootlog

Notes

Tags