NSLU2-Linux
view · edit · print · history

WRP400.HomePage History

Hide minor edits - Show changes to markup

September 03, 2010, at 12:21 AM by krim --
Changed lines 19-20 from:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this and the newer 2.00.05 firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack. You are also able to downgrade/upgrade from 2.00.05, 1.00.06 and 1.00.04c at any time. However after a 2.00.05 firmware upgrade it seems that the boot loader is replaced with a more limited version of uboot.

to:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this and the newer 2.00.05 firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack. You are also able to downgrade/upgrade from 2.00.05, 1.00.06 and 1.00.04c at any time. However after a 2.00.05 firmware upgrade it seems that the boot loader is replaced with a more limited version of uboot and you can not revert by downgrading.

September 03, 2010, at 12:17 AM by krim --
Changed lines 5-6 from:

There are no known software-only exploits for this device. For ProvisionedDevices? there is no known way to unlock it yet.

to:

There are no known software-only exploits for this device. For ProvisionedDevices? there are no known unlock methods yet.

September 03, 2010, at 12:15 AM by krim --
Changed lines 5-6 from:

There are no known software-only exploits for this device. If it is a ProvisionedDevice there is no known way to unlock it yet.

to:

There are no known software-only exploits for this device. For ProvisionedDevices? there is no known way to unlock it yet.

September 03, 2010, at 12:05 AM by krim --
Changed lines 19-20 from:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this and the newer 2.00.05 firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack. You are also able to downgrade/upgrade from 2.00.05, 1.00.06 and 1.00.04c at any time. However after a 2.00.05 firmware upgrade it seems that the UbootConsole has limited commands.

to:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this and the newer 2.00.05 firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack. You are also able to downgrade/upgrade from 2.00.05, 1.00.06 and 1.00.04c at any time. However after a 2.00.05 firmware upgrade it seems that the boot loader is replaced with a more limited version of uboot.

September 02, 2010, at 11:52 PM by krim --
Changed lines 19-20 from:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this and the newer 2.00.05 firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack. You are also able to downgrade/upgrade from 2.00.05, 1.00.06 and 1.00.04c at any time.

to:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this and the newer 2.00.05 firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack. You are also able to downgrade/upgrade from 2.00.05, 1.00.06 and 1.00.04c at any time. However after a 2.00.05 firmware upgrade it seems that the UbootConsole has limited commands.

September 02, 2010, at 07:46 PM by krim --
Changed lines 5-6 from:

There are no known software-only exploits for this device. If it is a ServiceProvidedDevice there is no known way to unlock it yet.

to:

There are no known software-only exploits for this device. If it is a ProvisionedDevice there is no known way to unlock it yet.

September 02, 2010, at 06:49 PM by krim -- ServiceProvidedDevice
Changed lines 5-6 from:

There are no known software-only exploits for this device. If you have a ServiceProvidedDevice there is no known way to unlock it yet.

to:

There are no known software-only exploits for this device. If it is a ServiceProvidedDevice there is no known way to unlock it yet.

September 02, 2010, at 06:46 PM by krim -- ServiceProvidedDevice
Changed lines 5-6 from:

There are no known software-only exploits for this device.

to:

There are no known software-only exploits for this device. If you have a ServiceProvidedDevice there is no known way to unlock it yet.

Changed lines 9-10 from:

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort (see the VendorBootLog and VendorRecoveryBootLog), however it turns out you can UnlockTheConsole and enable the TftpServer by using some SecretCGICommands and the ShadowDataHack to change the UBootVariables and enable login as the "admin" user (which is equivalent to root on this device) on the SerialPort. The KernelCmdline informs the kernel of the console lock state and the serial console driver is consequently enabled or disabled. It does have an interesting set of OpenPorts though.

to:

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort (see the VendorBootLog and VendorRecoveryBootLog), however it turns out you can UnlockTheConsole and enable the TftpServer by using some SecretCGICommands and the ShadowDataHack to change the UBootVariables and enable login as the "admin" user (which is equivalent to root on this device) on the SerialPort. The KernelCmdline informs the kernel of the console lock state and the serial console driver is consequently enabled or disabled. It does have an interesting set of OpenPorts though.

September 02, 2010, at 06:36 PM by krim -- typo
Changed lines 19-20 from:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this and the newer 2.00.05 firmwaere has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack. You are also able to downgrade/upgrade from 2.00.05, 1.00.06 and 1.00.04c at any time.

to:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this and the newer 2.00.05 firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack. You are also able to downgrade/upgrade from 2.00.05, 1.00.06 and 1.00.04c at any time.

September 02, 2010, at 06:35 PM by krim --
Changed lines 19-20 from:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack. You are also able to downgrade/upgrade from 2.00.05, 1.00.06 and 1.00.04c at any time.

to:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this and the newer 2.00.05 firmwaere has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack. You are also able to downgrade/upgrade from 2.00.05, 1.00.06 and 1.00.04c at any time.

September 02, 2010, at 06:32 PM by krim --
Changed lines 19-20 from:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack. You are also able to downgrade from 2.00.05, 1.00.06 and 1.00.04c at any time.

to:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack. You are also able to downgrade/upgrade from 2.00.05, 1.00.06 and 1.00.04c at any time.

September 02, 2010, at 06:30 PM by krim -- downgrade from 2.00.05 confirmed
Changed lines 19-22 from:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack. You are also able to downgrade from 1.00.06 to 1.00.04c at any time.

There is now version 2.00.05 firmware and source code available, but this has not been tested yet.

to:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack. You are also able to downgrade from 2.00.05, 1.00.06 and 1.00.04c at any time.

November 30, 2009, at 08:10 AM by rwhitby --
Changed lines 11-12 from:

There is no known way to access the command line or install custom firmware or packages on this device without performing hardware modifications to add a SerialPort. The firmware upgrade images are protected with an encrypted hash of the contents, and the encryption algorithm is not known. Therefore there is no way to create modified firmware upgrade images at the moment.

to:

There is no known way to access the command line or install custom firmware or packages on this device without performing hardware modifications to add a SerialPort. The firmware upgrade images are protected with an encrypted hash of the contents, and the encryption algorithm is not known. Therefore there is no way to create modified firmware upgrade images at the moment. Even after you have achieved root access, to flash custom firmware partial images onto the device you need to revert back to the 1.00.04.c firmware to be able to install an unencrypted firmware partial image.

November 29, 2009, at 11:29 PM by rwhitby --
Added lines 21-22:

There is now version 2.00.05 firmware and source code available, but this has not been tested yet.

February 25, 2009, at 11:35 AM by rwhitby --
Added lines 20-21:

We have so far been able to UnpackTheFirmware and ModifyTheRootFS to enable an ssh server on the device.

February 25, 2009, at 11:02 AM by rwhitby --
Changed lines 9-10 from:

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort (see the VendorBootLog and VendorRecoveryBootLog), however it turns out you can UnlockTheConsole and enable the TftpServer by using some SecretCGICommands and the ShadowDataHack to change the UBootVariables and enable login as root on the SerialPort. The KernelCmdline informs the kernel of the console lock state and the serial console driver is consequently enabled or disabled. It does have an interesting set of OpenPorts though.

to:

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort (see the VendorBootLog and VendorRecoveryBootLog), however it turns out you can UnlockTheConsole and enable the TftpServer by using some SecretCGICommands and the ShadowDataHack to change the UBootVariables and enable login as the "admin" user (which is equivalent to root on this device) on the SerialPort. The KernelCmdline informs the kernel of the console lock state and the serial console driver is consequently enabled or disabled. It does have an interesting set of OpenPorts though.

February 25, 2009, at 10:52 AM by rwhitby --
Changed lines 9-10 from:

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort (see the VendorBootLog and VendorRecoveryBootLog), however it turns out you can UnlockTheConsole and enable the TftpServer by using some SecretCGICommands. The KernelCmdline informs the kernel of the console lock state and the serial console driver is consequently enabled or disabled. It does have an interesting set of OpenPorts though.

to:

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort (see the VendorBootLog and VendorRecoveryBootLog), however it turns out you can UnlockTheConsole and enable the TftpServer by using some SecretCGICommands and the ShadowDataHack to change the UBootVariables and enable login as root on the SerialPort. The KernelCmdline informs the kernel of the console lock state and the serial console driver is consequently enabled or disabled. It does have an interesting set of OpenPorts though.

February 25, 2009, at 09:07 AM by rwhitby --
Changed lines 11-12 from:

There is no way to access the command line or install custom firmware or packages on this device without performing hardware modifications to add a SerialPort.

to:

