Re: [lime-users] Chef-cooked long-distance router

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 17/11/16 11:35, Ilario wrote: 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