This manual explains how to configure the LayGO protocol stack and its protocol services.

Each LayGO protocol and system component defines a configuration profile containing parameters which affect their behavior at runtime. The C language definition of the configuration profile is a structure exported by a xxxx_api.h file. These structures can be directly manipulated by applications, but LayGO also supports the use of configuration files.

Configuration files contain profiles which can be loaded at runtime with a minimum of coding effort. They are normally created and edited using the edcfg utility discussed in this manual. However, the LayGO API functions lgo_LoadConfiguration() and lgo_SaveConfiguration() allow applications to read and write their own configuration files. See the LayGO API Manual for details.

Note: Use of configuration files is optional but highly recommended. Using configuration files insulates applications from any future changes to the configuration structures.

This manual contains details on the configuration parameters for each system component and protocol layer. The protocol sections also contain information about the mapping of LayGO API functions to protocol events and the protocol-specific ioctl functions supported by each layer.