There is no known way to access the command line or install custom firmware or packages on this device without performing hardware modifications to add a SerialPort. The firmware upgrade images are protected with an encrypted hash of the contents, and the encryption algorithm is not known. Therefore there is no way to create modified firmware upgrade images at the moment.

February 25, 2009, at 09:05 AM by rwhitby --
Changed lines 11-12 from:

That that there is no way to access the command line or install custom firmware or packages on this device without performing hardware modifications to add a SerialPort.

to:

There is no way to access the command line or install custom firmware or packages on this device without performing hardware modifications to add a SerialPort.

February 25, 2009, at 09:04 AM by rwhitby --
Added lines 5-6:

There are no known software-only exploits for this device.

Added lines 11-12:

That that there is no way to access the command line or install custom firmware or packages on this device without performing hardware modifications to add a SerialPort.

February 25, 2009, at 08:59 AM by rwhitby -- The core team has a new unit for development.
Changed lines 5-6 from:

At the moment, it is not supported by Optware. The unit that the core developers had now has a busted serial port, and optware development for the WRP400 has stopped.

to:

At the moment, it is not yet supported by Optware.

Deleted lines 15-16:
February 25, 2009, at 08:49 AM by rwhitby --
Changed lines 7-8 from:

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort, however it turns out you can UnlockTheConsole and enable the TftpServer by using some SecretCGICommands. The KernelCmdline informs the kernel of the console lock state and the serial console driver is consequently enabled or disabled. It does have an interesting set of OpenPorts though.

to:

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort (see the VendorBootLog and VendorRecoveryBootLog), however it turns out you can UnlockTheConsole and enable the TftpServer by using some SecretCGICommands. The KernelCmdline informs the kernel of the console lock state and the serial console driver is consequently enabled or disabled. It does have an interesting set of OpenPorts though.

February 11, 2009, at 02:22 AM by rwhitby -- support status
Added lines 5-6:

At the moment, it is not supported by Optware. The unit that the core developers had now has a busted serial port, and optware development for the WRP400 has stopped.

July 11, 2008, at 01:19 PM by rwhitby --
Changed lines 13-14 from:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack.

to:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack. You are also able to downgrade from 1.00.06 to 1.00.04c at any time.

July 11, 2008, at 07:36 AM by rwhitby --
Changed lines 13-14 from:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole.

to:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole or apply the ShadowDataHack.

July 11, 2008, at 07:34 AM by rwhitby --
Changed lines 13-18 from:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this firmware has not been tested yet.

to:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this firmware has been flashed and will not undo any actions you've taken to UnlockTheConsole.

July 11, 2008, at 05:13 AM by rwhitby --
Changed lines 13-18 from:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1[1].00.06_fw.bin - this firmware has not been tested yet.

to:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1%5B1%5D.00.06_fw.bin - this firmware has not been tested yet.

July 11, 2008, at 05:12 AM by rwhitby --
Changed lines 13-18 from:

The firmware binary corresponding to the later version 1.00.6 source code has not been located.

to:

The firmware binary corresponding to the later version 1.00.6 source code has been located at ftp://ftp.linksys.com/downloads/NA/firmware/WRP400_v1[1].00.06_fw.bin - this firmware has not been tested yet.

July 10, 2008, at 01:20 PM by rwhitby --
Changed lines 5-6 from:

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort, however it turns out you can UnlockTheConsole and enable the TftpServer by using some SecretCGICommands. The KernelCmdline informs the kernel of the console lock state and the serial console driver is consequently enabled or disabled.

to:

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort, however it turns out you can UnlockTheConsole and enable the TftpServer by using some SecretCGICommands. The KernelCmdline informs the kernel of the console lock state and the serial console driver is consequently enabled or disabled. It does have an interesting set of OpenPorts though.

July 09, 2008, at 07:07 AM by rwhitby --
Changed lines 5-6 from:

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort, however it turns out you can UnlockTheConsole by using some SecretCGICommands. The KernelCmdline informs the kernel of the console lock state and the serial console driver is consequently enabled or disabled.

to:

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort, however it turns out you can UnlockTheConsole and enable the TftpServer by using some SecretCGICommands. The KernelCmdline informs the kernel of the console lock state and the serial console driver is consequently enabled or disabled.

July 08, 2008, at 07:58 AM by rwhitby --
Changed lines 11-12 from:

