Fix compatibility with Commotion Wireless.

[virtadpt]

R1 of the Commotion Wireless firmware made some incompatible changes to their configuration that we need to suss out and take into account in Byzantium.

• All Commotion instances now pick IP addresses from RFC-6958 (Carrier Grade NAT address block) - 100.64/10
• Each Commotion instance's client network comes from RFC-1918: 10/8
• It no longer uses a default set of wireless settings. When Commotion nodes are first started up, they have to be configured.
• BSSIDs for the mesh network are no longer hardcoded, they're deterministically generated. It's now a hash of the ESSID and wireless channel the node is configured for.

Source: https://commotionwireless.net/blog/commotion-r1-breaking-changes

[virtadpt]

I think we have a couple of possible options here.

• We can break with Commotion compatibility, at least for a little while.
• We can use Scapy (http://www.secdev.org/projects/scapy/) to monitor the local wireless environment for a short time to determine if there are any Commotion nodes nearby, and if there are configure Byzantium for compatibility. \ We'll need to characterize Grumpy Cat's network activity to figure out what to look for first.
• We can work out a compatibility mode with the Commotion team, because we're working with one another to build mesh networks first and foremost and not competing wit one another. Beer will probably be required.
• We add a user-side configuration tool that reconfigures a running Byzantium instance with some values entered by the user to set things up appropriately.
• We change Byzantium to do the same thing. I'm not so sure I like this option.

[sensorware]

any progress on this? I have seen ByzPi node show up in the commotion, but rebuilding the setup on wheezy. The Apache2 changes in Jesse are causing issues.