Linksys WRT54G v2.2

Additional FCC IDs of Q87-HGA5T-1 (Linksys HGA5T, high gain antennas), Q87-HGA7T-6 (Linksys HGA7T, high gain antennas)


 * There is an additional certification of W002940 (10/29/2004) for this device which notes added WPA2 capability.

Links of Interest

 * • Downloads (US)


 * WRT54G series on Wikipedia
 * Linksys WRT54Gxx page on the DD-WRT wiki
 * WRT54G page on the OpenWrt wiki
 * Project:DD-WRT/NEWD or VINT
 * Datasheet.pdf
 * Quick Install.pdf
 * User Guide.pdf

Flashing DD-WRT

 * Linksys WRT54G v2.2 On the DD-WRT Wiki
 * VINTage firmware. Details here.


 * 1) Read the peacock announcement found here: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=51486
 * 2) Do a Hard reset or 30/30/30 on the router according to note 1 of the peacock announcement (30/30/30)
 * 3) Set a static IP on your computer to 192.168.1.7. Subnet mask should be 255.255.255.0.
 * 4) Connect the lan cable from your computer to a LAN port of your router. Make sure your router is plugged in. Nothing should be connected to your computer or the router except the lan cable between them. Turn your firewall and any wireless computer connections OFF.
 * 5) Power cycle the router (unplug the power from the router for 30 seconds and then plug it back in)
 * 6) Open your browser to 192.168.1.1 by putting that in the browser address window of your browser. You should open the linksys webgui and NOT a page that says Management Mode. If you see management mode, power cycle the router again.
 * 7) Leave the username blank and enter "admin" as the password
 * 8) Go to administration and firmware upgrade
 * 9) Navigate to the folder that you are using, and select dd-wrt.v24-15230_VINT_mini.bin
 * 10) Hit upgrade
 * 11) When you get a message that the upgrade is successful, wait FIVE FULL minutes before continuing.
 * 12) If you don't get success, repeat from steps 6 up to this one. If you still don't get success, clear your browser cache. Try using a different browser as well, to navigate to 192.168.1.1.
 * 13) When you can access the dd-wrt webgui using a browser at 192.168.1.1, power cycle the router.
 * 14) When you can again access the dd-wrt webgui using a browser at 192.168.1.1, do another Hard reset or 30/30/30 on the router.
 * 15) At this point you can choose to put a different build on, depending on what you needs are.
 * 16) Reset your computer ethernet connection to auto IP and auto DNS
 * 17) Check for recommended builds here.

Flashing OpenWrt
Linksys WRT54G On the OpenWrt Wiki

Using the Linksys web GUI
It is possible to install OpenWrt directly with the Linksys web GUI. If you are initially installing OpenWrt use the Linksys web GUI, this is the easiest way.


 * Download the openwrt-wrt54g-squashfs.bin firmware image from the brcm-2.4 folder to your PC.
 * You can find that image at: http://downloads.openwrt.org/backfire/10.03.1/brcm-2.4/
 * Actually the safest version to use would be  8.09 . Hmmm, it looks like 10.03.1 is safe but you must use the brcm-2.4 variant like in the link above. I am not risking bricking my router for the initial flash, so I am going with 8.09.
 * Open http://192.168.1.1/Upgrade.asp in your browser or manually go to http://192.168.1.1 → Administration → Firmware Upgrade
 * Upload openwrt-wrt54g-squashfs.bin
 * Wait 2 minutes. The router will reboot itself automatically after the upgrade is complete.
 * Your router should now be telnettable at 192.168.1.1. The web interface luci is also available at http://192.168.1.1 . Telnet is disabled and ssh is enabled once a password has been set.
 * Type these commands out in telnet/ssh. This is to ensure that tftp is available, in case your router gets bricked.

nvram set boot_wait=on nvram set boot_time=10 nvram set wait_time=10 #important for some models nvram commit && reboot


 * You're done! At this point, you are free to continue using brcm-2.4. However, if you wish to use brcm47xx, proceed below.
 * Download the image openwrt-brcm47xx-squashfs.trx here: http://downloads.openwrt.org/backfire/10.03.1/brcm47xx/
 * Upload using luci at System > Flash Firmware
 * OR, you can simply ssh into the router,

cd /tmp wget http://downloads.openwrt.org/backfire/10.03.1/brcm47xx/openwrt-brcm47xx-squashfs.trx sysupgrade /tmp/openwrt-brcm47xx-squashfs.trx


 * Wait for the router to reboot and login! In case you somehow found out that you can't telnet, then ssh should be possible since your previous settings before flashing remained (unless you used sysupgrade -n)

