Bricked wAP following 6.32.4 upgrade

RouterOS General
1

Hi

I purchased a few wAP (RBwAP2nDr2) and have begun deploying a couple.

I configured them and then upgraded them to 6.32.4 (System & advanced tools & Wireless-cm2)

Now they are bricked: un-rea-cha-ble

The LEDs come on, and then a few seconds later, switch off, and then back on, etc…

I tried a reset but this has no effect whatsoever

Tried the same thing with two more wAPs, same result, except that now I have four bricked wAPs, (ed. well six now !)

I tried to reinstall the original ROS (6.30.4) via NetInstall - but without success so far

So basically, the gist here is don’t upgrade (or downgrade) a wAP if you know what’s good for you

Any ideas on how to fix this mess ?

thanks
yann

2

Netinstall using 6.34.4

3

OK, I finally managed to reinstate 6.30.4 using Netinstall

Apparently Netinstall doesn’t behave properly on Win7-64 or WinX-64

I booted up with Hiren 15.2 and was able to successfully install the desired ROS
and now the wAP is back in action

Sorry for the confusion my post may have caused

4

I do not have XP at 64 bit, but on windows 7 sp1 64 bit, windows 8.1 64 bit and windows 10 netinstall work without any problem only if the only active interface are the interface used for programming the device.

5

Thanks RExtended

Hiren contains an XP Pro 2002 (32bit)

I did try to upgrade the wAP from 6.30.4 to 6.32.4 through the file copy approach and it still didn’t succeed

Still, this isn’t very practical if Netinstall is the only available solution to upgrade ROS on a wAP

6

It is not… I have a wAP and I upgraded it using both the drag n drop .npk and System > Packages Upgrade without problems.

There was a hiccup on 6.35rc versions that may cause this, but doesn’t seem to be the case here.

Good practice to avoid this:

  • Keep firmware updated
  • Reset it to no defaults after major upgrades (reload the configuration afterwards)
7

Thanks Pukkita

Even Martin said that this isn’t an issue.

As I said earlier all I did was upgrade these wAPs from Winbox 3.4 and the
drag & drop method with the three 6.32.4 modules and obtained the same
result with each one.

I even tried this again once I had recovered the devices thanks to Netinstall
and got the same result

So either I’m really unlucky i.e. bad batch, or else I don’t know :]]

Well the important thing, as I told Martin, is that I found a work around
and that everything is hunky dory again.

I guess I won’t be updating them any time soon, that’s for sure.

Thanks for your inputs

cheers

8

Well the wAPs weren’t operating properly on the client’s network (CAPsMAN v2)
The connection would constantly come and go

So I tried to upgrade them to 6.35: this was successful, what do you know !
Not sure what the lesson is here…