[Commotion-dev] Disabling adhoc encryption on current nightly builds of Commotion-OpenWRT DR1?

[Dan Staples]

There is currently a bug in the quickstart, where if you click on
"Continue with an insecure network", it actually still turns on
encryption for the adhoc interface. To turn it off manually, set
wpa=false in the /etc/commotion/profiles.d/quickstartMesh file, then
restart commotion and restart networking. After going through the
quickstart, the adhoc/mesh interface uses the quickstartMesh commotion
profile, which you can confirm in /etc/config/network.

If doing the above doesn't fix it, or it complains about your encryption
settings, remove the wpa and key options for the mesh interface in
/etc/config/wireless, and then restart networking. But this shouldn't be
necessary, since /etc/config/wireless is largely generated by commotiond
(at least the interface-specific sections).

On Thu 04 Apr 2013 10:09:26 AM EDT, seamus tuohy wrote:
>
> On 04/03/2013 02:49 PM, Ben West wrote:
>>
>> Hi All,
>>
>> I'm having good success exercising recent nightly builds of
>> Commotion-OpenWRT DR1 on a Nanostation Loco M2. I understand this is
>> a new release, and that it has an active issue queue (which I'm going
>> to post to soon). I'm putting this question on the listserv right
>> now, in case this happens to touch on issues already filed, and also
>> for reference of other list members.
>>
>> The Quickstart tool on the new DR1 release is really neat! At
>> present, I'm trying out the tool by flashing a node and then
>> connecting to http://192.168.1.20/ on the node's eth0 port.
>
> That is great to hear!
>
>>
>>
>> However, it looks like QS enables psk2 encryption on the node's adhoc
>> interface, and I have yet to figure out how to disable it. That is,
>> the luci UI lists "Encryption: none" for the adhoc, and re-applying /
>> committing that setting via luci just seems to hang. Likewise,
>> manually editing /etc/config/wireless at the command line to disable
>> encryption is ineffective, because I think commotiond just
>> regenerates that file when I issue "wifi restart", clobbering my edits.
>
>
> If you go through the manual configuration and click the "Continue
> with a insecure network" button on the Keyfiles and Security page QS
> will remove the servald and wpakey values from the
> /etc/commotion/profiles.d/quickstartMesh profile which is used to
> generate the profiles at the end of QS. Otherwise, it will keep the
> default values, which are pulled from the
> /etc/commotion/profiles.d/defaultMesh config file. When JK gets in the
> office I will ask how commotiond intereperets the profile. From what
> you are saying I am assuming that a blank line results in the default
> behaviour of true. I will post again when I get the correct value to
> disable encryption for the config file.
>>
>>
>> Is there a trick to getting commotiond to not encrypt the adhoc
>> interface? I need the mesh unencrypted, so that the Nanostation can
>> mesh with my Ubuntu/commotion-mesh-applet and Android/Mesh Tether
>> devices.
>>
>> (Also, it seems that I can hack commotiond to not deploy encryption
>> by editing /lib/netifd/proto/commotion.sh, but I'm asking here on the
>> list in case there is a more elegant way.)
>>
>> Thanks.
>>
>>
>> -- 
>> Ben West
>> http://gowasabi.net
>> ben at gowasabi.net <mailto:ben at gowasabi.net>
>> 314-246-9434 <tel:314-246-9434>
>>
>>
>>
>> _______________________________________________
>> Commotion-dev mailing list
>> Commotion-dev at lists.chambana.net
>> https://lists.chambana.net/mailman/listinfo/commotion-dev
>
>
>
>
> _______________________________________________
> Commotion-dev mailing list
> Commotion-dev at lists.chambana.net
> https://lists.chambana.net/mailman/listinfo/commotion-dev
> -- 
> Dan Staples
>
> Open Technology Institute
> https://commotionwireless.net