Using the TFTP method
Right after flashing at your first login to OpenWrt set the following NVRAM parameters to enable tftpd at bootup:

nvram set boot_wait=on nvram set boot_time=10 nvram set wait_time=10 nvram commit && reboot

NOTE: Do not touch any other NVRAM parameters. NVRAM is only used as environment for the bootloader. OpenWrt ignores NVRAM parameters.

NOTE: On WRT54GL (at least), you should probably use 'wait_time' instead of 'boot_time'. bg300: Added.

NOTE: On WRT54GS v1.1 too you have to use 'wait_time' instead of 'boot_time', anyway if in doubt add both parameters.

Once you have set the NVRAM parameters above it is possible to use a TFTP client to flash OpenWrt. The TFTP method is also the recommended way to restore the original Linksys firmware or switch to other third-party firmwares.

First download a firmware image file ending in ".bin", e.g. openwrt-wrt54g-squashfs.bin.

Then follow the Generic TFTP flashing instructions.

Flashing Tomato
????

Flashing Gargoyle
Install Guide

Using mtd OR sysupgrade
If you have already installed OpenWrt and like to reflash for e.g. upgrading to a new OpenWrt version. It is important that you put the firmware image into the ramdisk (/tmp) before you start flashing.

cd /tmp/ wget http://downloads.openwrt.org/backfire/10.03.1/brcm47xx/openwrt-brcm47xx-squashfs.trx # The file must be the trx file. mtd write /tmp/openwrt-brcm47xx-squashfs.trx linux && reboot

OR

cd /tmp/ wget http://downloads.openwrt.org/backfire/10.03.1/brcm47xx/openwrt-brcm47xx-squashfs.trx # The file must be the trx file. sysupgrade /tmp/openwrt-brcm47xx-squashfs.trx

Feel free to explore the rest of sysupgrade options by typing 'sysupgrade' in the terminal.

Using LuCI

 * 1) Select Administration in the top right corner
 * 2) Choose the System > Flash Firmware tab
 * 3) Click Browse and navigate to the firmware (it must be a .trx file) you wish to flash to
 * 4) Click 'Upload image'
 * 5) Follow the instructions

Upgrading from Tomato
The instructions from the Tomato upgrade instructions are confirmed to work with Backfire (10.03.1-rc4, r24045)

Reverting to OEM Firmware from DD-WRT

 * 1) Read the peacock announcement found here: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=51486
 * 2) Do a Hard reset or 30/30/30 on the router according to note 1 of the peacock announcement (30/30/30)
 * 3) Set a static IP on your computer to 192.168.1.7. Subnet mask should be 255.255.255.0.
 * 4) Connect the lan cable from your computer to a LAN port of your router. Make sure your router is plugged in. Nothing should be connected to your computer or the router except the lan cable between them. Turn your firewall and any wireless computer connections OFF.
 * 5) Power cycle the router (uplug the power from the router for 30 seconds and then plug it back in)
 * 6) Open your browser to 192.168.1.1 by putting that in the browser address window of your browser. You should open the linksys webgui and NOT a page that says Management Mode. If you see management mode, power cycle the router again.
 * 7) Enter your username and password
 * 8) Go to administration and firmware upgrade
 * 9) Navigate to the folder that you are using, and select WRT54G_v4.21.1_fw.bin once you've unzipped it.
 * 10) Hit upgrade
 * 11) When you get a success, wait FIVE FULL minutes.
 * 12) When you can again access the Linksys webgui using a browser at 192.168.1.1, do another Hard reset or 30/30/30 on the router.
 * 13) Reset your computer ethernet connection to auto IP and auto DNS

JTAG Pinouts
 nTRST  1o o2	GND TDI  3o o4	GND TDO  5o o6	GND TMS  7o o8	GND TCK  9o o10	GND nSRST 11o o12  N/C Using Universal JTAG Adapter  white   1o o2	 black red   3o o4	 GND blue   5o o6	 GND green   7o o8	 GND yelow   9o o10  GND orange 11o o12  N/C

DD-WRT JTAG Recovery

 * /noemw switch required for backup & flash
 * /noemw /nocwd switches required for erase


 * 1) Backup CFE x2 (Compare the files, they must match exactly or there is something wrong with your JTAG setup)
 * 2) Erase Wholeflash x2
 * 3) Flash CFE
 * 4) Unplug Power
 * 5) Unplug JTAG Cable

TFTP:


 * 1) Set Rig ip static 192.168.1.10
 * 2) Plug network cable from rig to port 1
 * 3) Get TFTP ready, server ip - 192.168.1.1, Password - blank, file - dd-wrt.v24_mini_generic.bin
 * 4) Plug in power
 * 5) As soon as windows says "connected" hit upgrade. May have to use a network hub to make sure windows is always connected.
 * 6) Hard Reset 30\30\30