You can find version 1.00.4.c EncapsulatedFirmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip - this firmware has been verified to contain the same image contents as extracted from the BootFlash of a WRP400 purchased in Australia in May 2008, and has been found safe to use for a Web Firmware Upgrade (as can be seen by the UpgradeLog).

to:

You can find an EncapsulatedFirmware image at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip - this firmware has been verified to contain the same image contents as extracted from the BootFlash of a WRP400 purchased in Australia in May 2008, and has been found safe to use for a Web Firmware Upgrade (as can be seen by the UpgradeLog).

July 08, 2008, at 05:25 AM by rwhitby --
Changed lines 11-12 from:

You can find version 1.00.4.c firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip - this firmware has been verified to contain the same image contents as extracted from the BootFlash of a WRP400 purchased in Australia in May 2008, and has been found safe to use for a Web Firmware Upgrade (as can be seen by the UpgradeLog).

to:

You can find version 1.00.4.c EncapsulatedFirmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip - this firmware has been verified to contain the same image contents as extracted from the BootFlash of a WRP400 purchased in Australia in May 2008, and has been found safe to use for a Web Firmware Upgrade (as can be seen by the UpgradeLog).

July 08, 2008, at 04:09 AM by rwhitby --
Changed lines 11-12 from:

You can find version 1.00.4.c firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip - this firmware has been verified to contain the same image contents as found on a WRP400 purchased in Australia in May 2008, and has been found safe to use for a Web Firmware Upgrade (as can be seen by the UpgradeLog).

to:

You can find version 1.00.4.c firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip - this firmware has been verified to contain the same image contents as extracted from the BootFlash of a WRP400 purchased in Australia in May 2008, and has been found safe to use for a Web Firmware Upgrade (as can be seen by the UpgradeLog).

Changed lines 15-18 from:
to:
July 08, 2008, at 04:08 AM by rwhitby --
Changed lines 11-12 from:

You can find version 1.00.4.c firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip - this firmware has been verified to contain the same image contents as found on a WRP400 bought in Australia in May 2008, and has been found safe to use for a Web Firmware Upgrade (as can be seen by the UpgradeLog).

to:

You can find version 1.00.4.c firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip - this firmware has been verified to contain the same image contents as found on a WRP400 purchased in Australia in May 2008, and has been found safe to use for a Web Firmware Upgrade (as can be seen by the UpgradeLog).

July 08, 2008, at 04:08 AM by rwhitby --
Changed lines 11-12 from:

You can find version 1.00.4.c firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip - this firmware has been verified to contain the same image contents as found on a WRP400 bought in Australia in May 2008, and has been found safe to use for a Web Firmware Upgrade.

to:

You can find version 1.00.4.c firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip - this firmware has been verified to contain the same image contents as found on a WRP400 bought in Australia in May 2008, and has been found safe to use for a Web Firmware Upgrade (as can be seen by the UpgradeLog).

Changed lines 17-18 from:
to:
July 08, 2008, at 04:07 AM by rwhitby --
Changed lines 11-12 from:

You can find version 1.00.4.c firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip, but the firmware binary corresponding to the later version 1.00.6 source code has not been located.

to:

You can find version 1.00.4.c firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip - this firmware has been verified to contain the same image contents as found on a WRP400 bought in Australia in May 2008, and has been found safe to use for a Web Firmware Upgrade.

The firmware binary corresponding to the later version 1.00.6 source code has not been located.

July 08, 2008, at 03:39 AM by rwhitby --
Added lines 15-16:
July 07, 2008, at 08:17 AM by rwhitby --
Added lines 5-8:

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort, however it turns out you can UnlockTheConsole by using some SecretCGICommands. The KernelCmdline informs the kernel of the console lock state and the serial console driver is consequently enabled or disabled.

An OpenWrt Forum thread at http://forum.openwrt.org/viewtopic.php?pid=67961 documents the initial investigations into the locking technology used in this device.

Deleted lines 12-15:

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort, however it turns out you can UnlockTheConsole by using some SecretCGICommands. The KernelCmdline informs the kernel of the console lock state and the serial console driver is consequently enabled or disabled.

An OpenWrt Forum thread at http://forum.openwrt.org/viewtopic.php?pid=67961 documents the initial investigations into the locking technology used in this device.

July 07, 2008, at 08:01 AM by rwhitby --
Changed lines 7-8 from:

