27 Nov
2016
27 Nov
'16
11:06 p.m.
On 20/11/16 21:17, Amuza wrote:
On 17/11/16 11:35, Ilario wrote:
Hi again, I'm replying to myself : (
I had the opportunity to talk to Ilario who helped me a lot in the
troubleshooting -thank you Ilario!!- but unfortunately I still cannot
make it work.
I thought the cause of the problem was that I was trying to install the
wrong firmware (loco-m-xw), I thought everything would be fine when
installing the apparently correct one (rocket-m-xw). I was wrong.
Ilario taught me how to upload the firmware through TFTP. I could
communicate again with my router but, when doing the TFTP transfer, I
always had a 'Firmware check failed' message, despite I properly checked
file integrity (MD5) of the firmwares I tried to install: OpenWRT
rocket-m-xw, the LiMe rocket-m-xw and AirOS xw v.5.5.6.
Didn't understand what exactly happened but somehow I managed to have
the AirOS xw v5.5.6 back to life after a proper reset. Apparently the
AirOS system was always there, healthy, and I did not notice.
So I happily started the upload of the correct firmware (rocket-m-xw)
through the GUI hoping this time will be fine because now I was choosing
the correct firmware. But then I had the same problem as when I started:
I uploaded the firmware, clicked on Update, everything looked fine but
the new firmware (OpenWRT or LiMe) was not being installed, the AirOS
firmware always stayed there.
So I decided to apply the command line workaround I tried before:
- Upload the image through GUI
- ssh ubnt(a)192.168.1.20
- fwupdate.real -m fwupdate.bin -d
Everything looked cool during the process but, again, when the update
apparently ended, I was exactly at the same point of my previous email:
The router again seemed bricked. Fortunately now I knew that patience
and a reset would take me again to AirOS v5.5.6. That's where I am now,
again.
I do not know how to flash OpenWRT or LiMe on this PBE-M5-400 router.
Any suggestion? If I don't receive any answer I will soon try to get rid
of this thingy.
Does anyone know any working LiMe router more unidirectional than the
NanoStation M5? I need something more unidirectional.
It does not have to be a new model. Actually, I prefer if it is an old
one, so that I can get a second-hand one.
Cheers
2016-11-16 23:31 GMT+01:00 Amuza
<amuza(a)riseup.net>et>:
> Hi again. I got the suggested PowerBeam, the PBE-M5-400. I have
> downgraded it to version 5.5. I am ready to flash it with Lime
> bin for bullet. But I have just seen that the firmware of my
> PBE-M5-400 is XW, as in some Nanostations. However I do not see
> an XW Lime version for the bullet on the cooked images from the
> Chef. What should I do? Shall I proceed anyway?
You're right, the correct image is NOT
bullet but loco-xw which is
equivalent to bullet image but for XW hardware (it would have been
easier if they called it bullet-xw). Let us know :D Ilario
Thank you.
I'm in trouble now.
I wasn't able to flash the PBE-M5-400 through the GUI.
When putting the 192.168.1.20 in the browser, I went to Firmware
Update, select my loco-m-xw factory bin and pressed "Upload".
Then I could read the statement "Uploaded Firmware Version:
XW.v6.0.0-OpenWrt-r49403".
I clicked on the "Update" button and saw the "Firmware is being
updated" window.
After some seconds that window closed and then I could normally log in
again to the airOS at 192.168.1.20 : (
Flashing did not work.
Manually rebooting the router did not help, LiMe did not show up either.
By the way, I realized that according to the GUI I had a NanoBeam M5
400 instead of a PowerBeam M5 400. I contacted Ubiquity, they said
version 5.5 was NanoBeam, and then they rebranded it to PowerBeam with
version 5.6.
(I downgraded the system from 5.6 to 5.5 some emails ago)
As I could not flash it through the GUI, I went to openwrt.org and
found [1] that I could flash it through ssh with the following command:
fwupdate.real -m firmware_image_file.bin -d
I realized that every time I was trying to upload firmware with the
GUI, a file called "fwupdate.bin" appeared at /tmp with the same size.
So I uploaded my loco-m-xw factory LiMe bin file through the GUI and
then, through ssh, I went to /tmp and did the following:
fwupdate.real -m fwupdate.bin -d
Everything looked cool. The leds on the router did the Knight Rider
show. But then I could do nothing else. Now I cannot connect to the
PBE-M5-400 anymore in anyway I know.
Its only living signals now are the power led and the LAN led, the LAN
led flashes when it's got something plugged in, but that's all :/
Please help!
I attach a file with the outputs of flashing it through ssh. Just in
case they are useful.
Thank you.
[1] https://wiki.openwrt.org/toh/ubiquiti/nanobeam