<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>I've looked into Wifi Direct a little bit. From what I've seen, its not a replacement for adhoc mode unless you want to use Wifi Direct meshing. Wifi Direct meshing is limited to 32 nodes in the spec. So if you're happy with all meshes always under 32 nodes, then it could work well.</div><div><br></div><div>.hc</div><br><div><div>On Oct 15, 2012, at 1:36 PM, Robble, Jeff wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>
<div>Also, have you guys looked into Wi-Fi Direct?</div>
<div>
<div>
<div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<br>
</div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
Jeffrey Robble<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
Software Systems Engineer<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
The MITRE Corporation (Bedford)<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
Office: 781.271.2790</div>
</div>
</div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><Robble>, "Robble, Jeff" <<a href="mailto:jrobble@mitre.org">jrobble@mitre.org</a>><br>
<span style="font-weight:bold">Date: </span>Monday, October 15, 2012 1:34 PM<br>
<span style="font-weight:bold">To: </span>Hans of Guardian <<a href="mailto:hans@guardianproject.info">hans@guardianproject.info</a>><br>
<span style="font-weight:bold">Cc: </span>List Commotion Development <<a href="mailto:commotion-dev@lists.chambana.net">commotion-dev@lists.chambana.net</a>>, "Chong, Oliver L" <<a href="mailto:ochong@mitre.org">ochong@mitre.org</a>>, "Durrant, Sheldon A."
<<a href="mailto:sdurrant@mitre.org">sdurrant@mitre.org</a>>, "<a href="mailto:m0nk.omg.pwnies@gmail.com">m0nk.omg.pwnies@gmail.com</a>" <<a href="mailto:m0nk.omg.pwnies@gmail.com">m0nk.omg.pwnies@gmail.com</a>><br>
<span style="font-weight:bold">Subject: </span>Re: SPAN Android App<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>
<div>
<div>Hi Hans,</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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:
<a href="http://www.olsr.org/?q=node/13">http://www.olsr.org/?q=node/13</a></div>
<div><br>
</div>
<div>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)?</div>
<div><br>
</div>
<div>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 (<a href="http://www.tinc-vpn.org/">http://www.tinc-vpn.org/</a>) for P2P VPN across the mesh and sharing keys
via NFC.</div>
<div><br>
</div>
<div>SPAN is also looking into supporting iOS. Have the Commotion folks looked into that yet?</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
</div>
<div>
<div>
<div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
Jeffrey Robble<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
Software Systems Engineer<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
The MITRE Corporation (Bedford)<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
Office: 781.271.2790</div>
</div>
</div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Hans of Guardian <<a href="mailto:hans@guardianproject.info">hans@guardianproject.info</a>><br>
<span style="font-weight:bold">Date: </span>Friday, October 12, 2012 8:56 PM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:m0nk.omg.pwnies@gmail.com">m0nk.omg.pwnies@gmail.com</a>" <<a href="mailto:m0nk.omg.pwnies@gmail.com">m0nk.omg.pwnies@gmail.com</a>><br>
<span style="font-weight:bold">Cc: </span>"Robble, Jeff" <<a href="mailto:jrobble@mitre.org">jrobble@mitre.org</a>>, List Commotion Development <<a href="mailto:commotion-dev@lists.chambana.net">commotion-dev@lists.chambana.net</a>><br>
<span style="font-weight:bold">Subject: </span>Re: SPAN Android App<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div><br>
</div>
<div>Spreading the word would be awesome. And helping us figure out the SPAN code would be great as well.</div>
<div><br>
</div>
<div>.hc</div>
<br>
<div>
<div>On Oct 12, 2012, at 7:36 PM, m0nk wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div>That is so incredibly awesome. </div>
<div><br>
</div>
<div>I'll start digging into the project this weekend, sorry I have not come across it before.</div>
<div>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. </div>
<div><br>
</div>
<div>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…</div>
<div>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.</div>
<div><br>
</div>
<div>Thanks for the info… i am sure I will have questions after digging into the code and project.</div>
<div><br>
</div>
<div>josh</div>
<div>
<div><br>
</div>
<div>-- </div>
<div>m0nk</div>
<div>Sent with <a href="http://www.sparrowmailapp.com/?sig">Sparrow</a></div>
<div><br>
</div>
</div><p style="color: #A0A0A8;">On Friday, October 12, 2012 at 5:00 PM, Hans of Guardian wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span>
<div>
<div>
<div><br>
</div>
<div>Hey there,</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>If you're interested in trying the Commotion MeshTether app, you can get a test build here:</div>
<div><a href="https://commotionwireless.net/blog/meshtether-test-release">https://commotionwireless.net/blog/meshtether-test-release</a></div>
<div><br>
</div>
<div>and the source is here:</div>
<div><a href="https://code.commotionwireless.net/projects/commotion-android">https://code.commotionwireless.net/projects/commotion-android</a></div>
<div><br>
</div>
<div>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:</div>
<div><br>
</div>
<div><a href="https://android-review.googlesource.com/#/c/43070/">https://android-review.googlesource.com/#/c/43070/</a></div>
<div><br>
</div>
<div>.hc</div>
</div>
</div>
</span></blockquote>
<div><br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</span></div>
</div>
</span>
</div>
</blockquote></div><br></body></html>