You can find version 1.00.4.c firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip, but the firmware binary corresponding to the later 1.00.6.c source code has not been located.

to:

You can find version 1.00.4.c firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip, but the firmware binary corresponding to the later version 1.00.6 source code has not been located.

July 07, 2008, at 08:00 AM by rwhitby --
Changed lines 7-8 from:

You can find version 1.00.4.c firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip, but the

to:

You can find version 1.00.4.c firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip, but the firmware binary corresponding to the later 1.00.6.c source code has not been located.

July 07, 2008, at 07:59 AM by rwhitby --
Changed lines 7-12 from:

You can find firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort, however it turns out you can UnlockTheConsole by using some SecretCGICommands. The KernelCmdline informs the kernel of the console lock state and the serial console driver is only enabled

There is an OpenWrt Forum thread at http://forum.openwrt.org/viewtopic.php?pid=67961

to:

You can find version 1.00.4.c firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip, but the

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort, however it turns out you can UnlockTheConsole by using some SecretCGICommands. The KernelCmdline informs the kernel of the console lock state and the serial console driver is consequently enabled or disabled.

An OpenWrt Forum thread at http://forum.openwrt.org/viewtopic.php?pid=67961 documents the initial investigations into the locking technology used in this device.

July 07, 2008, at 07:48 AM by rwhitby --
Changed lines 9-10 from:

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort, however it turns out you can UnlockTheConsole by using some SecretCGICommands.

to:

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort, however it turns out you can UnlockTheConsole by using some SecretCGICommands. The KernelCmdline informs the kernel of the console lock state and the serial console driver is only enabled

Deleted lines 14-15:
Deleted line 15:
July 07, 2008, at 07:15 AM by rwhitby --
Added lines 15-16:
July 07, 2008, at 04:35 AM by rwhitby --
Added lines 13-14:
July 07, 2008, at 02:40 AM by rwhitby --
Changed lines 5-6 from:

Here are some PhotosOfTheInternals, and the SourceCode is available.

to:

Here are some high resolution PhotosOfTheInternals, and the Linksys GPL SourceCode is available.

July 07, 2008, at 02:39 AM by rwhitby --
Changed lines 1-2 from:
to:
July 07, 2008, at 02:33 AM by rwhitby --
Changed lines 1-2 from:
to:
July 07, 2008, at 02:33 AM by rwhitby --
Added lines 1-2:
Changed lines 7-8 from:

You can find firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip

to:

You can find firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip

July 07, 2008, at 02:32 AM by rwhitby --
Changed lines 1-2 from:

The Linksys WRP400 is a Wireless-G Broadband Router with 2 Phone Ports.

to:

The Linksys WRP400 is a Wireless-G Broadband Router with 2 Phone Ports.

Changed lines 5-6 from:

You can find firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip

to:

You can find firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip

July 07, 2008, at 02:32 AM by rwhitby --
Changed lines 1-2 from:

The Linksys WRP400 is a Wireless-G Broadband Router with 2 Phone Ports.

to:

The Linksys WRP400 is a Wireless-G Broadband Router with 2 Phone Ports.

July 07, 2008, at 02:28 AM by rwhitby --
Changed lines 1-9 from:

PhotosOfTheInternals

Firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip

SourceCode

OpenWrt Forum thread: http://forum.openwrt.org/viewtopic.php?pid=67961

to:

The Linksys WRP400 is a Wireless-G Broadband Router with 2 Phone Ports.

Here are some PhotosOfTheInternals, and the SourceCode is available.

You can find firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip

By default, this box is locked down so tight that you can't even get into it by soldering on a SerialPort, however it turns out you can UnlockTheConsole by using some SecretCGICommands.

There is an OpenWrt Forum thread at http://forum.openwrt.org/viewtopic.php?pid=67961

Deleted lines 12-15:
July 07, 2008, at 01:57 AM by rwhitby --
Changed lines 1-2 from:

PCB Pictures at http://www.nslu2-linux.org/gallery/wrp400 (temporarily at http://logs.nslu2-linux.org/wrp400 until the Gallery upload is fixed).

to:
July 07, 2008, at 01:54 AM by rwhitby --
Changed lines 5-6 from:
to:
Changed lines 9-14 from:

