User Tools

Site Tools


toh:linksys:toh:linksys:wrt350n

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

toh:linksys:toh:linksys:wrt350n [2012/12/29 03:32]
billf ported from the old wiki entry
toh:linksys:toh:linksys:wrt350n [2012/12/29 03:47] (current)
billf
Line 1: Line 1:
-====== Linksys WRT350N v1.0 ====== +DELETEME %% DELETEME %%
- +
-===== Identification by S/N ===== +
- +
-Useful for identifying shrinkwrapped units. The **S/N** can be found on the box, below the UPC barcode. +
-| |  (!) **Please contribute to this list.** (!) |  +
-| ^ Model ^ S/N ^ +
-| | WRT350N v1.0 -- Not available in Europe? |  CNQ01 |  +
-| | WRT350N v2.0 -- Only available in Europe? |  SNQ00 |  +
- +
-===== Hardware ===== +
-The WRT350N v1.0 is based on the Broadcom 4785 r2 running at 300MHz cpu. It has 8 MB flash and 32 MB SDRAM. The wireless NIC is a Broadcom Cardbus card with maybe a BCM5397 Chipset on the switch. ​ The WRT350N runs 802.11 B, G, and Draft N wireless protocols. It provides 4 gigabit LAN ports, 1 WAN port and a USB '​storage link' port. +
- +
-===== OpenWRT Firmware ===== +
-It is possible to run an older kamikaze bcrm-2.4 version of OpenWRT on the v1.0 hardware. ​ You may need to build this yourself to enable the required drivers. +
- +
-Support for the wrt350n v1.0 was added to SVN with changesets 11466-11471 (broadcom 2.4 build). ​ In order to use the device, make sure the bcm57xx package is included in your image (selected as * in menuconfig). ​ Without this package installed, the switch will not come up and you'll have to use a serial console to recover. +
- +
-Wireless works as long as kmod-brcm-wl-mimo is installed. ​ USB also works with kmod-usb-ohci,​ I have tested it as a print server with p9100d. +
- +
-===== A note about NVRAM ===== +
- +
-The switch in the wrt350n v1 is a little different from the older switch chips. ​ By default, it will forward packets between the LAN and WAN, much like a normal switch. ​ This is a problem during bootup because boot_wait will activate the switch to wait for an image. ​ The only way I could find to make the switch not forward packets on bootup was to set the following NVRAM variables:​ +
- +
-//Disabling boot_wait is a bad idea, so make sure you really need it off before doing so.// +
-<​code>​ +
-nvram set boot_wait=off +
-nvram set manual_boot_nv=1 +
-nvram unset disabled_57xx +
-nvram commit +
-</​code>​ +
- +
-===== Flashing ===== +
-WARNING: Flashing the pre-build openwrt-wrt350n_v1-squashfs.bin from downloads.openwrt.org could very well disable all ethernet ports on the router, forcing you to install a serial port to recover. ​ Search the forums and you'll see that happened to a bunch of people (include yours truely), so be warned. +
- +
-===== CFE Bootloader ===== +
- +
-The CFE bootloader brings up the ethernet with IP 192.168.1.1 and listens for a TFTP "​put"​ for a few seconds. ​ If a file is uploaded via TFTP, the header is read and the board type and checksum is validated before it is programmed into flash. ​ The default firmware image from OpenWRT may not have the required header. ​ This can be dealt with via the serial port like so: +
- +
-Start sending the firmware from a linux computer on the same network: +
-<​code>​ +
-echo -e "​binary\nrexmt 1\ntimeout 60\ntrace\nput openwrt-wrt350n_v1-squashfs.bin\n"​ | tftp 192.168.1.1 +
-</​code>​ +
-Receive the firmware file and program it to flash: +
-<​code>​ +
-flash -ctheader : flash1.trx +
-</​code>​+
toh/linksys/toh/linksys/wrt350n.txt · Last modified: 2012/12/29 03:47 by billf