[Commotion-dev] SPAN Android App

[Robble, Jeff]

Err, I meant "While the probability is low that there will be IPv4 address collision in a class A subnet" …

Maybe these questions / concerns should be posted on your forum.

Jeffrey Robble
Software Systems Engineer
The MITRE Corporation (Bedford)
Office: 781.271.2790

From: <Robble>, "Robble, Jeff" <jrobble at mitre.org<mailto:jrobble at mitre.org>>
Date: Monday, October 15, 2012 1:36 PM
To: Hans of Guardian <hans at guardianproject.info<mailto:hans at guardianproject.info>>
Cc: List Commotion Development <commotion-dev at lists.chambana.net<mailto:commotion-dev at lists.chambana.net>>, "Chong, Oliver L" <ochong at mitre.org<mailto:ochong at mitre.org>>, "Durrant, Sheldon A." <sdurrant at mitre.org<mailto:sdurrant at mitre.org>>, "m0nk.omg.pwnies at gmail.com<mailto:m0nk.omg.pwnies at gmail.com>" <m0nk.omg.pwnies at gmail.com<mailto:m0nk.omg.pwnies at gmail.com>>
Subject: Re: SPAN Android App

Also, have you guys looked into Wi-Fi Direct?

Jeffrey Robble
Software Systems Engineer
The MITRE Corporation (Bedford)
Office: 781.271.2790

From: <Robble>, "Robble, Jeff" <jrobble at mitre.org<mailto:jrobble at mitre.org>>
Date: Monday, October 15, 2012 1:34 PM
To: Hans of Guardian <hans at guardianproject.info<mailto:hans at guardianproject.info>>
Cc: List Commotion Development <commotion-dev at lists.chambana.net<mailto:commotion-dev at lists.chambana.net>>, "Chong, Oliver L" <ochong at mitre.org<mailto:ochong at mitre.org>>, "Durrant, Sheldon A." <sdurrant at mitre.org<mailto:sdurrant at mitre.org>>, "m0nk.omg.pwnies at gmail.com<mailto:m0nk.omg.pwnies at gmail.com>" <m0nk.omg.pwnies at gmail.com<mailto:m0nk.omg.pwnies at gmail.com>>
Subject: Re: SPAN Android App

Hi Hans,

What Android devices does Commotion currently support? I tried it out an my Galaxy Nexus (CDMA) and Galaxy S II (SPH-D710) to no avail.

Supporting all of the various Android devices and their hardware differences is a major issue. A common framework would be great. Currently SPAN works on devices with Wireless Extensions kernel support. That way we can simply use iwconfig; however, there are some things that iwconfig can't seem to do on Android devices, like set the 802.11 channel.

It seems that Commotion is focusing on OLSR. Is there a reason you went with OLSR and not BATMAN? Serval uses BATMAN I believe. Based on what I read, the main developers behind OLSR came up with BATMAN to address circular routing, network congestion, and performance issues. Yet, OLSR-NG apparently fixed their fisheye feature and now it performs much better than before with less network congestion: http://www.olsr.org/?q=node/13

Ultimately a generic framework for plug-and-play routing protocols would be best. That way people could test and determine which ones are best. Have you guys given any thought to reactive protocols (like AODV) vs. proactive protocols (like OLSR)?

Serval does a decent job with security; however, it seems that for each device they randomly generate a public/private key pair such that the public key is an IPv4 address they statically assign to that device. While the probability is low that there will be IPv4 address collision in a class C subnet, there is still a possibility, and that doesn't sit right with me. SPAN is looking into using tinc (http://www.tinc-vpn.org/) for P2P VPN across the mesh and sharing keys via NFC.

SPAN is also looking into supporting iOS. Have the Commotion folks looked into that yet?

Getting ad-hoc support into the Android framework would be amazing. The root requirement is a no-go for a lot of users. Also, it would be great if an Android app. could simply work over the mesh without needing to be customized against a special mesh API. That's why SPAN came up with a transparent proxy that runs on the device and routes outgoing packets to our mesh service. Of course apps will need an API to get the peer list, etc., but existing "stock" Android apps wouldn't need to change.

Jeffrey Robble
Software Systems Engineer
The MITRE Corporation (Bedford)
Office: 781.271.2790

From: Hans of Guardian <hans at guardianproject.info<mailto:hans at guardianproject.info>>
Date: Friday, October 12, 2012 8:56 PM
To: "m0nk.omg.pwnies at gmail.com<mailto:m0nk.omg.pwnies at gmail.com>" <m0nk.omg.pwnies at gmail.com<mailto:m0nk.omg.pwnies at gmail.com>>
Cc: "Robble, Jeff" <jrobble at mitre.org<mailto:jrobble at mitre.org>>, List Commotion Development <commotion-dev at lists.chambana.net<mailto:commotion-dev at lists.chambana.net>>
Subject: Re: SPAN Android App


Spreading the word would be awesome.  And helping us figure out the SPAN code would be great as well.

.hc

On Oct 12, 2012, at 7:36 PM, m0nk wrote:

That is so incredibly awesome.

I'll start digging into the project this weekend, sorry I have not come across it before.
I'd personally love to be involved and help out with damn near anything mesh related if it has the ability to reach the populous.

I'll be speaking at ToorCon in San Diego next weekend about meshing Android and some other conferences later this year.  Please let me know what can and can not be made "public" from your end…
I started speaking about our specific project, but I have been focusing my recent talks more on overall concepts, headaches and technical challenges across the projects that I know of.

Thanks for the info… i am sure I will have questions after digging into the code and project.

josh

--
m0nk
Sent with Sparrow<http://www.sparrowmailapp.com/?sig>


On Friday, October 12, 2012 at 5:00 PM, Hans of Guardian wrote:

Hey there,

I just saw that you posted the SPAN sources, thanks to Teco Boot's post to the olsr-dev list. It looks like there is a lot of overlap between the SPAN project, and the Commotion project, specifically olsrd on Android, and its issues. We're also working with Serval as well and are looking to get some more code sharing going on. To start with, an android ad-hoc framework to encapsulate all the tricks needed to enable adhoc mode for various devices.

If you're interested in trying the Commotion MeshTether app, you can get a test build here:
https://commotionwireless.net/blog/meshtether-test-release

and the source is here:
https://code.commotionwireless.net/projects/commotion-android

In related news, you'll probably be happy to hear that we've been working with some Google engineers on their 20% time to get adhoc support into Android. The patch is been submitted to the Android gerrit, has been verified by their automated builder, and is just waiting for final approval from the Android dev:

https://android-review.googlesource.com/#/c/43070/

.hc


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-dev/attachments/20121015/fa7c2ae1/attachment.html>