## SafeFire Links

### v1.3a

# Configuration Files

SafeFire Links uses configuration files to specify what Plugin Instances to load, how to connect the Instances and its configuration.

## Configuration file placement

If you do not specify configuration file in command line, SafeFire Links uses "sfppp.cfg" as default configuration file name. This file will be searched in the following folders (in the order specified below):

1. Current directory
2. Directory specified by ETC environment variable
3. Directory specified by HOME environment variable
4. Directory specified by LGSDIR environment variable

GUI version uses different approach: main configuration file is stored in PMPPP.INI file. Main configuration file in GUI version can be selected using Scenario combo box.

## Configuration file format

Configuration file consists of sections. Each section define variables. Each section has its name. Variables with same name in different sections are different variables.

Variable definition has the following format: `"name delimiter value"`

- name

  variable name. Characters in ranges 'a-z', 'A-Z', '0-9' and characters '_' and '.' are allowed.

- value

  variable value.

- delimiter

  either '=' or ':' character

For string variables the value is the whole configuration line starting from the first non-space symbol after the delimiter.

Some sections has special names:

1. general

   All variables from this section will be included into all other sections

2. ppp

   This is default root section

Root section is a special section which will be used as a starting point for determining binding dependencies and plugin loading order.

Each section can include unlimited number of files and other sections. You can use following commands:

> `!include "filename"
> @include "section"
> `
> Note: If "filename" has section definitions, the active session after processing include file will be the last session defined in the include file.

Note 1: Multiple sections with the same name make up one logical section.
Note 2: If one regular variable defined multiple times then last specified value has an effect. An example of non-regular variables are bindings, firewall rules and portmap rules: all instances of these variables are collected rather than replaced.

## Sample Configuration files

There are sample configuration files supplied with SafeFire Links that help users start their work fast.

To select sample configuration file that suits your needs best, see Up and Running book.

To examine plugin structure of sample configuration files see Sample Configuration files plugin connection charts

Return to documentation index | SafeFire Links (C) Link Guard Solutions 1999, 2000