WAP54G dead after FW update

Dear reader,

I shot myself in the foot...
I updated the firmware on my Linksys WAP54G from 1.08 to 2.06 and this ended
up in a dead AP.
The antenna works, SSID is broadcasted.
Connecting via a cable gives nothing, no ping, no web-configuration page,
Linksys setup can't find it...
Anyone have a clue on how to reflash this thing... ?

reg, Henno

Most likely you would want to get a warrenty fix on that. Once you fried
something you fried it. Just tell them that it suddenly went dead, as bad
firmware upgrades are NOT covered under warrenty.

You could also try holding the reset button for a couple of minutes and see
if it comes up. You could also try unplugging it for a few minutes. Though I
doubt that any of that would help.
"Henno Keers" <(E-Mail Removed)> wrote in message
news:c055jg$12fj3k$(E-Mail Removed)...
> Dear reader,
>
> I shot myself in the foot...
> I updated the firmware on my Linksys WAP54G from 1.08 to 2.06 and this
ended
> up in a dead AP.
> The antenna works, SSID is broadcasted.
> Connecting via a cable gives nothing, no ping, no web-configuration page,
> Linksys setup can't find it...
> Anyone have a clue on how to reflash this thing... ?
>
> reg, Henno
>
>

I did that firmware upgrade as well with no problems. Are you sure it is
actually dead? Perhaps the IP address of the access point is changed which
means you are going to have trouble connecting to it until you find out what
it is. Setup will not be able to find the access point if the IP address is
not the default one out of the box.

Are yo using a DHCP server and was the access point configured to get an IP
address or was it static? If it was DHCP, you may be able to guess at the
new IP address based upon the pool of addresses your DHCP works from.

Jeff


"Henno Keers" <(E-Mail Removed)> wrote in message
news:c055jg$12fj3k$(E-Mail Removed)...
> Dear reader,
>
> I shot myself in the foot...
> I updated the firmware on my Linksys WAP54G from 1.08 to 2.06 and this
ended
> up in a dead AP.
> The antenna works, SSID is broadcasted.
> Connecting via a cable gives nothing, no ping, no web-configuration page,
> Linksys setup can't find it...
> Anyone have a clue on how to reflash this thing... ?
>
> reg, Henno
>
>

> > Dear reader,
> >
> > I shot myself in the foot...
> > I updated the firmware on my Linksys WAP54G from 1.08 to 2.06 and this
> ended
> > up in a dead AP.
> > The antenna works, SSID is broadcasted.
> > Connecting via a cable gives nothing, no ping, no web-configuration page,
> > Linksys setup can't find it...
> > Anyone have a clue on how to reflash this thing... ?
> >
> > reg, Henno
> >
> >

I had the exact same problem with the exception that the setup
software CAN find the WAP54G.
It displays the new firmware version, but that is ALL that makes
sense.
The NEW default IP it has is 1.192.168.1 (even after a holding the
reset button in for 30seconds as recommended by Linksys support).
The MAC address shows as 00-11-22-33-44-55.

Now even directly wired to the AP I cannot access the WEB interface
via the SUPPOSED to be default IP, nor the NEW 1.192.168.1. However,
connected to my home network I am still able to get a DHCP address to
my wireless devices (DHCP is supplied by my router not the AP) and I
can indeed surf the net.

Again, I am unable to PING or contact the web interface since I did
the firmware upgrade to v2.06. This has happened to me on 2 WAP54Gs,
one I would think a fluke, but 2? I don't think so. I am getting ready
to return both of these AP for RMA, hopefully they will send me WAP54G
with the old firmware.

BTW, I also noticed there is now a WAP54G v2.0 out there. Anyone know
what the differences are? There is a WAP54G v1.0, v1.1, and now a
v2.0!

Dirk , je schreef:
>>> Dear reader,
>>>
>>> I shot myself in the foot...
>>> I updated the firmware on my Linksys WAP54G from 1.08 to 2.06 and
>>> this
>> ended
>>> up in a dead AP.
>>> The antenna works, SSID is broadcasted.
>>> Connecting via a cable gives nothing, no ping, no web-configuration
>>> page, Linksys setup can't find it...
>>> Anyone have a clue on how to reflash this thing... ?
>>>
>>> reg, Henno
>>>
>>>

Hi Dirk,

>
> I had the exact same problem with the exception that the setup
> software CAN find the WAP54G.
> It displays the new firmware version, but that is ALL that makes
> sense.
> The NEW default IP it has is 1.192.168.1 (even after a holding the
> reset button in for 30seconds as recommended by Linksys support).
> The MAC address shows as 00-11-22-33-44-55.
>

