An open todo list...

[m0nk]

SPAN is currently functional on a minimal set of devices.

We need to (in no real order):

* Test more devices (HTC, Moto, etc)

* Conquer the issues with the Qualcom chips

* Shift all traffic to IPv6 and benefit from the security inherent in the transition

* Implement a simplistic mechanism for handshakes and encrypting traffic around the mesh

* Continue to evolve the concept of enclaves

* Implement what I am calling "Mercedes Routing" - Basically splitting packets and ensuring they route through disjoint paths to avoid single point sniffing / capture

* Evangelize the tech and get more people excited

* Ponder the iOS devices some more

* Simplify the install and setup

* Contemplate merging with the Batman team / collaborate?

I'm sure there is a ton more, please post 'em.  It's just a start for a working list if anyone wants to volunteer.

[m0nk]

One of the cool things about the NinjaTel phone was the custom SimCard that pushed the devices to their network.  I think I'll spend a day or two poking at writing custom sims.  Might be a worthwhile endeavor if we can for the phone into mesh mode by simply supplying a new sim...

[m0nk]

stoker, please enable posting to this site via email.  I live on the phones to much to be forced to log into the web client to post things.

kthxbai

[stoker]

Done.

[monk dot]

thanks!

Done.

--
 
 

[Nick F]

m0nk, do you have the NinjaTel rom? Link is in this document: https://defcon.hackingyour.net/FlashingyourNinjatel.pdf

Is a comprehensive list of developers and their device arsenals being maintained? I have Sprint HTC EVO 3D, Virgin EVO 4G V, Droid 2 Global, Samsung Epic Touch, Samsung Exhibit II, LG Optimus V, and Acer Iconia Tab A100.

[Mike Trieu]

Just saw your ToorCon talk on YouTube and wanted to ask if your team has considered implementing the HWMP routing protocol adopted by the IEEE 802.11s standard. I believe the open80211s project for Linux has already banged out the code for the reactive (RM-AODV) and some of the proactive (tree mode) bits. You seem to be interested primarily in reactive protocols, so this should be right up your alley. The "radio-metric" part might be difficult to code, but some other groups have substituted that with a simpler hop-based metric. 

In regards to "Mercedes Routing", I'm not entirely sure of the scope of that idea, but it sounds like a great way to avoid co-channel interference from nearby adjacent nodes by attempting to prefer routes to nodes with less interference (which is actually what the "radio-metric" section of 802.11s addresses, IIRC). 

I totally support everything you mentioned on the list above and hope I can contribute in whatever way I can. I'm not much of a coder, but I do understand what's going on for the most part when I see it. This technology is the future, especially when some wired infrastructure networks are starting to voluntarily employ draconian policing standards on behalf of the content cartel like 6-strikes. 

[stoker]

Hi Mike,

Thanks for reaching out to us. 802.11s is on our radar but we haven't
looked too closely at it yet. Based on your description HWMP sounds
very appealing. We'll definitely have to check into the open80211s
project. A quick glance shows they set up the mesh using the "iw"
command with the "mp" (Mesh Point) interface type.

At a high level it seems that we'll need to make kernel-level changes
to truly support 802.11s. Alternatively, I wonder how difficult it
would be to compile the HWMP protocol itself into a stand-alone
daemon. Has that already been done?

Ugh, CAS. Don't get me started.

- stoker

> --
> You received this message because you are subscribed to the Google Groups
> "Smart Phone Ad-Hoc Networks" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to spandev+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Nivatius]

I just wanted to know if you are aware of FreiFunk, a german initiative that tries to build a free wifi mash. iirc they are using batman and openwrt
it whould be great if your project could make it possible to use phones as part of the network.

[jorda...@dlsu.edu.ph]

Hello, may I just if which of these can still be improved or implemented? Thank you!
--
<http://www.dlsu.edu.ph> <https://www.facebook.com/DLSU.Manila.100>
<http://instagram.com/dlsu> <https://twitter.com/dlsumanila>
<http://dlsumanila.tumblr.com/> <http://iblog.lasalle.ph/>

DISCLAIMER AND CONFIDENTIALITY NOTICE
The information contained in this e-mail, including those in its
attachments, is confidential and intended only for the person(s) or
entity(ies) to which it is addressed. If you are not an intended recipient,
you must not read, copy, store, disclose, distribute this message, or act
in reliance upon the information contained in it. If you received this
e-mail in error, please contact the sender and delete the material from any
computer or system. Any views expressed in this message are those of the
individual sender and may not necessarily reflect the views of De La Salle
University.

[stoker]

Out of all the ones m0nk listed, the only two that we've tackled so far are evangelizing SPAN and implementing some rudimentary iOS support.

If you'd like to help out, it comes down to where you want to spend your time. There are really four key areas:

1. Android kernel: Get ad-hoc mode working on modern Android devices. We mainly support Google and Samsung devices, but we've had requests for Motorola.

2. Android OS: Integrate SPAN more directly in the Settings app and Android framework. Get SPAN running on Kit Kat and Lollipop. Allow normal apps to use the SPAN network**

3. Routing protocol: Improve the routing protocol to make it more efficient and resource aware (respect power levels with willingness to be a multi-point relay, etc.). Add support for BATMAN**, AODV, and other routing protocols.

4. Mesh-aware apps: Implement mesh-aware apps, like P2P VOIP, P2P video chat, etc. (consider leveraging Jitsi project: https://jitsi.org/ **).

Personally, I believe that the big ones are the three I've marked with **.

- stoker