bugtraq - RE: Linksys WRT54G - Advice for european users

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ECOWS01MTwG0IZX1z6V00031f05@smtp-out1.blueyonder.co.uk>
Date: Tue, 8 Jun 2004 08:53:22 +0100
From: "micm" <micm@...h.org.uk>
To: <bugtraq@...urityfocus.com>
Subject: RE: Linksys WRT54G - Advice for european users

 > -----Original Message-----
> From: bugtraq-return-14636-micm=toth.org.uk@...urityfocus.com 
> [mailto:bugtraq-return-14636-micm=toth.org.uk@...urityfocus.co
> m] On Behalf Of Connor, Ethan M. W
> Sent: Monday, June 07, 2004 5:56 PM
> To: 'Christer Palm'; bugtraq@...urityfocus.com
> Subject: RE: Linksys WRT54G - Advice for european users
> 
> Another bit of warning about linksys and their inability to 
> get the firmware
> release vs. hardware version worked out correctly.  If you install the
> latest WAP54G firmware update for the v2 hardware on v1 or 
> v1.1 hardware
> (which the readme says is supported)...  Expect the ethernet 
> port to disable
> itself (due to the order in which the interfaces are 
> initialized on the
> device) after you power cycle it...

The readme for the european version of the firmware has this to say:

=======
Note:  If you try and upgrade an older unit to firmware 2.07 without
upgrading 
the firmware to 1.09.1 prior to upgrade, you may damage the Access
Point.
=======

And also has a pdf containing the instructions and links to the relevant
firmware downloads.
http://www.linksys.com/download/vertxt/WAP54GupgradeprocedureV2.doc

As someone who suffered from the dead ethernet port symptom, I can
confirm that the upgrade via the 1.09 version fixed the issue.  Note
also that it's mentioned in various places that the 1.09 firmware is not
a functional firmware - however it in fact works identically to 1.08
(USA version).  Make sure you power cycle the router at least once after
upgrading to 1.09 rather that just letting it reboot by itself
post-update.

Analysis elsewhere
(http://www.sveasoft.com/modules/phpBB2/viewforum.php?f=10) suggests
that the 1.09 firmware updates the pmon code within the router.

Mike.