Qualcomm Atheros make a bunch of combo bluetooth + 802.11 mini-pcie NICs that you can use to achieve what you're doing, but on PC hardware.

What's missing is bluetooth 3.0 and AMP (Alternate MAC/PHY) support in the OS. If someone hacks that up, you can also do this on openwrt boxes. Which, btw, would be awesome.



adrian



On 29 August 2013 13:47, Paige <veeforvoluntary@gmail.com> wrote:
I hear you for sure re: closed source. I would personally really love
to see it opened up for the world to make use of too. Can't say there's
anything in the company road map and I doubt they will open up the app
code but stay tuned for news on the protocol.

We've noticed Bluetooth and WiFi interference at times (scanning for
nearby clients on BT can sometimes knock out WiFi for example) but most
chips in smartphones and laptops can use BT and WiFi simultaneously for
transmitting data.  We also use WiFi direct for those Android devices
that support it. There's a reason why this sort of thing is only
possible with the emergence of smartphones. It's just too bad we can't
reach iOS users.

I just imagine an area with meshed home routers plus the overlay
meshing for a super efficient infrastructure which optimizes for energy
/ battery consumption, extending each nodes reach and offering
redundancy for backup connections. Each mesh works well on it's own but
they're also complimentary.

Thanks for the feedback! ;)

On Thu Aug 29 10:13:41 2013, Adrian Chadd wrote:
> This is cool stuff. But, what we really need for this to be done on
> _open_ platforms is for someone to code up a Bluetooth 4.0
> alternate-PHY thing for some open source operating system that lets
> one glue the BT and wifi stacks together so they can dump data where
> appropriate.
>
> Now, for the real feedback:
>
> * bluetooth is lower power and shorter range, but it's also much lower
> throughput (compared to 11n) for the same range to an adjacent device;
> * it overlaps the whole 2ghz range, so if you're doing a lot of
> bluetooth transmit, you're interfering with nearby 2ghz wifi devices;
> * it also will be an "or" with the onboard wifi - ie, you can't
> transmit bluetooth and 2ghz wifi simultaneously on a lot of chips.
> There's an antenna switch that stops you from doing this;
> * almost none of the open source stuff has sane transmit power or rate
> control hooks that would let you get away with much higher density
> 2ghz meshing - why transmit at full power if you're only talking to
> someone 3ft away?
>
> I like what you're doing but a lot of what you're doing is tucked away
> in closed source blobs. It's hard to implement that on more open
> platforms.
>
> Once people here get their (atheros!) mesh hardware doing much more
> useful things, I'm happy to sit down and do more brainstorming in
> relation to what you can do with the hardware and how you can do evil
> things at the 802.11 layer.
>
>
>
> -adrian
>
> (still hacking away at TDMA and 11n in his spare time..)
>
>
>
> On 29 August 2013 09:38, Paige <veeforvoluntary@gmail.com
> <mailto:veeforvoluntary@gmail.com>> wrote:
>
>     For those of you who haven't heard the news from Jenny, yet: Open
>     Garden decided to publicly release the original white paper
>     "Multi-hop Wi-Fi Offload
>     <https://opengarden.com/Multi-hop_Wi-Fi_Offload.pdf>" by CTO,
>     Stanislav Shalunov.
>
>     Hopefully this brings some inspiration and answers some questions
>     (ex. Mitar: Why Bluetooth?)
>
>     Also, please excuse my lack of participation this past month -
>     I'll be back in the action next month. I'm also going to a
>     festival called Libertopia <http://libertopia.org> this weekend in
>     San Diego where I'll attempt to spread the word.  These people are
>     really into alternative, decentralized services.
>
>     I'm starting my drive down tonight so have a great meeting and
>     enjoy the weekend everyone!
>
>     Peace.
>     -Paige
>
>     _______________________________________________
>     mesh mailing list
>     mesh@lists.sudoroom.org <mailto:mesh@lists.sudoroom.org>
>     http://lists.sudoroom.org/listinfo/mesh
>
>