High Performance Node - Specification

From WirelessAfrica
Jump to navigation Jump to search

High Performance Node Development & Test Network

High Performance Node - Dev and Test Network

(Note) This is not the proper page for this discussion, will move it later. Keeping it here as much of the discussions currently happening, is around topics on this page

  • Development
    • Lab development platforms
  • Locally deployed Test network
    • Installation of a 10 node network on the CSIR campus
    • Tx power set on minimum and attenuators used to minimise transmission distance
    • Sites on the campus need to be selected
    • Equipment for test network needs to be procured - suppliers?
      • Enclosures - Poynting Antennas
      • Gateworks boards -
      • Dual WiFi cards -
      • Power over Ethernet(poE)injectors -
  • Demo nodes
    • The thinking is around something the size of a linksys, using a small patch antenna ( This can use used when the demo needs to travel).


Current Bokkie router (Poynting)

HPN based on current “Bokkie” router, to become “Bokkie v2”

Block Diagram of HPN

Block diagram of HPN


  • Based on Poynting Enclosure (Product code:WLAN-A0033)
  • Modification: swap 1x 2.4 GHz omni-directional antenna for 1x 5.8 GHz omni-directional antenna


Current Compact flash card being used

Enclosure - Other

  • 4x Gateworks board mounting standoffs
  • External Mounting bracket



  • Wall mounting bracket (different types depending on type of wall - specification)
  • Mounting pole (different types - spec)
  • M10\M12 Coach Screws and fisher plugs (# depending on wall mounting bracket)
  • 10x pack Cable ties
  • Earthing kit Webb Industries have earthing kits that can be used. see http://www.webb.co.za/index.php?nav=news&ID=50
    • Clamp\lug on one end of earthing cable for attachment onto wireless installation mounting bracket
    • Earthing cable: Length (?), Gauge (?) - 10-15mm diameter
    • Clamp on spike for other end of earthing cable for attachment onto earthing spike
    • Earthing spike - 1m (driven into the ground at base of wall of the wireless installation)


Firmware: "bokkie1 mesh distribution"

This software specification is based on the current FreeBSD version of the firmware. I have named it "bokkie1 mesh distribution" as a working title (for want of a better name - please provide a nice snazzy one)

  • A script is used to build the current firmware build based on the platform. Please insert the list of packages\utilites\etc used to make this build.
    • packages installed
      • dnsmasq
      • ffproxy
      • olsrd
      • php - This is not used at the moment pending what the GUI needs.
      • thttpd - Maybe change to mini_httpd because it can do ssl.
    • files with local changes
      • crontab fstab host.conf motd nsswitch.conf syslog.conf termcap ttys boot.config loader.conf localtime motd rc.conf snmpd.config beastie.4th early.sh .cshrc rc.d/var gateways zebra.conf.org ripd.conf.org ripngd.conf.org master.passwd group
    • local stuff
      • rc.early
      • rc.conf.mesh.{dbn|pta}
      • rc.subr.mesh
      • add-dd-dns
      • add-mesh-dns
      • dd-list
      • del-dead-dns
      • wlanwd
      • newupdate
      • dnsmasq.conf
      • dnsmasqaddrs
      • regdns
      • rssi
      • rc.d/4over6
      • 4over6
      • bsnmpd6
      • upgrade(2)
      • /root/.ssh/{id_dsa|id_dsa.pub|config}
      • /usr/local/etc/{olsrd.conf|rc.d/olsrd} start_olsrd
      • rc.d/ffproxy
      • udpr
      • pinger
      • namedb/*
    • Scripts and configs used to build all of this:
      • build_chroot, create_it, checkfiles
      • small-clean.cfg, small-7-arm.cfg, small-7.cfg, small-7-32m.cfg
      • small-file-list, small-file-curr-list.diff, small-file-named-list, small-file-noathstats-list
  • Additional
    • IPv4 over IPv6
      • Allows for automatic configuration of the tunnels
      • Automatic DHCP of IPv4
    • Supports HTTPS and HTTP
    • Runs mini_httpd web server


The GUI has two main links, Status and Administration(basic). The Status link is unencrypted, however, the Administrion link(s) are encrypted and authenticated.

  • Status link provides for the user to view:
    • The configuration status of the Node
    • The routing table
    • The link/signal strength with respect to other nodes in the vicinity
  • Administration
    • Change hostname
    • Set the NTP server (remote/local)
    • Set DNS server (remote/local)
    • Create a cluster
    • Command line interafce

Remote upgradeable

  • What current functionality exists?
  • What further development is needed?
  • What limitations exits?
    • Cannot be remotely upgraded if there is a protocol change

Further development to functionality

  • GSM modem to the development network and first nodes in the field
  • Watchdog
    • Problem with native watchdog on Gateworks Avila board
      • Boot failure resuscitation
    • Specific to Gateworks Avila Board
    • PCB to be developed that plugs into the JTag connector
  • WEP security
  • Mechanism to get the GPS co-ord configured in the HPN. This can later be used in the visualisation tool on the gateway with a Google plot of the nodes.
LED type indicator system
  • Indicator:
    • Visual: Example of indicator system (using LEDs mounted at the bottom of the enclosure) for alignment, type of box (ie. red or green, which is an indication of the channel being used), power to box
      • 1 - Left most LED can be either RED or GREEN, showing type of box - this can be configured in the setup and commissioning of the router(indication of the channel being used), ie. this is either a red box or a green box
      • 1 - Right most LED shows power
      • 2 - 5 Used as 4 point scale for signal strength
    • Audible: with a buzzer used for alignment
    • Check the power consumption (especially for multiple LEDs), and how to start/stop the beeping mode (may also be used for LEDs)