HowTo build your own mesh node

Firstly:

You will need the following:

Hardware:

Node:

Either a PC or a Wireless Router or SBC Single Board Computer

Antennae:

Buy or make your own (see Home-Brew Antennae).

Other:

  1. Cables: Rf and UTP cable
  2. POE convertors, Buy or make your own (see Home-Brew POE)
  3. Pole and brackets

Firmware

Your wireless router may require firmware updates that will be made available here.

OpenWRT and spinoffs (Freifunk, DD-WRT)

Sveasoft

Software

Routing

Firstly you need to choose a routing protocol, if any, that suits the rest of your network. You need to make sure that your node has the routing protocol installed and configured. For instance, you may need to install an OLSR client. Some firmware versions, like Freifunk's, have routing protocols installed by default.

Then:

Build it!

See Linksys hack for 1st stab at this, more soon!

Software/Firmware Settings

IP Allocation You will need to obtain an IP address for your node. 192.***.***.***/**

Routing protocl Settings

Example (OLSR):

HNA:

HowTo create an ipk package

TOOLS

Get the script rightfully called ipkg-build at, among other places, ftp://ftp.handhelds.org/packages/ipkg-utils, or http://www.mizi.com/download/mz20/ipkg-build.

CREATING THE PACKAGE STRUCTURE

Say you wanna create a package called MyPackage; you further wanna package the project called MyProject. Then do the following:

  1. Create a directory called MyPackage.
  2. Inside directory MyPackage, create a directory called CONTROL.
  3. Copy your project (MyProject) to the MyPackage directory.
  4. Inside directory CONTORL creating a file called control.

NOTE:

When the package is installed on the target, the MyPAckage directory will be created with respect to root. So if you wanted your files to be installed in /usr/bin on the target system, then our project would in this case be “/usr/bin”. That is you create inside directory MyPackage a directory called /usr/bin.

FORMAT AND CONTENTS OF /CONTROL/control

Package: MyPackage

Priority: optional // default

Version: 1.0 //package version

Architecture: mipsel

Maintainer: I_maintain@you.com

Source: ftp:ftp:122.122.122.122 //See Note below

Section: misc //See Note below

Description: This is an attempt to create ipkg.

NOTE:

The fields Section and Source seem rather useless to me in this example and I initially left them out; however the ipkg-build script complained requiring them, so I just put them in as a workaround without knowing/”caring” of their need. There are other fields not included here which you might need for your purposes, check the web for more.

Further the comments are mine for this documentation purposes only and the script MIGHT NOT permit comments.

RUNNING THE ipkg-build SCRIPT

Now simply run (of course being outside of the directory MyPackage):

“./ipkg-build –c –o root –g root MyPackage” // as root or non-root, or

“./ipkg-build –c MyPackage” //as root

IF all’s well, a package on the current directory will be created.

NOTE:

Without the “-c” option, I could not get the package installed successfully, you can try with or without and see for yourself.

HowTo create/be part of a VPN

If you want to be part of a Virtual Private Network, you will require VPN software on your client.

HowTo Stabilise a ver 2.2 WRT54G running OpenWRT based firmware

After a lot of tweaking OLSR running on Linksys has had no "ping down" messages for about 5 days now. Some of the tips to getting OLSR on OpenWRT stable.

1. Lock all the nodes to 802.11B don't let it auto sense 2. If there are any v2.2 hardware devices, change the clock speed to 216MHz with the following commands1

nvram set clkfreq=216
nvram commit
reboot

3. Lock the RX and TX antenna to the one you connected your external antenna too, don't use AUTO. TAKE NOTE!!! On Version 2.0 hardware Antenna A is on the left looking from the front of the linksys and and on Version 2.,2 hardware Antenna A is on the right looking from the fron of the linksys. This caught me out a few times.