182010-03-24 13:11:06ptr_here172010-03-24 13:10:23ptr_here162010-03-24 13:09:25ptr_here152010-03-19 20:03:30ptr_here142010-03-19 16:28:39ptr_here132010-03-19 16:23:02ptr_here122010-03-19 16:15:59ptr_here112010-02-27 12:13:53ptr_here102010-02-26 19:42:44ip-62-235-238-228.dsl.scarlet.be92010-02-26 19:41:16ip-62-235-238-228.dsl.scarlet.be82010-02-26 19:40:28ptr_here72010-02-26 19:39:49ip-62-235-238-228.dsl.scarlet.be62010-02-26 19:39:40ip-62-235-238-228.dsl.scarlet.be52010-02-26 19:39:08ip-62-235-238-228.dsl.scarlet.be42010-02-26 19:38:48ptr_here32010-02-26 19:38:08ip-62-235-238-228.dsl.scarlet.be22010-02-26 19:36:56ptr_here12010-02-26 19:26:15ptr_here

use this NodeConfig scripts to easily change the configuration of any number of nodes. Just connect all nodes over the cabled ethernet network, note all the mac-addresses of the nodes you want to configure, and run the available scripts configure all of those. usage of the attached scripts: ./telnet-loop.sh nodetable.csv nodeconfigscript will connect to all nodes (one-by-one), listed in the nodetable.csv (mac-addresses, etc.) execute the nodeconfigscript _on the node. It is using the telnet daemon running on the nodes to connect. the variant ssh-loop.sh uses ssh to connect to the nodes -- use ssh keys to connect without having to enter passwords... use copy-loop.sh to copy files over to all of the nodes listed in your table.

BattleMeshV3/NodeConfigScript/Zlan is a general configuration (gateway to the internet on wired side etc) BattleMeshV3/NodeConfigScript/Olsr configuration of basic olsr node BattleMeshV3/NodeConfigScript/Babel configuration of babel node BattleMeshV3/NodeConfigScript/Batman configuration of batman node

usefull short fragments of code to script the configuration -- we use the 'uci' command to set the system configuration, as it is standard on openwrt and easy to use command line tool.

the 'node-configuration-factory' parses the node table, and exports the parameters specified using the variable names @PARAM0@ to @PARAM9@ -- use these in your scripts for node specific parameters. eg. if you specified an ip address in the 4th column IP="@PARAM3@"

the wireless device has different names on different types of devices -- you can query the name from the uci system (it's typically 'wifi0' or 'radio0') and then use it further in your script, eg.

as it is mandatory to keep the wired interface configured with it's default settings (ip 192.168.1.1/24) for the node-configuration-factory to work -- you need to configure an alias interface if you want to use the ethernet interface with other configuration settings. eg.

executing commands after booting -- quick and dirty eg. (PARAM7 parameter contained a static routing configuration in this case: 'route add -net 192.168.3.0/24 gw 192.168.13.1 && route add -net 192.168.13.0/24 gw 192.168.4.1' ) /etc/rc.local << EOF ]]> /proc/sys/net/ipv4/ip_forward eval "@PARAM7@" exit 0 EOF]]>

a neat, easy and clean way to reset a node is to use a feature of the squashfs+jffs filesystem: the squashfs partition contains the pristine install, while the jffs contains all configuration and added packages. executing the openwrt command firstboot will cleanup the jffs partition and reset the configuration to its initial state