Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| toh:netgear:wgt634u [2018/02/20 18:51] – ↷ Links adapted because of a move operation bobafetthotmail | toh:netgear:wgt634u [2021/12/05 11:52] – Brand name capitalization adjusted tmomas | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| - | A router that was end-of-lifed by Netgear on October 1, 2005, it remains a useful and versatile device. | + | {{section> |
| - | Note: A lot of good information is on the OldWiki page: http://wiki.openwrt.org/ | + | A router that was end-of-lifed by Netgear |
| - | Trunk introduced a legacy target ( https:// | + | Note: A lot of good information is on the OldWiki page: [[http:// |
| + | |||
| + | Trunk introduced a legacy target ( https:// | ||
| ===== Supported Versions ===== | ===== Supported Versions ===== | ||
| - | There are two versions of the WGT634U, but they are not labelled in a distinguishing manner. | + | ---- datatable ---- |
| + | cols : Brand, Model, Versions, Supported Current Rel, OEM device homepage URL_url, OWrt Forum Topic URL_url, Device Techdata_pageid | ||
| + | headers : Brand, Model, Version, Current Release, OEM Info, Forum Topic, Technical Data | ||
| + | align : c, | ||
| + | filter | ||
| + | ---- | ||
| + | |||
| + | There are two versions of the WGT634U, but they are not labelled in a distinguishing manner. The first version is very rare and appears to represent the first production run, almost all extant versions are the latter. The difference between the two is principally in that the first lacks a heatsink on the CPU and populates both serial ports and the JTAG interface with headers. The early version also populates some resistors for the JTAG. Later models, presumably, can enable JTAG by installing the 0603 SMD resistors, though this has not been known to be tested yet. | ||
| ===== Hardware Highlights ===== | ===== Hardware Highlights ===== | ||
| - | ^ CPU ^ Ram | + | ---- datatable ---- |
| - | | Broadcom BCM3302@200MHz | + | cols : Model, Versions, CPU, CPU MHz, Flash MB_mbflashs, |
| + | header | ||
| + | align | ||
| + | filter | ||
| + | ---- | ||
| Also notable are the mini-PCI slot and Atheros b/g radio. | Also notable are the mini-PCI slot and Atheros b/g radio. | ||
| - | The JTAG is not confirmed to work, but differences between the early versions and later ones show missing resistors on what looks almost certainly to be a JTAG interface. | ||
| ===== Installation ===== | ===== Installation ===== | ||
| + | ---- datatable ---- | ||
| + | cols : Model, Versions, Supported Current Rel, Firmware OpenWrt Install URL_url, Firmware OpenWrt Upgrade URL_url, Firmware OEM Stock URL_url | ||
| + | headers : Model, Version, Current Release, Firmware OpenWrt Install, Firmware OpenWrt Upgrade, Firmware OEM Stock | ||
| + | align : c,c,c | ||
| + | filter | ||
| + | ---- | ||
| + | |||
| + | -> [[docs: | ||
| + | |||
| - | There are numerous ways to install OpenWrt on the WGT634U. | + | There are numerous ways to install OpenWrt on the WGT634U. Unlike many other devices, the WGT634U does not automatically try to fetch an image via TFTP or automatically accept one that is sent. TFTP can only be initiated from a serial console. Images can also be flashed from a running system, either the stock firmware or using the mtd utility from a previous version of OpenWrt. |
| Line 32: | Line 53: | ||
| Unless you manage to overwrite the CFE bootloader, you can flash any image using this method from any state, even semi-bricked, | Unless you manage to overwrite the CFE bootloader, you can flash any image using this method from any state, even semi-bricked, | ||
| - | For more details on this process, see [[docs:user-guide: | + | For more details on this process, see [[docs: |
| * Setup a TFTP server on the local network, placing the appropriate .bin image in the TFTP server space (e.g. '' | * Setup a TFTP server on the local network, placing the appropriate .bin image in the TFTP server space (e.g. '' | ||
| - | * Important: The WGT634U bootloader will not reliably flash an image larger than about 2 megabytes. (This appears to be a limitation of CFE.) If your image is larger than this, as is the case for <b>all recent | + | * Important: The WGT634U bootloader will not reliably flash an image larger than about 2 megabytes. (This appears to be a limitation of CFE.) If your image is larger than this, as is the case for **all recent |
| - | * Attach a [[docs: | + | * Attach a [[docs:techref: |
| * Attach a network cable between the WAN port of the WGT634U and your computer. Configure your computer' | * Attach a network cable between the WAN port of the WGT634U and your computer. Configure your computer' | ||
| Line 44: | Line 65: | ||
| * While holding down Ctrl-C in the serial console, apply power to the WGT634U and the boot should abort at the '' | * While holding down Ctrl-C in the serial console, apply power to the WGT634U and the boot should abort at the '' | ||
| - | * Configure the network interface for a static address in the same subnet as your computer | + | * Configure the network interface for a static address in the same subnet as your computer\\ < |
| - | < | + | |
| CFE> ifconfig eth0 -addr=192.168.1.250 -mask=255.255.255.0 | CFE> ifconfig eth0 -addr=192.168.1.250 -mask=255.255.255.0 | ||
| Device eth0: hwaddr 00-0F-B5-3F-23-6E, | Device eth0: hwaddr 00-0F-B5-3F-23-6E, | ||
| Line 52: | Line 72: | ||
| </ | </ | ||
| - | * Flash the binary file (in two parts, if necessary): | + | * Flash the binary file (in two parts, if necessary):\\ < |
| - | < | + | |
| CFE> flash -noheader < | CFE> flash -noheader < | ||
| CFE> flash -noheader -offset=< | CFE> flash -noheader -offset=< | ||
| </ | </ | ||
| - | * Here is a more explicit example of a two-part flash including the expected responses from the router: it will take only 15 seconds or so to **read** each 2 MiB binary file, but typically **3 minutes** on my device to actually complete the '' | + | * Here is a more explicit example of a two-part flash including the expected responses from the router: it will take only 15 seconds or so to **read** each 2 MiB binary file, but typically **3 minutes** on my device to actually complete the '' |
| - | + | ||
| - | < | + | |
| CFE> flash -noheader 192.168.1.1: | CFE> flash -noheader 192.168.1.1: | ||
| Reading 192.168.0.1: | Reading 192.168.0.1: | ||
| Line 70: | Line 87: | ||
| </ | </ | ||
| - | * Reboot: | + | * Reboot:\\ < |
| - | < | + | |
| - | CFE> reboot | + | |
| - | </ | + | |
| ==== Upgrading OpenWrt ==== | ==== Upgrading OpenWrt ==== | ||
| Line 79: | Line 93: | ||
| === LuCI Web Upgrade Process === | === LuCI Web Upgrade Process === | ||
| - | Download openwrt-brcm47xx-squashfs.trx from openwrt release to your local, from luci interface " | + | Download openwrt-brcm47xx-squashfs.trx from openwrt release to your local, from luci interface " |
| === Terminal Upgrade Process === | === Terminal Upgrade Process === | ||
| Line 95: | Line 109: | ||
| ==== Info ==== | ==== Info ==== | ||
| - | | **Architecture: | + | ^ Architecture |
| - | | **Vendor: | + | ^ Vendor |
| - | | **Bootloader: | + | ^ Bootloader |
| - | | **System-On-Chip:** Broadcom BCM3302 V0.7 (from / | + | ^ System-On-Chip |
| - | | **CPU Speed:** 200 Mhz | | + | ^ CPU Speed |
| - | | **Flash-Chip:** [[http:// | + | ^ Flash-Chip |
| - | | **Flash size:** 8 MiB | | + | ^ Flash size | 8 MiB | |
| - | | **RAM: | + | ^ RAM |
| - | | **Wireless: | + | ^ Wireless |
| - | | **Ethernet: | + | ^ Ethernet |
| - | | **USB: | + | ^ USB |
| - | | **Serial: | + | ^ Serial |
| - | | **JTAG: | + | ^ JTAG | [[# |
| ==== Photos ==== | ==== Photos ==== | ||
| Line 122: | Line 136: | ||
| ==== Opening the case ==== | ==== Opening the case ==== | ||
| - | There are four screws on the bottom. | + | There are four screws on the bottom. They are either phillips head or T-8 Torx. Refurbs tend to have phillips, the originals from Netgear tend to have torx. In the absence of a T-8, a small flathead screwdriver can be used in a pinch. I recommend a Torx if you are going to be opening it more than once. |
| //Main PCB// | //Main PCB// | ||
| Line 130: | Line 144: | ||
| ==== Serial ==== | ==== Serial ==== | ||
| - | The serial console is available on J7. Numbered from the ethernet port side of the board, they are: | + | The serial console is available on J7. Numbered from the ethernet port side of the board, they are: |
| - VCC (3.3V) | - VCC (3.3V) | ||
| Line 137: | Line 151: | ||
| - GROUND | - GROUND | ||
| - | The serial port is the typical 3.3V TTL serial commonly found on router and router-like devices, NOT a PC-style RS-232 serial, with it's different signaling voltages. | + | The serial port is the typical 3.3V TTL serial commonly found on router and router-like devices, NOT a PC-style RS-232 serial, with it's different signaling voltages. It's 115200 8-N-1 without hardware or software control. |
| ==== JTAG ==== | ==== JTAG ==== | ||
| - | There is a JTAG looking port (2 x 7 holes) on the board. | + | The JTAG is not confirmed to work, but differences between the early versions and later ones show missing resistors on what looks almost certainly to be a JTAG interface. |
| + | |||
| + | There is a JTAG looking port (2 x 7 holes) on the board. Except for the very early versions of the board, however, needed surface mount resistors are missing. On the bottom of the board, early versions are populated with 0603 SMD resistors: | ||
| * R66 = 10k ohms | * R66 = 10k ohms | ||
| * R65 = 33 ohms | * R65 = 33 ohms | ||
| Line 148: | Line 164: | ||
| * R73 = 0 ohms (shunt) | * R73 = 0 ohms (shunt) | ||
| - | The pinout is *probably* standard 14-pin, but check and report back. For more information on reflashing the device, see these [[http:// | + | The pinout is *probably* standard 14-pin, but check and report back. For more information on reflashing the device, see these JTAG tools |
| - | See [[docs: | + | See [[docs:techref: |
| ===== Specific Configuration ===== | ===== Specific Configuration ===== | ||
| Line 166: | Line 182: | ||
| FIXME! | FIXME! | ||
| - | NOTE: By default, the physical WAN port lands on the LAN and the last physical LAN port (identified as #4 on the device) is the WAN port. | + | NOTE: By default, the physical WAN port lands on the LAN and the last physical LAN port (identified as #4 on the device) is the WAN port. |
| ==== Failsafe mode ==== | ==== Failsafe mode ==== | ||
| - | Failsafe mode does not work on the WGT634U. | + | Failsafe mode does not work on the WGT634U. If you discover different, report back here. |
| ===== Basic configuration ===== | ===== Basic configuration ===== | ||
| - | Link to [[docs: | + | Link to [[docs: |
| ===== Hardware mods ===== | ===== Hardware mods ===== | ||
| Line 180: | Line 196: | ||
| ==== Replacing the radio ==== | ==== Replacing the radio ==== | ||
| - | Because the radio comes in a mini-PCI slot, it is possible to replace it with a different radio. | + | Because the radio comes in a mini-PCI slot, it is possible to replace it with a different radio. The principal obstacle to this is that the stock antenna is soldered on, and the coax pigtail must be cut or desoldered to remove it. With minor case modifications, |
| The mini-PCI slot is reported to have limited power, making the use of higher powered radios like the Ubiquiti SR2 problematic. | The mini-PCI slot is reported to have limited power, making the use of higher powered radios like the Ubiquiti SR2 problematic. | ||
| Line 199: | Line 215: | ||
| - | Then install USB Storage(install kmod-fs-vfat if you just want fat/ | + | Then install USB Storage(install kmod-fs-vfat if you just want fat/ |
| Or simply run below: | Or simply run below: | ||
| < | < | ||
| Line 207: | Line 223: | ||
| ==== Host USB port uses ==== | ==== Host USB port uses ==== | ||
| - | The USB host port was unique at the time the WGT634U was introduced. | + | The USB host port was unique at the time the WGT634U was introduced. Diverse device driver availability allow the USB port to connect any number of various hardware. For example, by connecting a 4-port hub, a WGT634U with a connected USB GPS, USB Storage and USB sound was used as a kismet wireless stumbling device, playing MP3 audio clips for feedback. |
| Note however, that although the USB port is advertised as USB2 and indeed it is detected as such, it is limited to 12Mbps data rates. | Note however, that although the USB port is advertised as USB2 and indeed it is detected as such, it is limited to 12Mbps data rates. | ||
| - | Another use employed a zd1211 usb radio as a way of implementing a two-radio repeater. | + | Another use employed a zd1211 usb radio as a way of implementing a two-radio repeater. Separating the two radios with a USB extension (up to 5 meters) is probably wise. |
| ==== Avoid 8.09.1! ==== | ==== Avoid 8.09.1! ==== | ||
| Line 219: | Line 235: | ||
| ==== Recovering from Board Information Overwrites ==== | ==== Recovering from Board Information Overwrites ==== | ||
| - | Despite the amazing functionality of these devices, they do not get as much love and attention from OpenWrt developers as they once did. At various stages of history, the board detection logic has become messed up, and distributed versions of the OpenWrt image (see in particular 8.09.1, and Kamikaze Trunk mid-July 2010 to the end of 2010) have overwritten crucial parts of the board configuration information on flash, which renders the device unbootable thereafter. | + | Despite the amazing functionality of these devices, they do not get as much love and attention from OpenWrt developers as they once did. At various stages of history, the board detection logic has become messed up, and distributed versions of the OpenWrt image (see in particular 8.09.1, and Kamikaze Trunk mid-July 2010 to the end of 2010) have overwritten crucial parts of the board configuration information on flash, which renders the device unbootable thereafter. Recovery is not terribly difficult however, with a serial console. Attach the console, boot up to a CFE prompt, and type the following commands: |
| < | < | ||
| Line 233: | Line 249: | ||
| (substituting your own macaddrs, which are printed on the case.) | (substituting your own macaddrs, which are printed on the case.) | ||
| + | |||
| + | ===== Tags ===== | ||
| + | {{tag> | ||