US Robotics USR2410 Manual de usuario descargar pdf (Pagina 44)

Chapter 6 -

System Automation

When setting up the mesh routers, as with any other consumer router, a monitor and keyboard

were not available. Without this requirement, the mesh routers would not have been easily set up

in an arbitrary location. For example, during testing, mesh routers were set up along the hallway

in the Engineering III building, not in a lab setting. To be able to properly manage the mesh

routers, and to confirm that the machine booted properly, a number of utilities and scripts were

used. These are presented in the following sections and code is available in Appendix C.

6.1.1

Meshstart

A start up script that used the system beep command to exhibit the mesh router’s status, configure

the devices, and to start the Click Modular Router software was created. For more information

about the Click Modular Router software, see Chapter 5.

There were a number of steps required to setup a system to behave as one of the mesh routers.

These included configuring the wireless device, configuring the client interface device if present

and needed, and choosing the correct configuration to be used by the Click Modular Router. To

make sure that when one of the systems was booted up it had successfully completed all the

required steps, a Perl program was written. This program was broken into two separate files, one

called meshstart.init the other called meshstart. Meshstart.init was run during the boot up

process, and calls meshstart. Meshstart executed the required commands based on a

configuration file called meshstart.conf, which defined all of the parameters needed to set up the

wireless card for communicating with the other mesh wireless devices. These parameters include

the device name, channel to use, network id (ESSID) and the address with which the device

should be configured. Also defined in the meshstart.conf file is the client device information. If

this configuration information is present, the specified device is configured to allow client

machines access to the mesh network through the system. The meshstart.conf file also defines

whether or not to run the Click software in userspace or as a kernel module, and what click

configuration to use. As the meshstart program runs, and sets up the devices, it beeps in a way to

notify if there was a problem with running one of the commands or if everything was successful.

A description of the beeps can be found in Table 6-1 below. A failure of a setup step can be heard

when after hearing the beep sequence for the step, the failure beep sequence is heard. Meshstart

is configured to run during the boot up process, reading the meshstart.conf file and properly

configuring the system.

1 2 ... 39 40 41 42 43 44 45 46 47 48 49 ... 106 107

Sin comentarios

US Robotics USR2410 Manual de usuario Pagina 44