Quantcast
Channel: Enabling Communications, Anywhere, Anytime
Viewing all 144 articles
Browse latest View live

Tools for mapping Mesh Extender coverage

$
0
0
In previous tests of the Mesh Extenders we were manually noting the signal strength at various locations, and then drawing maps by hand to get an idea of the coverage.

Thanks to the great work by one of our students, Loïc, we now have a nice tool that lets us collect GPS traces annotated with Mesh Extender signal strength.

Now we can collect continuous traces of signal strength very easily.  Here is one where Loïc put one Mesh Extender on a hills hoist in a suburban back-yard, and set about riding around the neighbourhood with the other Mesh Extender in his backpack to see how it performed:


The ability to quickly deploy Mesh Extenders without great care or aiming is well illustrated in this situation.

A map of the signal strength is visible below.  Red and brown means no link, while orange through blue is progressively stronger signal.


As in previous tests, we see coverage of a couple of hundred metres in typical suburban conditions, reaching to a radius of around ten houses, and thus covering approximately 25x - 100x as many houses as Wi-Fi.


Range Testing Mesh Extenders in Boston & at the MIT Media Lab

$
0
0
While here in Boston with the Shuttleworth Foundation, I decided to take the opportunity to see what kind of coverage we can obtain with a Mesh Extender in my hotel room.  

My room is on the 7th floor of the Kendall Hotel in Cambridge, which provides a good vantage point in amongst buildings that are often 10 - 20 floors.  I put the Mesh Extender on top of the wardrobe in my room, and set about walking around the local area to see how far the signal would reach.

You can get an idea of the coverage in the map below, generated using the coverage mapping tool written by Loïc, one of our students.  This tool reads the signal strength directly from Mesh Extender via the ServalD HTTP interface, and merging it with a GPS fix from the phone.  The resulting trace is processed with some scripts to produce an HTML page that overlays the data points on Google Maps.
We expect to release the mapping tool in the next few weeks. 

You can see that coverage in this case extends one to two blocks. Not surprisingly, range is shortest when faced with the tallest buildings, e.g., through the Boston Marriot Hotel.  Nonetheless, the signal almost always appears to penetrate through an entire building, and is usable on the other side.  

Basically, whereas Wi-Fi can punch through about one wall before fading out, the UHF packet radio link can punch through something like 10 walls before fading out.

Points with confirmed coverage back to my hotel room. Actual coverage is somewhat better, but the collection tool needs tweaking to show spots with good link below 10dB.

The keen eye will notice that this area is right next to MIT, and indeed we have coverage right around the MIT Media Lab where we are having our Shuttleworth Foundation meetings.  So one morning I decided to see if we could establish a mesh between my hotel room and the room we were in the Media Lab building.  

That room faces the away from the hotel, so the signal would have to punch through the Media Lab building, as well as the MIT Health Services building which is in between the lab and the hotel.  In the image below the room in the media lab where we were meeting is roughly indicated by the arrow near the bottom of the image.  



As the link was from the top floor of one building to the top floor of another building it is likely that some signal followed a free space path outside of the buildings, but there is certainly no line-of-sight path.

The link frustratingly dropped out once we were inside the building with the Mesh Extender. However, we did find that by placing the Mesh Extender out on the deck outside that we had a steady link back to the hotel room.  So while we couldn't have the Mesh Extender inside the room, it was possible to have a mesh phone inside the room, talking to the Mesh Extender outside on the deck, and from there back to the hotel. In the image below you can see that the phone could see both Mesh Extenders, as well as the other phone in my pocket.  The Mesh Extender is visible out on the deck in the background.

In the MIT Media Lab with link back to the hotel via the Mesh Extender on the balcony.
So while it would have been nice if link could be sustained inside the building, it was still pretty easy to establish a link between two buildings a couple of hundred metres apart in a built-up urban area, with one of the Mesh Extenders indoors.

Range Testing Serval Mesh Extender on the National Mall in Washington with the New America Foundation

$
0
0


The following is a joint blog post with the New America Foundation's OTI/Commotion Wireless project:

On an uncharacteristically chilly May morning, members of the Commotion and Serval projects set out for the National Mall in Washington, DC to test Serval's latest piece of hardware: the Mesh Extender. Commotion Wireless is an open-source toolkit of software, documentation, and training materials that strengthens communities by allowing them to build their own local communication infrastructure. Serval is a mesh networking software designed to act as an ad hoc communications network where other infrastructure is either absent or unavailable -- such as in remote areas or disaster scenarios.


Some of us stood at the Washington Monument while others were at the Lincoln Memorial -- a distance of nearly a mile. Using two Mesh Extenders, we successfully sent text messages and shared files between our phones (running Serval) -- entirely independent of the cellular infrastructure.


On the way back to the office, we hopped on the Metro -- DC's subway system -- to run another impromptu field test. From opposite ends of the train, we were able to send and receive messages through six subway cars (and their passengers) while the train was moving. That meant we could do something Metro riders usually can't -- send and receive messages while in the subway tunnels.