From examination of the source code, it seems that the WRP400 is just a rebranded version of the CyberTan WGV414 (http://www.cybertan.com.tw/Products/WGV414.htm).

The source code does not build on Ubuntu, but does build on CentOS 5, and looks like it builds the "cybertan_rom_bin" image (which contains the second rootfs listed below). It also builds the u-boot binary, including the secret console-locking code. What seems to be missing is means to build the "cybertan_half_bin" image, and the tool to turn those images into a flashable binary (with the "WRP400 FiRmWaRe" header).

The u-boot configuration in the source code is "cywgv414dls".

to:
July 07, 2008, at 01:51 AM by rwhitby --
Added lines 18-20:
July 07, 2008, at 01:45 AM by rwhitby --
Added lines 16-17:
July 07, 2008, at 01:44 AM by rwhitby --
Added lines 7-8:

OpenWrt Forum thread: http://forum.openwrt.org/viewtopic.php?pid=67961

July 07, 2008, at 01:43 AM by rwhitby --
Changed lines 9-10 from:

The source code does not build on Ubuntu, but does build on CentOS 5, and looks like it builds the "cybertan_rom_bin" image (which contains the second rootfs listed below). It also builds the u-boot binary, including the secret console-locking code. What seems to be missing is means to build the "cybertan_half_bin" image, and the tool to turn those images into a flashable binary (with the "WRP400 FiRmWaRe?" header).

to:

The source code does not build on Ubuntu, but does build on CentOS 5, and looks like it builds the "cybertan_rom_bin" image (which contains the second rootfs listed below). It also builds the u-boot binary, including the secret console-locking code. What seems to be missing is means to build the "cybertan_half_bin" image, and the tool to turn those images into a flashable binary (with the "WRP400 FiRmWaRe" header).

July 07, 2008, at 01:43 AM by rwhitby --
Changed lines 9-10 from:

The source code does not build on Ubuntu, but does build on CentOS? 5, and looks like it builds the "cybertan_rom_bin" image (which contains the second rootfs listed below). It also builds the u-boot binary, including the secret console-locking code. What seems to be missing is means to build the "cybertan_half_bin" image, and the tool to turn those images into a flashable binary (with the "WRP400 FiRmWaRe?" header).

to:

The source code does not build on Ubuntu, but does build on CentOS 5, and looks like it builds the "cybertan_rom_bin" image (which contains the second rootfs listed below). It also builds the u-boot binary, including the secret console-locking code. What seems to be missing is means to build the "cybertan_half_bin" image, and the tool to turn those images into a flashable binary (with the "WRP400 FiRmWaRe?" header).

July 07, 2008, at 01:43 AM by rwhitby --
Changed lines 7-8 from:

From examination of the source code, it seems that the WRP400 is just a rebranded version of the CyberTan? WGV414? (http://www.cybertan.com.tw/Products/WGV414.htm).

to:

From examination of the source code, it seems that the WRP400 is just a rebranded version of the CyberTan WGV414 (http://www.cybertan.com.tw/Products/WGV414.htm).

July 07, 2008, at 01:42 AM by rwhitby --
Changed lines 1-2 from:

PCB Pictures at http://www.nslu2-linux.org/gallery/wrp400

to:

PCB Pictures at http://www.nslu2-linux.org/gallery/wrp400 (temporarily at http://logs.nslu2-linux.org/wrp400 until the Gallery upload is fixed).

July 07, 2008, at 01:42 AM by rwhitby -- Linksys WRP400
Added lines 1-13:

PCB Pictures at http://www.nslu2-linux.org/gallery/wrp400

Firmware at http://firmware.linksys-cisco.cz/WRP400/WRP400_v1.00.04.c_ETSI.zip

Source code at ftp://ftp.linksys.com/opensourcecode/wrp400/

From examination of the source code, it seems that the WRP400 is just a rebranded version of the CyberTan? WGV414? (http://www.cybertan.com.tw/Products/WGV414.htm).

The source code does not build on Ubuntu, but does build on CentOS? 5, and looks like it builds the "cybertan_rom_bin" image (which contains the second rootfs listed below). It also builds the u-boot binary, including the secret console-locking code. What seems to be missing is means to build the "cybertan_half_bin" image, and the tool to turn those images into a flashable binary (with the "WRP400 FiRmWaRe?" header).

The u-boot configuration in the source code is "cywgv414dls".

BootLog?

view · edit · print · history · Last edited by krim.
Based on work by krim and rwhitby.
Originally by rwhitby.
Page last modified on September 03, 2010, at 12:21 AM