Serial Pinouts
 VCC 1 o o 2  VCC TX1 3 o o 4  TX0 RX1 5 o o 6  RX0 N/C 7 o o 8  N/C GND 9 o o 10 GND

DD-WRT 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_mini_wrt54g.bin
 * 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, hit enter
 * 8) type "flash -noheader : flash1.trx" w/o quotes, this starts the tftp daemon, hit enter
 * 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 or 30/30/30...then config
 * 14) you'll see it boot up

DD-WRT vlan Info

 * Project:DD-WRT/VLAN Support

Confirmed the WRT54G v2.2 supports port-based vlans via the GUI & nvram.

"/proc/switch/eth0" does exist

WRT54G v2.2's ports are mapped like this:

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

Defaults
root@DD-WRT:~# nvram show | grep vlan.ports vlan0ports=3 2 1 0 5* vlan1ports=4 5 size: 19306 bytes (13462 left) root@DD-WRT:~# nvram show | grep port.vlans port5vlans=0 1 16 port4vlans=0 port3vlans=0 port2vlans=0 port1vlans=0 port0vlans=1 size: 19306 bytes (13462 left) root@DD-WRT:~# nvram show | grep vlan.hwname vlan1hwname=et0 vlan0hwname=et0 size: 19306 bytes (13462 left)

GUI
Port 4 moved to WAN's vlan

root@DD-WRT:~# nvram show | grep vlan.ports vlan0ports=3 2 1 0 5* vlan1ports=4 5 size: 19478 bytes (13290 left) root@DD-WRT:~# nvram show | grep port.vlans port5vlans=0 1 16 port4vlans=1 18 19 port3vlans=0 18 19 port2vlans=0 18 19 port1vlans=0 18 19 port0vlans=1 18 19 size: 19478 bytes (13290 left) root@DD-WRT:~# nvram show | grep vlan.hwname vlan1hwname=et0 vlan0hwname=et0 size: 19478 bytes (13290 left) root@DD-WRT:~#

nvram
Port 4 moved to WAN's vlan

root@DD-WRT:~# nvram show | grep vlan.ports vlan0ports=2 1 0 5* vlan1ports=3 4 5 size: 19420 bytes (13348 left) root@DD-WRT:~# nvram show | grep port.vlans port5vlans=0 1 16 port4vlans=0 port3vlans=0 port2vlans=0 port1vlans=0 port0vlans=1 size: 19420 bytes (13348 left) root@DD-WRT:~# nvram show | grep vlan.hwname vlan1hwname=et0 vlan0hwname=et0 size: 19420 bytes (13348 left) root@DD-WRT:~# lsmod Module                 Size  Used by ip_nat_pptp             2560   0 (unused) ip_conntrack_pptp      3036   1 ip_nat_proto_gre       1664   0 (unused) ip_conntrack_proto_gre   2584   0 [ip_nat_pptp ip_conntrack_pptp] etherip                5104   0 (unused) switch-robo            5356   0 (unused) switch-core            6352   0 [switch-robo] root@DD-WRT:~# ls /proc/switch eth0 root@DD-WRT:~# cat /proc/switch/eth0/vlan/0/ports 0      1       2       5t* root@DD-WRT:~# cat /proc/switch/eth0/vlan/1/ports 3      4       5t root@DD-WRT:~# cat /proc/switch/eth0/vlan/2/ports 3 root@DD-WRT:~# nvram show | grep vlan.ports vlan0ports=2 1 0 5* vlan1ports=3 4 5 size: 19560 bytes (13208 left) root@DD-WRT:~#

Pictures
DarkShadow's Unit 

Rare 32MB
anectine17 wrote: The v.2 and v.2.2, on occasion, came with a 32MB RAM chip with only 16MB enabled. The vast majority of these routers came with a basic 16MB RAM chip. To tell whether or not you have the "special" one with the 32MB chip, you have to open the router and read the number on the RAM chip itself. If you have chip #issi is42s16800a-7t, you can enter nvram set sdram_init=0x008 nvram set sdram_ncdl=0x000 nvram commit reboot and that will enable all 32MB. If you have any other chip, that hack will not work...in fact if you try it, you'll end up with a brick. Good luck.

The SK hynix chip, HY5DU281622ET-J is the most common one in the v.2 and v.2.2. I've taken apart probably 50 v.2's and a dozen 2.2's and I've seen 2 of the 32MB chips in the v.2.2, and 4 in the v.2. They're out there, but getting harder and harder to come by. Most people hang on to them once they get them.