These results represent a significant breakthrough, since until now Serval and Commotion have been limited by the relatively short range and low power of Wi-Fi. In addition to increasing range and power, the Mesh Extender  removes a major obstacle to widespread adoption of mesh for mobile phones: rooting. Normally a prerequisite for Androids to connect to a mesh network, this technically challenging process for installing a new operating system can cause problems down the road for the rooted phone. In this case, the Mesh Extender routes the messages, not the users' phones, eliminating the need for rooting.

However, the Mesh Extender is still a prototype. Software issues make voice calls possible but indecipherable. Further development, including better error correction and noise cancellation, will allow for not only voice calls but potentially even longer-distance connections. Despite these remaining challenges, the Mesh Extender is a huge step towards reliable decentralized infrastructure.

A device with multiple radios and a small processor, the Mesh Extender essentially acts as a relay between phones running Serval software. It is lightweight, portable, and relatively cheap and easy to build. The parts can be purchased and assembled for as little as $99. Impressively, the battery can support three to five days of continuous use. The Mesh Extender uses omni-directional antennas (as opposed to point-to-point links), which make for much easier set up and
configuration, and allow for truly mobile networks.

The Mesh Extender operates simultaneously on the 2.4 GHz and 900 MHz bands, both of which are unlicensed. This allows phones running Serval to tether to the closest Mesh Extender over Wi-Fi (2.4 GHz), while the Mesh Extenders themselves communicate over the 900 MHz band, which is both less congested and has better propagation characteristics.

Crossing the Charles River by Mesh Extender

$
0
0
I am just about to head off to the airport to head home to Australia, but had the chance last night to do one last range test with the Mesh Extenders here in Boston.

Again I put one Mesh Extender on the wardrobe here in room 704 at the Kendall Hotel



I then caught up with Jon from the Awesome Foundation, and we took advantage of the warm evening to walk across the bridge to the far side of the Charles River to see if we could get signal over there.

Once we were on the far side, we were able to obtain an adequate signal over a stretch of around a kilometre along the far bank.  Here I am with the Mesh Extender, connected in a single hop to the Mesh Extender in my hotel room.


To give an idea of where we were, and the distance of the link, see the image below. We also had link at most points along the Charles River Reservation IV.


While we were obviously down at ground level, I was conscious of the many apartment buildings along the foreshore of Back Bay East that would have even better for linking across the Charles River.

There are probably hundreds of apartments along Storrow Drive that would have been able to get a link to the Kendall Hotel with a Mesh Extender, again confirming my view that the Mesh Extenders make mesh telephony much more practical, by making it easy to connect relatively distant locations without aiming antennae, or needing lots of hops.

Balloon Communications

$
0
0
It has been interesting to read about Google's plans to deliver internet via a fleet of helium balloons.

Despite the scepticism from some parts, it has real potential.

Indeed, broadcasting from flying and floating platforms is not new.

The US have used "stratovision" to broadcast TV in rural areas and war zones for half a century.

Closer to home, and closer to what Google are doing, the Serval Project and the Horus demonstrated helium-lofted mesh network nodes at Linux Conference Australia 2011 just after the Brisbane down-town area was flooded, to enable local mobile communications -- potentially including internet:


The main difference is we used a relatively small tethered balloon, partly because of cost (our budget was $100 including helium), and partly because we were using Wi-Fi communications instead of dedicated commercially licensed spectrum.

But like Google, we also gained some experience working with the Civil Aviation Authority here in Australia, because the conference venue was in the flight path to Brisbane airport.

While we only lofted the balloon to about 50m, way too low to cause actual trouble to air traffic, we wanted to do the right thing, so contacted Brisbane air traffic control.  The result was the first time my activities have shown up on a NOTAM ("Notice to All Airmen"):

C0126/11
       OBST TETHERED UNLIT WX BALLOON
       PSN 220 MAG 8.35NM FM BRISBANE VOR
       SFC TO 400FT AGL

       FROM 01 262335 TO 01 270500

Watching the video you will see that it is quite a feasible way to provide communications.  For me one of the very satisfying points was seeing people who had never used mesh communications before trying it out, and understanding it's potential to help in times of need, e.g., following disaster.

Note that our mesh communications and telephony software has advanced a long way from what is shown in the video.

If we were running the test again, we would loft one of our new prototype Mesh Extender units that use a UHF radio in an ISM band (similar rules as for the 2.4GHz Wi-Fi band) as well as Wi-Fi and could feasibly operate at higher altitude, and provide communications over many kilometres.

Crowd-funding the Serval Mesh Extender Announcement & Video

$
0
0
Those who have been following the blog here will have heard about our prototype Mesh Extenders that we have been developing.

In short, the Mesh Extender lets us break the "Wi-Fi barrier" of Mesh Telephony, typically extending range 10x to 100x depending on the environment.  This means that a single mesh hop can span a block or two in typical suburban or urban areas, and into the kilometres in open terrain.

This has tremendous potential to increase the utility of mesh telephony.

Also, because the Mesh Extender acts as a Wi-Fi access point for phones, it completely removes the need for "rooting" or "jail breaking" a phone for it to participate on the mesh.

This also means that lots of nearby phones can use a single Mesh Extender.

In other words, it makes the mesh better and easier to join.

