<div dir="ltr"><div>FYI, to flash a Picostation from AirOS to UniFI, you had to first flash a transitional image at <a href="http://www.ubnt.com/downloads/unifi/2.3.9/airos2unifi.bin">http://www.ubnt.com/downloads/unifi/2.3.9/airos2unifi.bin</a>, Then you add the Picostation to the UniFI dashboard, which may trigger a 2nd flashing.<br><br></div>It is possible that the transitional image mucks around with the partition table.<br><div><a target="_blank" href="http://www.ubnt.com/downloads/unifi/2.3.9/airos2unifi.bin" rel="nofollow"></a></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 20, 2016 at 3:16 PM, Josh King <span dir="ltr"><<a href="mailto:jking@chambana.net" target="_blank">jking@chambana.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Nicolas,<br>
<br>
Okay, so I've been able to flash directly to Commotion, to AirOS, and<br>
back on both of the Picostations I'm working with, both through the web<br>
interface and TFTP on multiple versions of AirOS. I'm wondering if<br>
maybe the process of flashing it to the UniFi firmware may have messed<br>
with its partition table. Can you try flashing one of your picostations<br>
back to AirOS using TFTP, and then flash it to Commotion v1.1 using<br>
TFTP? Also, can you send me a link to the unofficial instructions you<br>
mentioned for flashing it to UniFi? Thanks!<br>
<br>
On Wed, 2016-05-18 at 09:59 +0200, Nicolas North wrote:<br>
> Hi! Ok no problem thanks so much for your quick replies!<br>
><br>
> Ok I see. I actually would be very happy to use the picostation m2hp<br>
> / bullet m2hp / rocket trifecta in the entire deployment as they are<br>
> three perfect sizes for our needs: normal houses would get a<br>
> picostation, houses or offices with roof access would get a bullet<br>
> with a 15dBi N type omni antenna, and the highest rooftops would get<br>
> a rocket with a 10dBi ubiquiti omni antenna also for future expansion<br>
> outside the area. This was the initial plan and I think would work<br>
> very well. The two TP-Link devices on the commotion website are for<br>
> indoors only and still cost very much here in Italy at least.<br>
><br>
> If however it’s true that cw firmware can be compiled for any device<br>
> supported by owrt [I was able to compile pure owrt in the past but I<br>
> got stuck when trying to compile cw as I couldn’t get the<br>
> configuration menu to show] and if you have any suggestion for<br>
> outdoor devices I could use I’ll jump on that ship right now without<br>
> further ado. I was looking into ubiquiti devices because of the great<br>
> experience I’ve been having with them [on their first party firmware<br>
> at least ;] but really anything will do. How do others do it<br>
> nowadays? I basically need any device that works and I can attach a<br>
> larger than normal antenna [N type, Yagi, anything]. Ideally there<br>
> should be a few possible antenna sizes for different locations but<br>
> then again I’m just starting out here but I think this is a fairly<br>
> common setup and if anyone has a few minutes to chip in with their<br>
> experience and / or to provide any suggestion that would be immensely<br>
> appreciated.<br>
><br>
> Thanks again so much everyone and Josh for looking into this! <br>
><br>
><br>
> Nicolas<br>
><br>
><br>
><br>
> From: Josh King <<a href="mailto:jking@chambana.net">jking@chambana.net</a>><br>
> Reply: Josh King <<a href="mailto:jking@chambana.net">jking@chambana.net</a>><br>
> Date: 17 May 2016 at 23:35:42<br>
<span class="im HOEnZb">> To: Nicolas North <<a href="mailto:star@nikksno.io">star@nikksno.io</a>>, commotion-discuss <commotion-dis<br>
> <a href="mailto:cuss@lists.chambana.net">cuss@lists.chambana.net</a>><br>
</span><div class="HOEnZb"><div class="h5">> Subject: Re: [Commotion-discuss] CW Firmware on a Ubiquiti<br>
> Picostation M2HP <br>
><br>
> > Hey Nicolas, <br>
> ><br>
> > I wasn't able to get the picostations until pretty late in the day,<br>
> > so <br>
> > I don't know if I'll have information for you tonight. If not, I'll<br>
> > do <br>
> > my best to get you some feedback as soon as I can tomorrow. <br>
> ><br>
> > About the Unifi APs, I don't think we support any of their AC<br>
> > hardware <br>
> > yet due to driver issues. <br>
> ><br>
> > On Tue, 2016-05-17 at 14:45 +0200, Nicolas North wrote: <br>
> > > Hi! <br>
> > > <br>
> > > That would be fantastic thank you so much! <br>
> > > <br>
> > > I can try anything you may suggest tonight. <br>
> > > <br>
> > > Thank you very much again in advance! <br>
> > > <br>
> > > <br>
> > > Nicolas <br>
> > > <br>
> > > <br>
> > > <br>
> > > From: J. Heretic <<a href="mailto:jking@chambana.net">jking@chambana.net</a>> <br>
> > > Reply: J. Heretic <<a href="mailto:jking@chambana.net">jking@chambana.net</a>> <br>
> > > Date: 17 May 2016 at 14:41:58 <br>
> > > To: Nicolas North <<a href="mailto:star@nikksno.io">star@nikksno.io</a>>, commotion-discuss<br>
> > <commotion-dis <br>
> > > <a href="mailto:cuss@lists.chambana.net">cuss@lists.chambana.net</a>> <br>
> > > CC: Ben West <<a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a>> <br>
> > > Subject: Re: [Commotion-discuss] CW Firmware on a Ubiquiti <br>
> > > Picostation M2HP <br>
> > > <br>
> > > > Hi Nicolas, <br>
> > > > <br>
> > > > I'm going to grab some picostations from the office today and<br>
> > try <br>
> > > > again <br>
> > > > to reproduce the problem you're having. <br>
> > > > <br>
> > > > On Tue, 2016-05-17 at 11:13 +0200, Nicolas North wrote: <br>
> > > > > Hi there everyone! <br>
> > > > > I'm very sorry for the really late reply but I've been a<br>
> > little <br>
> > > > held <br>
> > > > > back lately by all of the difficulties I've encountered<br>
> > while <br>
> > > > > starting this project that I really believe in, so I've been <br>
> > > > working <br>
> > > > > on it on my own for a few weeks to see what I could figure<br>
> > out. <br>
> > > > Key <br>
> > > > > updates are as follows: <br>
> > > > > I've found a way to "unlock" / "unbrick" ubiquiti<br>
> > picostations <br>
> > > > and <br>
> > > > > bullets and have been able to do so several times. For now<br>
> > my <br>
> > > > > experience has always been: unbox them, try installing<br>
> > commotion <br>
> > > > > firmware immediately from the web interface as per the <br>
> > > > instructions, <br>
> > > > > device installs and reboots, seemingly gets stuck in limbo<br>
> > [no <br>
> > > > > bootloop but not showing up in any network scan with or<br>
> > without <br>
> > > > dhcp <br>
> > > > > under any subnet], enter tftp, try reinstalling AirOS,<br>
> > device <br>
> > > > reboots <br>
> > > > > into endless bootloop, enter tftp again to flash cw firmware<br>
> > only <br>
> > > > to <br>
> > > > > get 512 firmware check error. The solution for me has <br>
> > > > consistently <br>
> > > > > been to install unifi on the devices as per ubiquiti<br>
> > instructions <br>
> > > > [a <br>
> > > > > procedure that is unsupported but explained on their<br>
> > website] <br>
> > > > via <br>
> > > > > tftp [I can provide the link if anyone is interested]<br>
> > [always <br>
> > > > got <br>
> > > > > them working on unifi like this btw], then enter tftp again<br>
> > and <br>
> > > > > install AirOS 5.1.2, and only then was I always able to<br>
> > actually <br>
> > > > > install cw firmware via AirOS web interface and working as <br>
> > > > instructed <br>
> > > > > in the cw howtos. The devices reboot perfectly and fully <br>
> > > > functionally <br>
> > > > > in cw and except for my first attempt [see last mail] where<br>
> > I <br>
> > > > had <br>
> > > > > problems with LuCI, I was always able to do the initial<br>
> > setup <br>
> > > > > perfectly. The major problem here which had been haunting my <br>
> > > > dreams <br>
> > > > > [irony, but true] for the last few weeks is that upon the<br>
> > first <br>
> > > > > reboot the devices completely loose their mesh and WiFi<br>
> > configs <br>
> > > > and <br>
> > > > > they seem to be missing key packages suck as olsr and such.<br>
> > A <br>
> > > > > possible explanation for this is that after the cw install<br>
> > only <br>
> > > > 2% of <br>
> > > > > space is left on the device's NAND for some reason I have yet<br>
> > to <br>
> > > > > understand. A quick df -h via ssh reveals the partitions all <br>
> > > > together <br>
> > > > > make up less than 50MB although this also appears to be the<br>
> > case <br>
> > > > with <br>
> > > > > stock AirOS and Unifi at least on my devices. <br>
> > > > > I've been searching everywhere for a solution to this<br>
> > problem <br>
> > > > and <br>
> > > > > I've found that the standard openwrt image is 50MB but being <br>
> > > > these <br>
> > > > > always bin files I've never been able to expand their<br>
> > partitions <br>
> > > > > before flashing them. <br>
> > > > > I've also tried installing stock owrt following metamesh's <br>
> > > > directives <br>
> > > > > from a link in the last email but although I could install<br>
> > it <br>
> > > > > [through the super complex procedure listed above] on both <br>
> > > > devices I <br>
> > > > > still got 98% of storage space used and couldn't get all <br>
> > > > packages <br>
> > > > > installed as per their tutorial! <br>
> > > > > I really don't understand how this is happening given that <br>
> > > > except <br>
> > > > > from the possible firmware locks introduced recently I'm <br>
> > > > basically <br>
> > > > > getting extremely common deviceS in the mesh world and<br>
> > installing <br>
> > > > cw <br>
> > > > > or even stock openwrt onto them. I'd really like to know<br>
> > what <br>
> > > > I'm <br>
> > > > > doing wrong. I've seen your new thread about this ubiquiti<br>
> > issue <br>
> > > > but <br>
> > > > > I don't understand how I could even try using other routers<br>
> > on <br>
> > > > the cw <br>
> > > > > download page if they're not weather proof. Apart from the<br>
> > fact <br>
> > > > of <br>
> > > > > course that I risk getting even more devices that will end<br>
> > up <br>
> > > > bricked <br>
> > > > > or not fully functional after all of the money I've already <br>
> > > > spent. <br>
> > > > > Should I try with unifi AC AP pros? Are they supported by<br>
> > cw? <br>
> > > > > I really want and need to start this project. It'll be a<br>
> > very <br>
> > > > > profound achievement I think and there are already tens of <br>
> > > > people <br>
> > > > > with more every day asking me when it'll be online and I<br>
> > cannot <br>
> > > > > accept that it's not working or even worse that I'm so close<br>
> > such <br>
> > > > as <br>
> > > > > having it only work until a reboot or a power loss related<br>
> > hard <br>
> > > > > reboot. <br>
> > > > > I will happily reward any dev or specialist at cw or in<br>
> > this <br>
> > > > > community with a 100€ bounty / donation if this can help [all<br>
> > I <br>
> > > > can <br>
> > > > > afford right now] that will be able to help me get online by<br>
> > any <br>
> > > > mean <br>
> > > > > in a timely fashion and in a cost effective way, with more<br>
> > small <br>
> > > > > donations to the project every month in the future from the<br>
> > tip <br>
> > > > jar <br>
> > > > > we'll establish here on location. <br>
> > > > > This has to happen now :) <br>
> > > > > Thanks in advance and truly sincere kudos for the amazing<br>
> > work <br>
> > > > on <br>
> > > > > this fantastic project. I really appreciate all of your help<br>
> > on <br>
> > > > this <br>
> > > > > as well of course and I definitely look forward to working<br>
> > with <br>
> > > > you. <br>
> > > > > Thanks again! <br>
> > > > > <br>
> > > > > Nicolas <br>
> > > _______________________________________________ <br>
> > > Commotion-discuss mailing list <br>
> > > <a href="mailto:Commotion-discuss@lists.chambana.net">Commotion-discuss@lists.chambana.net</a> <br>
> > > <a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" rel="noreferrer" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a> <br>
> > -- <br>
> > Josh King <br>
> > PGP Fingerprint: 8269 ED6F EA3B 7D78 F074 1E99 2FDA 4DA1 69AE 4999<br>
--<br>
Josh King<br>
PGP Fingerprint: 8269 ED6F EA3B 7D78 F074 1E99 2FDA 4DA1 69AE 4999</div></div><br>_______________________________________________<br>
Commotion-discuss mailing list<br>
<a href="mailto:Commotion-discuss@lists.chambana.net">Commotion-discuss@lists.chambana.net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" rel="noreferrer" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Ben West<div><a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br><a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a><br>314-246-9434<br></div></div>
</div>