welcome: please sign in

The following 194 words could not be found in the dictionary of 1 words (including 1 LocalSpellingWords) and are highlighted below:
10min   4x   5x   Access   added   address   allow   an   and   ap51   aptitude   are   as   at   attachment   battery   be   been   before   both   build   by   can   cat   check   com   common   conditions   config   configuration   connected   consumption   containing   copy   daemon   Debian   detected   dev   device   devices   different   dir   directories   directory   Dlink   done   downloads   embedded   etc   every   exchange   exchanging   exit   experimental   exports   extensively   extract   file   files   Flash   flash   flashed   flashing   Flashing   folder   Fonera   Foneras   For   for   from   Further   further   gz   had   hand   Happy   has   hasn   have   http   if   image   images   in   Increase   install   instances   ip   is   it   It   its   Kamikaze   kamikaze   kernel   latter   let   like   ln   log   low   M3   makes   manually   memory   mesh   minimal   mode   necessary   network   newly   nfs   nodes   Note   Now   of   on   one   only   open   Open   or   other   over   package   packages   patch   Patches   patches   port   Port   port1   port2   port3   port4   possible   procedure   race   reboot   reducing   restarting   revision   ro   router   Router   running   same   scripts   selection   seperate   server   Setup   Several   showed   single   some   soon   srv   Station   status   still   successful   such   support   svn   switch   Symlinks   symlinks   tar   telnet   tested   that   The   the   them   Then   there   They   time   tmp   to   tool   trunk   uci   up   update   used   ve   Warning   well   were   which   you   your  

Clear message
location: BattleMeshV3 / FlashRouter

Flashing Station

The tool used for the flashing procedure is ap51-flash. Several patches have been added to support a low-memory consumption mode as well as scripts for the OpenWRT package which allow running an ap51-flash daemon on every LAN port of an embedded device like the Dlink DIR-300 and flashing 4 devices at the same time. Further both flashing images from the RAM (up to 7MB for a Dlink flash router) or a seperate NFS server is possible (for the WBM3, the latter has been done).

Warning: It hasn't been tested extensively for such a flashing-battery for 20 nodes before. The WBM3 showed, that there are still some race conditions in the tool and scripts, which makes restarting single instances manually necessary from time to time.

The Setup

|   |
|   |
|   \----- Debian PC, running a NFS server
\------(WAN-Port) 5x Dlink DIR-300
                             \----- 4x Foneras

NFS server configuration

aptitude install nfs-kernel-server nfs-common



Symlinks to image file directories (ln -s ...):

ln -s /directory/to/image-files /srv/nfs/images/port1
ln -s /directory/to/image-files /srv/nfs/images/port2
ln -s /directory/to/image-files /srv/nfs/images/port3
ln -s /directory/to/image-files /srv/nfs/images/port4

Now you can exchange different images for flashing by exchanging the /srv/nfs/images/ folder containing the symlinks.

Flash Router

For the WBM3, there've been some experimental patches been added to the ap51-flash tool. They are further reducing its RAM consumption on the one hand and to let ap51-flash exit only, if it detected a successful reboot of a newly flashed device (before you had to check manually if the 10min. for flashing a Fonera were over).

Note: Increase ip address on WAN (in /etc/config/network) for every other flash router connected to the same switch

Then build your OpenWRT flash router image(s) and flash it/them on your soon to be Flash-Router(s).

Access to flash router: telnet 192.168.2.x

Flashing status: cat /tmp/ap51-flash.log

Happy flashing!

BattleMeshV3/FlashRouter (last edited 2010-06-05 17:03:17 by 213)