We now want to refine these prototypes into something that can end up being a saleable product so that we can get to the point where the general public can buy them and use them.

We thought about venture capital and other routes, but we don't want to compromise the openness of the technology we are creating.

This means that private and public philanthropic funding have been the mainstay until now, and has been vital in getting the Serval Mesh and Mesh Extenders to their current stage where we can make secure mesh phone calls, send secure mesh text messages and share files over the mesh.

While this sort of funding has been great, it is not really geared to moving to the product stage.

This is why we decided to launch a crowd-funding campaign so that the people who want the technology we are creating, and will ultimately benefit, can participate in funding its development, and help make sure that the Serval Mesh is available as soon as possible, and remains completely free and open software and hardware.


Our target is US$300,000 which will allow us to design a product based around the prototype Mesh Extenders, and attack the outstanding software work required to make the Mesh Extender an easy-to-use and automatically updating appliance.

I invite you to take a look at our campaign at http://igg.me/at/speakfreely, and encourage you to spread the word far and wide, and if you would like, to contribute.

Serval in the MIT Technology Review

$
0
0
See the current issue of the MIT Technology Review for a write up about Serval and Commotion and mesh telephony in general:

http://www.technologyreview.com/news/516571/build-your-own-internet-with-mobile-mesh-networking/

They provide a nice summary of our long running problems with Android failing to support ad-hoc Wi-Fi, and that this prevents various humanitarian uses of Android phones.  We encourage Google to review their policy.

Shameless plug: The crowd-funding campaign they mention as launching soon is http://igg.me/at/speakfreely

Interfacing between the Serval Mesh and Cellular Networks (Part 2)

$
0
0
In a previous post we described our initial work towards creating a two-way mesh to cellular gateway using mobile phones as the only major component.

Thanks to Michael's great work, we have this now working.

Calling out is automated with the Serval Mesh software announcing itself as a GSM gateway when you attempt to call an off-mesh number, as you can see in the screen shot below.

He also managed to get incoming calls working.

He even managed to get DTMF parsing working, so that when you call into the mesh you get prompted for the number on the mesh you wish to be connected to, and you can then just dial the number on your phone, and get put through.

This last feat is quite amazing given that the DTMF codes have to survive being played through tiny ear buds, re-recorded through a tiny microphone before actually being decoded.

We know that the frequency response of the audio path is very non-linear, but Michael managed to come up with a commendably simple signal processing solution that could work in spite of this.

You can see how easy it is to setup in the following video:


On the same day we filmed that video, I also called one of our friends in New Zealand Red Cross using this arrangement.

That is, from our lab in Australia, I dialed his normal New Zealand number from on the mesh, selected "GSM Gateway" when offered, and then waited to be connected.

There was a lot of delay early in the call, bit it then caught up to within a couple of seconds for the rest of the call.

That delay was longer than normal for a mesh call, possibly because one of the mesh phones was acting as the access point for the phone I was using, and there may have been some CPU contention (we were using 500MHz IDEOS U8180s that are very slow), combined with Wi-Fi packet loss in the University building here due to the presence of lots of other Wi-Fi devices.

Anyway, Matthew and I had a usable and effective conversation for about five minutes discussing recent news.

Matthew's assessment of the audio quality was "not great, but definitely usable, and certainly much better than nothing."

We agree, and really, this is the point: there are 100 better ways to connect a mesh to the outside world, but if all you have on hand during a disaster is a couple of phones and some duct-tape, there was previously no solution -- but now there is.

We plan to integrate this capability into the mainline Serval Mesh app in the future.

To help us do this, and generally advance the Serval Mesh, please consider supporting our crowd-funding campaign at igg.me/at/speakfreely, and spreading the news about that campaign far and wide.



Android phone prices hit new low

$
0
0
The march of technology keeps driving the price of low-end Android phones ever lower.

Economics is a strange beast at the best of times, and all the more so when it comes to the price of mobile phone handsets as various subsidies can reduce the price substantially.

The result is that the cheapest countries to buy mobile phones are those where the carriers are willing to offer the deepest subsidies, and it isn't always obvious which countries those are.

My anecdotal experience suggests that the two cheapest countries, with prices generally similar, are Kenya, which makes sense since GDP-per-capita is relatively low, and Australia, where, well, to be honest I don't really know.

We have previously bought Android phones like the Huawei IDEOS U8180 for AUD$50 - AUD$70.

Then the other day I noticed that the local supermarket is selling an Android phone for AUD$40, and I thought that was cheap:



But then the local Post Office catalogue arrived offering the Huawei Y100 (U8185) for AUD$29 including a 2GB microSD card and $2 starter SIM card with Vodafone:


This $29 wonder includes GPS, Bluetooth, an 800MHz processor and a screen so small it almost hurts. Basically they are a 50% faster version of the U8180's we are so familiar with.  The extra speed makes a noticeable difference.

We had the latest version of the Serval Mesh running on it within a few minutes:



Sure, both of these phones are also benefit from discounting through the retail chain, in much the same way that all the Android phones around the $50 mark were a year ago.  History suggests that Android phones at this kind of price-point will become regularly available over the coming year.




Smaller, more elegant Mesh Extender prototype