The EXACT thing happend to me when I hooked up my laptop to the interface of
the WAP, same weird IP and MAC.

> Now even directly wired to the AP I cannot access the WEB interface
> via the SUPPOSED to be default IP, nor the NEW 1.192.168.1. However,
> connected to my home network I am still able to get a DHCP address to
> my wireless devices (DHCP is supplied by my router not the AP) and I
> can indeed surf the net.
>

I can't get an IP from my router anymore...

> Again, I am unable to PING or contact the web interface since I did
> the firmware upgrade to v2.06. This has happened to me on 2 WAP54Gs,
> one I would think a fluke, but 2? I don't think so. I am getting ready
> to return both of these AP for RMA, hopefully they will send me WAP54G
> with the old firmware.
>

Well, that makes 3 WAP's.

> BTW, I also noticed there is now a WAP54G v2.0 out there. Anyone know
> what the differences are? There is a WAP54G v1.0, v1.1, and now a
> v2.0!

I only noticed that the same FW is available for ALL types...

reg, Henno

Dirk , je schreef:
<big snip>

I just spoke to a support person from Linksys via their live-chat site and
she told me to get it replaced under warranty.

reg, Henno.

On 8 Feb 2004 09:58:33 -0800, Dirk spoketh
>
>Again, I am unable to PING or contact the web interface since I did
>the firmware upgrade to v2.06. This has happened to me on 2 WAP54Gs,
>one I would think a fluke, but 2? I don't think so. I am getting ready
>to return both of these AP for RMA, hopefully they will send me WAP54G
>with the old firmware.
>
>BTW, I also noticed there is now a WAP54G v2.0 out there. Anyone know
>what the differences are? There is a WAP54G v1.0, v1.1, and now a
>v2.0!

I had absolutely no issues with upgrading my WAP54G to the 2.06
firmware. But I went from 1.06 to 2.06 simply because I found 1.08 to be
very bad (WAP would crash upon restart when changing settings). 2.06
have fixed this...

I believe the difference between v1 and v2 of the WAP is merely
cosmetic. There's a different LED layout...

Lars M. Hansen
www.hansenonline.net
Remove "bad" from my e-mail address to contact me.

Lars M. Hansen , je schreef:
> On 8 Feb 2004 09:58:33 -0800, Dirk spoketh
>>
>> Again, I am unable to PING or contact the web interface since I did
>> the firmware upgrade to v2.06. This has happened to me on 2 WAP54Gs,
>> one I would think a fluke, but 2? I don't think so. I am getting
>> ready to return both of these AP for RMA, hopefully they will send
>> me WAP54G with the old firmware.
>>
>> BTW, I also noticed there is now a WAP54G v2.0 out there. Anyone know
>> what the differences are? There is a WAP54G v1.0, v1.1, and now a
>> v2.0!
>
> I had absolutely no issues with upgrading my WAP54G to the 2.06
> firmware. But I went from 1.06 to 2.06 simply because I found 1.08 to
> be very bad (WAP would crash upon restart when changing settings).
> 2.06 have fixed this...
>
> I believe the difference between v1 and v2 of the WAP is merely
> cosmetic. There's a different LED layout...

Howcome then that it flunked my WAP while the web-interface told me that the
update went ok ?

reg, Henno

Henno Keers <(E-Mail Removed)> wrote:
> Lars M. Hansen , je schreef:
>> On 8 Feb 2004 09:58:33 -0800, Dirk spoketh
>>>
>>> Again, I am unable to PING or contact the web interface since I did
>>> the firmware upgrade to v2.06. This has happened to me on 2 WAP54Gs,
<snip>
> Howcome then that it flunked my WAP while the web-interface told me that the
> update went ok ?

Did you turn it off immediately afterwards?

If the difference between ver 1.1 & 2.0 is only cosmetic, why can't I apply
the Satori_v2_2.00.8.7sv-pre1.bin firmware?


"Ian Stirling" <(E-Mail Removed)> wrote in message
news:rNyVb.1437$(E-Mail Removed)...
> Henno Keers <(E-Mail Removed)> wrote:
> > Lars M. Hansen , je schreef:
> >> On 8 Feb 2004 09:58:33 -0800, Dirk spoketh
> >>>
> >>> Again, I am unable to PING or contact the web interface since I did
> >>> the firmware upgrade to v2.06. This has happened to me on 2 WAP54Gs,
> <snip>
> > Howcome then that it flunked my WAP while the web-interface told me that
the
> > update went ok ?
>
> Did you turn it off immediately afterwards?