Configuring a node

Compact flash nodes and CD-ROM nodes with a floppy drive installed can be configured via a web-interface and clicking on "Config".

Configurable values are:

channel
This can be any valid channel for the protocol being used. For 802.11b this is any integer between 1 and 11. Every node in a given mesh must be on the same channel.
wired interface
This can be set to "auto", "dhcpd", or "dhclient". Depending on the setting the node will either act as a DHCP client or a DHCP server. If it is a DHCP client then it will act as an "internet connected node". The default is "auto".
hostname
This is the name by which this host identifies itself.
latitude, longitude
The latitude and longitude for use by the visualization engine. Do not set these unless you have also custom configured RouteViz with a local map and it's latitude and longitude corners.
nameservers
A comma separated list of nameservers that will be used locally and given out to DHCP clients to use for their lookups. You should choose something local to your ISP or a public DNS server.
ssid
A unique identifier for the whole mesh cloud, this must be the same one all machines that wish to be part of the mesh.

Configuring a node creates the file /etc/cuw_config on a node. That file which is simply a flat file containing variable assignments. You can untar an upgrade image, replace it's cuw_config file, then retar it and then apply it as an upgrade. This is an easy way to create a localized distribution from the standard builds.

Wind
Submitted by Wind on Mon, 2005-07-11 12:48.

Self-Healing DNS?
As nodes should strive to be truly maintenance-free over a long period of time, a static list of DNS machines may not be sufficient. I find that DNS servers, especially public servers, are always going down and getting overcrowded. Ideally, I would want the node to test the DNS machines regularly and only give out the addresses of servers that give a timely response.

Perhaps it could look at the routed traffic to see if there are DNS machines in use that the node doesn't have on its list, and then add them. I don't claim to know if this is a good idea, and I know that we don't want people using an untrustworthy DNS source.

Could desktop-based nodes (with extra speed and memory) also be set up as DNS machines?