$
0
0
(Please check out our crowd-funding campaign at http://igg.me/at/speakfreely to help us turn the Mesh Extender into a product that can be used to help people communicate in difficult circumstances.)

There is nothing like being busy to increase the incentive to just get something done in spite of the things that make it impossible.

So today I decided that I would actually get around to making a Mesh Extender prototype out of a TP-Link MR3020 wireless router.

These have an Atheros 9k chipset, so they have the good Wi-Fi chip that we need, which is usually the tricky bit. They have a USB port for the mass storage that Rhizome needs to run.  So far so good.

The previous TP-Link (WR703N) routers we used didn't have an easily accessible serial port -- they just had a couple of tiny points on the PCB you could solder to.

In contrast, the MR3020 has real hole-through pins that can take a standard 0.1" single-inline header, and some of the earlier builds actually have the connector installed.

With the help of a work-experience student we put OpenWRT on several of the MR3020s and got them about half-way to working as Mesh Extenders, able to mesh over Wi-Fi.

That just left the serial connection to the UHF packet radio, which is what I attacked today.

The serial port normally has a login and is used to log kernel messages.  After figuring out how to turn off as much of that as possible short of recompiling the kernel, I then set about connecting up one of the packet radio modules and getting some holes drilled so that we could put the RFD900 packet radio in the little case.  Well, mostly in the case, because the heat-sink sticks out a bit.

The following pictures show how this makes a neat little unit:





We have some Verbatim nano USB memory sticks on order so that we can replace the big USB drive on the side with a little tiny bump, which will further stream line the shape.

That leaves only the battery to consider, and we have a few options for those.

Importantly, we have shed the USB hub and USB to serial adapter, which between them were consuming perhaps 20% of the total power budget, and made the resulting prototypes frustratingly large.

Indeed, compare the images below of the older prototypes to the images above, where the only missing component is a battery connected to the USB port of the MR3020.




Once we cut a hole for the heat-sink and get the lid fitting back on, and install the nano USB sticks, we should have a nice pocket-sized prototyping platform from which to refine.

I really could have used some mesh communications gear last weekend

$
0
0
(Please also take a look at our crowd-funding campaign at igg.me/at/speakfreely)

Last weekend my family and I stayed down at Second Valley, an hour and a half drive from home in Adelaide.  It is a popular beach holiday spot, with a variety of beach shacks, permanent homes and farm land.



We arrived Friday night in the rain, only to discover that the power was out.  There are a lot of trees around the area, and with the woolly weather it was quite possible that a one had fallen across the power lines somewhere, and so given the late hour we figured we would just get ourselves and the kids into bed in the dark, and worry about it in the morning.

What we didn't know until after, was that the problem was the power junction on the property filling up with rain water, and so no crew was going to be called out automatically:

This box should have been full of electricity, not water.

We soon discovered that our assumption that the local infrastructure would be available had caused us to be quite poorly prepared.  We only had our mobile phones and a laptop computer for light sources, and hadn't bothered to fully charge any of them.

This was a bit of a problem as our little people still needed story time, and some light in the room to get to sleep.

But electricity wasn't all we were without, because water makes its way from this tank:

The rain tank


 Through this electric pump:
The water pump

And into this rather vital household appliance:

The toilet
Fortunately we could use a bucket to fill the cistern from the water tank. Oh yes, and the septic system is electric as well, so even using buckets to operate the cistern we were only buying time before the manure hit the, well, lawn.

The gas stove also had an electric starter, but fortunately we had a gas lighter, and could at least boil water.

To add to the challenge, there is no land-line phone in the house, and the mobile phone coverage is of the kind that requires you to stand on the toilet seat and make a strange face, or stand outside facing 17 degrees NNW and hold the phone exactly three Royal Cubits above ground level to get signal.

This made it a difficult proposition to call the electricity network to find out when the power would come back.  So we weathered the night, but in the morning there was still no power.  But there was still rain.

After eventually making the call standing in the rain, we were informed that a work crew had been dispatched and would come as soon as they were able.

They did eventually turn up, but only after they had tried to call us, and as far as we can work out, didn't come immediately because they couldn't get in touch with us to make sure we would be home.

All in all, the lack of effective communications meant that we were without power for probably 12 hours longer than necessary.

So here I am running a crowd-funding campaign for mobile mesh telephony, and so I should be amongst the most prepared in the event of things going wrong communications wise.

But of course I hadn't bought any gear along with me, not a mesh extender, or even a mesh-cellular gateway made of duct-tape, so that I could at least have waited inside for the call back from the power company.

Maybe next time I go away, I will actually carry the tools I make.  

This is also why it is important that we make the Serval Mesh useful, even when things aren't going wrong, so that people are carrying it and know how to use it when the need arises.

View of Mesh Extender prototype with 50Wh external battery

$
0
0
Just a couple of quick snaps from in the lab today showing the Mesh Extender prototype with an external battery that should be sufficient to run it for 24 hours.

A lot of the battery case is empty air, so it would be possible to make something even more compact.

We might also look at making the shell of the mesh extender so that it can physically attach to a battery pack for simple one-piece operation when required, but still allow replacement with an external battery pack.



The battery pack is about the size of a Galaxy S2 phone, but 20mm thick.  As mentioned, this could be shrunk with a better battery pack than this cheap one we bought of deal extreme.

ISM 915MHz band availability in different countries

$
0
0
I found this handy table today that lists ISM band availability around 915MHz in a variety of different countries:

http://meshplus.com/?qa_faqs=is-an-fcc-license-required

While closer scrutiny is required, it is the best compilation of this data I have found yet, especially for countries outside of ITU Region 2.

Latest iteration of the Mesh Extender

$
0
0
We finally got our hands on some nano-USB memory sticks, and have adjusted the radio placement in the MR3020 routers we are using, so that the lid can go back on without duct-tape, and the whole unit looks much sleeker.

Also, we have some smaller and surprisingly complementary styled rechargeable battery units for them, that even have a percentage charge remaining indication.  All for $17.50 on ebay!

The result is as shown in the following photos.



The battery packs even have a 2-digit LED display to tell you how much battery capacity you have left -- very handy for in the field.






The ability to directly wire the RFD900 into these units simplifies the wiring amazingly, and really is one of the big enablers for being able to assemble the prototypes at an affordable cost:

The biggest outstanding challenge is finding a nano USB memory stick that is both reliable and works sensibly with OpenWRT.  Verbatim ones don't seem to work with OpenWRT properly, while SanDisk ones might still have the "go read-only and die" bug that others have reported.  Time will tell...

Demoing the Serval Mesh and Mesh Extenders to School Children as part of Australian National Science Week 2013

$
0
0
We were fortunate enough to win a National Science Week grant to run several events in the north of South Australia to demonstrate what we are doing primarily to school students in schools in regional and remote areas.  We were also able to include demonstrating the technology on a steam train.

Our itinerary took us from Adelaide to Port Augusta to Quorn to Hawker over two days.

The idea was to encourage students in the regional centre of Port Augusta and remote towns of Quorn and Hawker to see value and encourage an interest in science, technology, engineering and mathematics (STEM) subjects.

At Port Augusta we worked with 13 to 17 year olds, who quickly worked out how to use the Serval Mesh app on the phones we supplied.  We also had a visit from the local TV station, and we understand that they ran a story the following night.

Several of the guys from Project Horus joined us so that we could put Mesh Extenders up high and communicate with them over longer distances, which we did:

Here are a couple of the switched-on students from Port Augusta Secondary School holding the balloon that Mark and the other Project Horus setup for us.

You can also see our two kids in the foreground.  It was a very welcome change to not have to leave the family behind, but instead share some fun adventures with them.

We then moved along to Quorn and Hawker Area Schools.

Quorn has about 150 students from reception to year 12, and we spoke to all of them in two groups.  All age groups were able to interact with the technology, call each other, and enjoy the balloons organised by Project Horus.  The balloon did pop, though, as the wind picked up to gale force during the morning.

We then moved on to Hawker Area School which has just 47 students.  The wind was way too fast to do any outdoors balloon work, but we still had the students talking and texting within a few minutes in the class room.  We also explained how telephone networks function, even with the littlest kids, explaining how the centralised approach leads to single points of failure.  This was quite fun, with flying sharks making an appearance, as the photo shows:


It is amazing what you can teach six year olds if they don't know that it is material from a second year University course.  We then let the kids draw in their own additions to the diagram, which in addition to the extra flying shark trying to eat the cell tower included other people using mobile and fixed phone lines.  It was particularly impressive to see that a child under the age of 8 had worked out that the fixed phone line needed to be connected to the rest of the network:


By sheer chance Victor Harbor Primary School were staying at Hawker School overnight on their Outback Camp, so we spoke to them as well.

Mark and the guys had setup an indoor balloon for them, and spoke to them about their work, and getting penguins flying close to the edge of space:


Then we all went outside into the howling gale, and released the balloon into the wind to the delight of all. It disappeared so quickly that by the time the camera got organised it was just a small black speck over the tallest tree in this shot:


We rounded out the trip with our final event on the Pichi-Richi Steam Train on the Saturday.  Our idea was to talk to anyone on the train who was willing to listen, and to allow people to talk from end to end on the train.  Problems with the Mesh Extenders meant that we only had end-to-end communications when the train was going around corners, which fortunately is most of the time on the Pichi Richi Pass.



There is very little cellular coverage in the pass, allowing us to capture images like the following showing services available on a mesh-enabled phone where an ordinary phone would have none:


What was particularly nice on the train was one of the students at Quorn Area School was also a car captain on the train, and not only remembered what we had said the previous day, but showed further interest in what we were doing.  So all in all, I'd call the events a success.

Over-the-Mesh Updates for Serval Mesh Extender Prototypes

$
0
0
I have just spent the day working on field upgradability for the serval mesh extender prototypes.

Note that the following is how updates for the prototypes work at present. We expect that this may change over time, and is likely to be different in the final products.

Updates to servald will be supported in two different ways.

First, it will be possible to pull the USB memory stick from the unit and copy the new servald binary onto the stick.

Second, if there is no servald binary on the USB memory stick, then it will look for an update via Rhizome.  If there is an update, it will install it.  As with all Rhizome files, the updates are cryptographically protected so that only genuine updates will be accepted.

None of the update functions are automatic, because we want to place updates entirely under user control, as a partial protection against network poisoning attacks.

To effect an update (or to restart the servald on a mesh extender without turning it off and on again), just press the WPS button on the MR3020 router.

Of course, if something stuffs up, for example you have a bad update on the USB memory stick, then hold the WPS button down for 10 seconds and it will "factory reset" back to the original servald that shipped with it.

More as we develop it.

Honourable Mention at the Global Security Challenge Grand Final

$
0
0
Earlier in the year we entered the Serval Project into the Global Security Challenge.

The theme for this year's challenge was cyber-security, something that we felt was a good fit for the Serval Mesh, with its encrypted-by-default operation, ease of use, and applicability to a wide range of situations.  

The recent revelations of wide-spread wire-tapping by the NSA, GCHQ and others has only served to reinforce the relevance of a secure digital mobile communications platform that never gives unencrypted access to your communications to carriers or other organisations that might be pressured by agencies like the NSA.

So it was very pleasing when we were named finalists last month and invited to pitch at the grand final that was held yesterday here in London.

The grand final itself was an interesting event, with a diverse range of finalists from the UK, the USA, Israel, Sweden, Canada and Spain, and of course ourselves as the sole representative from the Southern hemisphere.  We were also unique in that we were the only social enterprise present.

Each finalist had six minutes to give a pitch, and then a ten minute question and answer session with the judges.  These were combined with the material that we had already submitted to determine the winner of each category.

The day was divided into pre-revenue and post-revenue companies.  I am not sure that they knew quite how to place us, because while we have received over a million dollars in philanthropic funding, we haven't made any commercial sales.

They had to make a decision, and that was to place us in the post-revenue category.  This placed us in the category with a number of innovative start-ups who are already active in the market place, and with business models and solutions that are well aligned with the existing security industry, and representing a formidable field for us to compete against.

So it was very pleasing when it was announced that we had come a close second place in our category. So close in fact, that they took the unusual step of awarding us an Honourable Mention, which apparently is not something that they normally do.  You can get an idea of how unusual this is by the handwritten annotation of honourable mention on the certificate:


While it would have been nice to win outright, it was an amazing affirmation for us to be named in the list of the ten most promising security related endeavours, and then to be recognised in this unusual way.

This is now the third time in the last three months that we have been recognised for our innovation in secure communications, following winning the communications category of The Technology Challenge for Atrocity Prevention, and being the only non-US entity accepted to present at a recent DARPA symposium on secure mesh networks.

Of course, none of this would have been possible without our team, or the support of Flinders University, the Shuttleworth Foundation, the New America Foundation, the NLnet Foundation and the Awesome Foundation and our many individual donors and volunteers.

Avoiding jet-lag completely, and other body-clock hacks.

$
0
0
Jet-lag is not fun.  Nobody likes jet-lag.

But for me, the situation is more acute.

First, I live in Australia, so travelling almost anywhere involves substantial time-shifts. I still remember my surprise when going to a conference in China and realising that: (a) I wasn't jet-lagged; and (b) everyone else was instead. Such is the effect of living in Australia.

Second, I have a young family at home, and also teach at a University.  This means that most of my trips have to be kept to the absolute minimum duration.  Take my two most recent trips:

Trip 1: Adelaide -> Washington DC -> Amsterdam -> Adelaide in 9 days, including a complete 24-hour time shift, and heading East all the way, which is reputed to be the worst direction for jet-lag (a subject I'll comment on later).

Trip 2: Adelaide -> London -> Adelaide in 95 hours. That's right, I wasn't even gone for four whole days. But I had to be fully in the London timezone immediately for meetings two hours after landing, and then on the one whole day I was there because I was presenting a grand-final pitch at the Global Security Challenge.  I then had to be back in Adelaide time straight away on returning, because I was rostered on at church, and then had a meeting that afternoon.

If I had tried these trips three years ago, it would have been jet-lag city.  Fortunately since then I have learned progressively more about an excellent and (for me at least) easy way to beat jet-lag before it even happens.

This is the fasting method of which there are lots of descriptions online, including this one.  But I want to add to the record, first by confirming that for me it works, and second, outlining my simplified approach, and some comments about one of the causes of killer week-long jet-lag that has been revealed by the discovery of the ability of the hunger clock to override the circadian body clock.  But first the method:

The method

1. Before departing, set watch to destination timezone.
2. Don't eat after 16h00 in destination time zone.
3. Try to sleep as much as you can on the plane so that you aren't sleep deprived on arrival (which is distinct from jet-lag, but no more fun). Pack an eye-mask or use the one they supply on board.  If you can manage it, snooze all the way on a 24 hour flight, with the odd movie etc to keep you occupied if you like.  The sleep part isn't important for the jet-lag, however, just your sleep deprivation, for reasons I will soon explain.
4. Do eat at 08h00 or similar sensible breakfast time in destination time zone.

When I say don't eat, I mean don't eat. Nothing. No fruit. No Juice. No oysters, roast turkey, custard pies or anything. Only water.

Why you can't even eat a little bit during the fast

The reason it is really, really, important that you don't eat during that 16 hour period is that your body needs to switch to "hungry mode", and get the idea that during that time there is no food coming. If you eat anything, no matter how small, during the fasting period, it is basically game over, go to jail, do not collect $200. Try again tomorrow, it's still better than having jet-lag for a week.

Why you need to eat breakfast at the right time

The reason it is really important to then eat a good breakfast at the right time, is that is the moment when your body clock shifts. Yup, your body clock shifts however many hours in the process of eating that breakfast.  Your hunger clock presses the reset button on your normal circadian body clock.

Now, there is a trick to this: Don't eat breakfast at the time you want to wake up, because you will begin to wake two hours before the time you ate breakfast. I can't remember where I read about this little fact, but once I realised it, suddenly a number of problems I had with the method previously made sense, and I was able to sort them out, largely by not giving in and eating at 05h30 or 06h00 instead of a couple of hours after I wanted to actually wake up.

Basically your body tries to be wide awake at breakfast time, whenever that is.  So if you have breakfast at 06h00 you will wake at 04h00, which was exactly the sort of problem I was having when I first tried this method.  Once I sorted that out, it worked beautifully for me.

How to have the worst jet-lag ever: eat in the middle of the night

Once I realised how that the hunger clock resets the circadian rhythm, and has this 2-hour preamble built into it, the jet-lag horror stories of several friends suddenly made sense: They got up in the middle of the night due to jet-lag, went out and partied, or ate something and watched a movie and then went back to bed.  Every time they did this, they encouraged their body clock to move 2-hours back.  I now believe that their horror stories of week-long jet-lag suddenly made a whole lot more sense. 

How to wake up early every morning if you are "not a morning person"

It also started to occur to me that many people who claim to be "night people" on the basis that they have trouble getting up "early" in fact are poor or late breakfasters.  It might be for many (I don't claim all) that if they force themselves to eat a substantial breakfast within 2 hours of their rising time that they might be able to pull their body clock forward that little bit, and keeping it there.  This is only conjecture, since I am basically a morning person.  I welcome people reporting their experiences.

Mesh Extender assembly

$
0
0
Following our crowd-funding campaign we have funds to build a number more mesh extenders, and get them out to some early adopters as well as to NZ Red Cross.  So the last few days have been a bit of a production line while we get the hardware assembled.

The worst part of the assembly is getting the lids of the MR3020 routers, which left me with a broken pocket knife and sore fingers for a couple of days.  Basically the lids are cemented to the main body of the case, and you have to break each point of cemented bond, without breaking the lid.  Some are much easier than others, depending, presumably, on the amount of cement used.  We had one lid cracked out of the ten units made.

Then it was soldering the radios and router PCBs together:

The cases are down with the engineering workshop services to get the holes drilled for the radio connectors, and some of the internal ribbing ground off so that the radio can sit flush with the inside of the case.

Otherwise, it has been teaching, and sorting out some of the local tax arrangements for the contributions from Australians in our crowd funding campaign.  If you put an Australian shipping address and requested a perk, then you will get a GST-inclusive tax invoice.  We won't be out of pocket with GST, because we budgeted for it, and also the GST on all the hardware will more than make up for the GST we have to pay on Australian contributions.

Our focus is now on fixing a couple of late issues with the mesh extender firmware so that it works at least for meshms over UHF radio.  Optimising the throughput for larger files will happen overtime, and be delivered as over-the-mesh updates.

Lets use Thingometrics instead of Biometrics

$
0
0
One of these pebbles could be your next password, and this is a much better idea than using your fingerprint as a password.  Sound crazy? Then read on.

Image in the public domain
It is entirely possible that a hundred people have thought of this before, and if so, my apologies.

Much ado is made of biometrics from time to time,  most recently on the latest iPhone.

Most of the attention focuses on how wonderful it is to be able to use your thumb, eye-ball or some other body part to identify yourself.

Many companies are formed based on the assumption that biometrics are secure, and are generally speaking A Good Idea.

However, as we have been reminded by the Chaos Computer Club (CCC) in Germany breaking the biometric authentication on the iPhone in less than two days using common household ingredients and just a photo of the fingerprint.

The CCC sum up many of the major problems with biometrics in their post:

"We hope that this finally puts to rest the illusions people have about fingerprint biometrics. It is plain stupid to use something that you can´t change and that you leave everywhere every day as a security token", said Frank Rieger, spokesperson of the CCC. "The public should no longer be fooled by the biometrics industry with false security claims. Biometrics is fundamentally a technology designed for oppression and control, not for securing everyday device access." Fingerprint biometrics in passports has been introduced in many countries despite the fact that by this global roll-out no security gain can be shown.

There are a few salient points in the above that are so important that they require repeating, as well as some important consequences. Please excuse the all caps, but these are really important points that need to be made again and again, because industry, government and individuals continue to be badly deluded as to the value and sensibility of biometrics as an authentication or access control.

1. You leave your fingerprint EVERYWHERE.  Despite the fact that we tell people to keep their passwords secret, the biometrics movement encourages people to use a password that is IMPOSSIBLE to keep secret.

2. Because you leave your fingerprint "password" everywhere, you don't know when someone has captured and compromised your password.  So you continue to acting like your fingerprint is secure, and so does your phone, your passport and everything else that depends on it.

3. If you do discover that someone is doing something naughty with your supposedly secret fingerprint password, YOU CANT CHANGE YOUR FINGERPRINTS.

4. Because of all of the above your fingerprint is of more value to naughty people who want to defraud you than it is to you.  

5. All of this is bad, because it creates economic incentives for bad people to STEAL YOUR FINGERPRINT, or worse STEAL YOUR RETINA.

6. In case you think that practically perfect fingerprint cloning on real fingers is impossible consider the following: It is well known that bricklayers often abrade their fingerprints completely, showing that making a "blank finger" is trivial.  All that remains is to engrave the blank finger with the target's finger print, e.g., using laser micro-surgery techniques.  I'm not saying that this would be trivial, but it is hopefully apparent that there are major problems facing fingerprint based identification, even if it advances to actually requiring a live person attached to the finger print.

We also know that normal passwords are both annoying and also have their own security problems. (Although at least you can give your password to someone and retain binocular vision and the ability to hold cutlery, and then get a new password to replace the old one.)

So, what should we do?

We should try to do something that will not make the biometrics lobby too upset, so that they don't push back with more lies and patently false claims about the security or sensibility of biometrics.

One way of doing this could be coming up with a scheme that can leverage the accurate object and surface imaging technologies that these companies have created, and allow them to rapidly transition focus from the largely counterproductive biometrics field.  In other words, lets leave them room to still make money and be prosperous.

Enter the idea of thingometrics instead of biometrics.

Basically, lets stop scanning body parts, and instead scan simple objects.

Simple objects can be easily chosen that:

1. are hard to clone from a photograph (unlike finger prints),
2. don't leave the means to reproduce them on surfaces everywhere. That is are more rivalous than not, instead of the practically nonrivalous nature of fingerprints.
3. can be given to a forceful attacker without having to hand over any body parts
4. can be easily replaced if ever compromised

Things like sea shells, small pebbles, a crumpled mass of stiff wire, or any other morphically stable robust object would be good candidates.  Attach them to your physical key ring for convenience. You could even use one of your existing physical keys for extra convenience (which always comes at a cost to security).

Need to change your password? Just go outside and find a new rock, or better yet take a monthly work-mandated trip to the beach to find your new password.

It would be quite possible to make a 3D printer to produce a pseudo-random object with a keyring attachment point if you want an more environmentally sensitive source of things to metric.

If you want to be super-paranoid you could reduce the residual risk of someone comprehensively imaging your password object from a distance by making the interior of it the password part.  Again, 3D printers would be your friend here, or if you have a handy supply of geodes would make for a password with street cred among your geologist friends.  If used with dedicated imaging sensors the complex interior need never be visible from the outside at all.

Oh yes, and with thingometrics you can easily implement some helpful security protocols.  For example, you can register anti-passwords, in the form of other objects that when presented cancel the authority of an other thingometric password, analogous to revocation certificates in PKI systems.

You might carry one anti-password with you, and one or more in a safe remote place so that if you lose (or are robbed) of your thingometric passwords anti-passwords you can easily cancel the stolen password (or instruct someone remotely to do so on your behalf).

You can also physically destroy a thingometric password if you are worried about it being captured, and because well chosen thingometric passwords are closer to being rivalous, you can have better confidence that no one else has obtained the password if you still hold the original.

3D printers and the like represent risks, but nothing is perfect, and the risks are much lower than with fingerprint biometrics which as previously noted leave sufficient imprint everywhere for people using relatively easy technologies like those developed by the CCC.

Thingometrics has the extra advantage that it could be implemented using the camera on a smart-phone, without needing to have an extra sensor.  At most, you might want a second camera for stereoscopic vision.   So not only is thingometrics safer for you, and more secure for your data, it can also be cheaper to implement.

It also means that it would be much easier to support in free and open software and operating systems, because there are no more funny closed drivers and firmware than normal.

So let's think about what would be needed to implement thingometrics in practice.

1. Some good image mapping algorithms, that can capture the shape and texture of an object in front of a camera to develop a detailed enough 3D image.

2. Some good image matching algorithms that can detect (or reject) an object being held in front of the camera.

And, er, that's about it really*.

I suspect that suitable technologies exist in part or in full in the academic literature and elsewhere, and that creating a functional system could be implemented fairly readily* by a skilled and dedicated team.

If you go for a dedicated sensor and the inside-out key idea described above, then this becomes much, much, simpler to do. It could probably be implemented in a semester by a good student (any volunteers? I'm happy to supervise. You don't have to be in Australia, either.)

So, here is the challenge: Let's get a bunch of us together to implement thingometrics, and give the world a better alternative to biometrics.  I've registered the domain names.  Now we just need the team.

Paul "I want to keep my thumbs" Gardner-Stephen.

* Which isn't to say that there wouldn't still be quite a bit of work. Everything is relative, after all.
Viewing all 144 articles
Browse latest View live