Hi Hans,<div><br></div><div>I was having lots of problems getting Commotion to work under OpenWRT trunk r32002 and newer, due to recent changes made to kernel and I think to netifd.<br><a href="https://dev.openwrt.org/changeset/31640/">https://dev.openwrt.org/changeset/31640/</a></div>
<div><a href="https://dev.openwrt.org/changeset/32049/">https://dev.openwrt.org/changeset/32049/</a></div><div><br></div><div>This is what prompted my question to this list about how the meshconfig tool works (the tool that handles node auto-config), since it apparently stopped working for newer versions of trunk.</div>
<div><br>I do have compiled ar71xx and atheros images from when I reverted Commotion back to trunk r31639, and I though I had published them to <a href="http://info.gowasabi.net">info.gowasabi.net</a>, but I may have misplaced them.</div>
<div><br></div><div>I will look and respond later today.<br><br><div class="gmail_quote">On Thu, Jun 21, 2012 at 6:01 PM, Hans-Christoph Steiner <span dir="ltr"><<a href="mailto:hans@guardianproject.info" target="_blank">hans@guardianproject.info</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
We tried this image and were able to get something working. But we had to manually setup the wifi settings, tweak the olsrd.conf, and manually start olsrd. Did we miss something or is this image not yet setup to do commotion by default?<br>
<br>
.hc<br>
<div><div class="h5"><br>
On May 22, 2012, at 12:11 PM, Ben West wrote:<br>
<br>
> Hi All,<br>
><br>
> I updated the compiled images for ath5k and ar71xx I made after some<br>
> further testing yesterday. These images are compiled from the<br>
> commotion-openwrt repo as it existed on 5/18/12.<br>
> <a href="http://info.gowasabi.net/commotion-openwrt/openwrt/" target="_blank">http://info.gowasabi.net/commotion-openwrt/openwrt/</a><br>
><br>
> Recently flashed nodes seemed to complain about missing OLSR plugins,<br>
> and I wasn't sure if they were required for operation.<br>
><br>
> (I had thought I filed an issue on Redmine @<br>
> <a href="https://code.commotionwireless.net/projects/commotion-openwrt/issues" target="_blank">https://code.commotionwireless.net/projects/commotion-openwrt/issues</a><br>
> asking if commotionbase missing some declared dependencies, but it<br>
> looks it may have gone missing.)<br>
><br>
> On Mon, May 21, 2012 at 2:40 AM, Ben West <<a href="mailto:me@benwest.name">me@benwest.name</a>> wrote:<br>
>> Hi All,<br>
>><br>
>> In aftermath from Friday's hackathon, here are recent compiled<br>
>> Commotion-opewrt images for ath5k and ath9k targets, including the<br>
>> .config files I used and images for UBNT M and Buffalo devices:<br>
>> <a href="http://info.gowasabi.net/commotion-openwrt/openwrt/" target="_blank">http://info.gowasabi.net/commotion-openwrt/openwrt/</a><br>
>><br>
>> I have so far successfully flashed these devices, and afterwards<br>
>> telnetted into 192.168.1.20 to configure them:<br>
>> - a really crusty old FON2100 (openwrt-atheros-root.squashfs and<br>
>> openwrt-atheros-vmlinux.lzma)<br>
>> - UBNT Nanostation Loco M2<br>
>> (openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin)<br>
>> - UBNT Bullet M2 (openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin)<br>
>><br>
>> After telnetting into each device to set a root password, I rebooted<br>
>> them. All 3 nodes are now meshing w/ each other (can ping / ssh<br>
>> between them), confirming basic operation of both the ath5k ad ath9k<br>
>> drivers.<br>
>><br>
>> Do note the ath5k images DO NOT have any luci packages compiled into<br>
>> the images, but are available as separate *.ipk files at the URL<br>
>> above. I did this since the FON has only 16MB RAM, and just the bare<br>
>> image w/o the web UI leaves less than 1MB in free RAM. Newer ath5k<br>
>> devices like the Open Mesh OM1P and Engenius EOC-1650 should have at<br>
>> least 32MB RAM to handle the web UI.<br>
>><br>
>> Finally, leading from discussion on IRC, I added a support ticket<br>
>> requesting periodic (e.g. nightly or weekly) snapshot builds located<br>
>> on the <a href="http://code.commotionwireless.net" target="_blank">code.commotionwireless.net</a> server for popular targets like<br>
>> ath5k and ar71xx.<br>
>> <a href="https://code.commotionwireless.net/issues/308" target="_blank">https://code.commotionwireless.net/issues/308</a><br>
>><br>
>> --<br>
>> Ben West<br>
>> <a href="mailto:me@benwest.name">me@benwest.name</a><br>
><br>
><br>
><br>
> --<br>
> Ben West<br>
> <a href="mailto:me@benwest.name">me@benwest.name</a><br>
><br>
</div></div>> _______________________________________________<br>
> Commotion-dev mailing list<br>
> <a href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a><br>
> <a href="http://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">http://lists.chambana.net/mailman/listinfo/commotion-dev</a><br>
><br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Ben West</div><div><a href="mailto:me@benwest.name" target="_blank">me@benwest.name</a></div><br>
</div>