Wifi is Hard

While I was watching the Air Stream guys clamber over my roof I was thinking about Wifi and the the Village Telco.

My Wifi experience is steadily growing. I have now been involved in a couple of long distance links with directional antennas and several mesh networks. Some patterns are emerging:

  • Long distance Wifi is an inherently unreliable medium. It’s no where near as reliable a DSL, or mobile phones, or a TV antenna installation that “just works” for years. Expect a lot of work to set up a reliable link, and ongoing work by skilled people to maintain the links.
  • Each node takes a surprisingly large amount of hard work to set up – on that Sunday we invested around 4 man days, and the link is not complete yet. In Dili our first mesh link took over a week to set up due to interference problems. However even in Timor Leste I can buy a sim-card and have reliable telephony (and 3G Internet) in 60 seconds.
  • There is also work to maintain Wifi links, they periodically go down for one reason or another. Once you set them up you are not finished. There is a dubious plus side to this – it means a job for life for the people running the networks!
  • One reason Wifi links are hard in the need for Line of Sight (LOS). Do not underestimate this requirement. It means pain. Wifi works fine indoor for a few 10’s of meters. Outdoors, once you get past 100m or so, you need Line of Sight. If a tree or other obstacle get between you and the other node your link won’t work. This sounds easy, but in practice if you have a 25m tree, you need a 25m tower. This is very tough from a mechanical point of view – it means big, complex towers, lots of work, and physical safety issues. Even on my house we needed a 12m height, just to clear some of the local obstacles you get in a 1st world neighbourhood. This means a big, guyed, mast, and man-days of effort for installation. These photos show what was required for our first node in Dili (although it got easier after that):
  • Another big issue is interference from other 2.4 GHz activity, in particular the hidden node problem. This has been my biggest problem in the Dili and Kilkenny meshes. In practice it means small packets tend to get through, but large ones do not. In an extreme case for one link in Dili we needed to resort to Ethernet cable as a Wifi link simply wouldn’t work. Directional antennas can help this problem, but mesh routing need omnis by definition. In practice, the mesh networks I have seen have a mixture of omni and directional links.

Mesh nodes in the Village Telco are designed to be set up by people with modest Wifi skills in remote, developing world locations, where technical help (like an Air Stream team), 1st world hardware and Wifi equipment shops are not available. If you need one more D-shackle, a Nanostation 2, or a new grid antenna that’s too bad, expensive, and months of delay while it gets shipped in.

Village Telco end users are going to depend on these networks for telephone calls. In some cases it might be their only telecommunications. End users have high expectations for telephone network up-time – much higher than for Internet. People running these networks (the Village Telco Entrepreneur) will be investing their life savings and expecting to generate an income.

So a key challenge of the Village Telco is to take an inherently unreliable, hard to set up, hard to maintain technology (long range Wifi), and make it simple and reliable in a 3rd world environment when installed and maintained by local people.

I am gathering data on this challenge as the Dili Village Telco grows. Over the next few months we will get experience with up time and scale up to 100 nodes. I am hoping that mesh networks will offer reliability advantages over point-point, statically routed Wifi links, and that installation gets smoother with experience and a denser mesh. The up time of the 10 node pilot network to date has been good. Despite the set-up hassles, the Timorese guys are hungry for more Potatoes. The magic of free local calls makes the set-up effort worth it. I’ll post more on this (and an update of the Dili Village Telco) soon.

Last week I was chatting with Alipio, one of my friends in Timor Leste. He has experience in mesh networks and Ubuntu Linux, and was a great help with the Dili Village Telco Workshop last April. Alipio is excited about the possibilities of the Mesh Potato and Village Telco. If it can be shown to work, he wants to promote the system to the Timorese government. However he is wary – foreigners are always dropping out the sky with magic technology that breaks 2 days after they leave. I asked him what he needs to see:

  1. The Timor Leste government wants to see sustainable, durable, renewable, up to date technology.
  2. It needs to be locally owned and operated, not driven by 1st world people.
  3. It needs to work reliably for 6-12 months before he would consider promoting it to his government.
  4. It needs to work.

9 thoughts on “Wifi is Hard”

  1. Just one small comment about the ‘unreliability’ of your wifi mesh networks versus the other telecommunications networks. I disagree that wifi is necessarily any more or less reliable than any of the other networks. It should be pretty obvious that the operational challenges of engineering and maintaining a network falls on the company/people who build that network.

    When you build that network, that is you, but when you are a user of the network, as in the case of a mobile network or fixed line network, it isn’t. I wonder how much the likes of Telstra, Optus and Vodafone spend on maintenance of their respective networks? :)

    By the way, I’m not trying to lessen what you are doing, I think that is brilliant and have been following your blog entries for quite some time, just trying to point out that now you are sitting on the other side of the bridge.

  2. Good point Darryl.

    Either way our job at the Village Telco is to make it easy for the guy setting up and maintaining the network, and reliable for the end users. This might be achieved by putting systems and software in place that performs all the back-room network maintenance that 1st networks employ people for.

  3. Darryl,

    Telstra, Optus and Vodafone have exclusive use of their channels, and can call upon legal resources if anyone infringes upon them. 2.4GHz is a war zone. My 2.4GHz mouse won’t work over more than about 300mm on a Saturday evening. The rest of the week it works over about 2m.

  4. The tower has the look of something swaying in the breeze. :-) There do, however, appear to be guy ropes descending from high up on the tower, so I expect its really quite vertical, and not moving too much.

  5. No much breeze – that flag looking object in the foreground seems to show the air is
    calm. Anyways, it seems a crazy sort of person that climbs those small, thin

  6. Probably worth finding out where the need for babysitting comes from. The frequency? Competition on the band? The choice of antennae? What else? And then finding solutions for each and implementing them. And documenting them, writing the big handbook of deploying ‘taters in the process.

    Also, now you know why telco equipment is *expensive*. Engineering it less means more techie time to babysit the gear. It’s easy to overlook, but the handsets are highly optimised against the base stations, and unlike an internet (“end to end”), telco networks contain considerable high-level logic to the point that you barely need any in the handset.

    And since you are effectively building a telco on “internet” technology, you get to deal with the reverse of what telco engineers run into trying to build an internet.

    Over here there’s a telco-also-doing-isp offering add-on subscriptions for filtered email (on their *horrible* exchange bodge, now for the entirety of their aol-type clientele), anti-virus, malware blocking, and so on. They’re effectively trying to own the end-user device (with their branded software) and services, even though you paid for the computer, on the grounds that end-users call the support line for trouble with that too. Hey, if that’s what they expect, you can’t blame the isp^Wtelco to try and deliver it. Whether it’s wise of the customer to wish for this is another thing entirely.

    But my point is that this sort of thing needs addressing too. It’s not just about the technology. Far from it. In fact that’s where the white-man-leaves-the-hardware-ceases-to-function syndrome comes from. And yes, it is our fault for failing to address it.

Comments are closed.