8.10 Configuration Files

Here a short list of the files generated by fli4l ``on-the-fly'' at boot time.

Provider configuration
- etc/ppp/pap-secrets
- etc/ppp/chap-secrets
DNS configuration
- etc/resolv.conf
- etc/dnsmasq.conf
- etc/dnsmasq_dhcp.conf
- etc/resolv.dnsmasq
Hosts-File
- etc/hosts
imond-configuration
- etc/imond.conf

8.10.1 Provider Configuration

For the providers chosen User-ID and password are adapted in etc/ppp/pap-secrets.

Example for Provider Planet-Interkom:

# Secrets for authentication using PAP
# client        server  secret                  IP addresses
"anonymer"      *       "surfer"                *

In this example ``anonymer"' is the USER-ID. As a remote server in principle anybody is allowed (hence ``*"'). ``surfer"' is the password for the Provider Planet-Interkom.

8.10.2 DNS Configuration

You can use fli4l as a DNS server. Why this is meaningful (and for Windows PCs in the LAN even mandatory) is explained in the documentation of the ``base"' package.

The resolver file etc/resolv.conf contains the domain name and the name server to use. It has the following contents (where ``domain.de"' only is a placeholder for the value of the configuration variable DOMAIN_NAME):

        search domain.de
        nameserver 127.0.0.1

The DNS server dnsmasq is configured by the file etc/dnsmasq.conf. It is automatically generated during boot by processing the scripts rc001.base and rc370.dnsmasq and might look like this:

user=dns
group=dns
resolv-file=/etc/resolv.dnsmasq
no-poll
no-negcache
bogus-priv
log-queries
domain-suffix=lan.fli4l
local=/lan.fli4l/
domain-needed
expand-hosts
filterwin2k
conf-file=/etc/dnsmasq_dhcp.conf

8.10.3 Hosts File

This file contains a mapping of host names to IP addresses. This assignment, however, is used only locally on the flil4 and is not visible for other computers in the LAN. This file is actually redundant if a local DNS server is started in addition.

8.10.4 imond Configuration

The file etc/imond.conf is constructed amongst others from the configuration variables CIRC_x_NAME, CIRC_x_ROUTE, CIRC_x_CHARGEINT and CIRC_x_TIMES. It can consist of up to 32 lines (except for comment lines). Each line has eight columns:

Range weekday to weekday
Range hour to hour
Device (ipppX or isdnX)
Circuit with default route: ``yes"'/``no"'
Phone number
Name of the circuits
Phone charges per minute in Euros
Charge interval in seconds

Here an example:

#day  hour  device  defroute  phone        name        charge  ch-int
Mo-Fr 18-09 ippp0   yes       010280192306 Addcom      0.0248  60
Sa-Su 00-24 ippp0   yes       010280192306 Addcom      0.0248  60
Mo-Fr 09-18 ippp1   yes       019160       Compuserve  0.019   180
Mo-Fr 09-18 isdn2   no        0221xxxxxxx  Firma       0.08    90
Mo-Fr 18-09 isdn2   no        0221xxxxxxx  Firma       0.03    90
Sa-Su 00-24 isdn2   no        0221xxxxxxx  Firma       0.03    90

Further explanations for Least-Cost-Routing can be found in the documentation of the package ``base"'.

8.10.5 The File `/etc/.profile`

The file /etc/.profile contains user-defined settings for the shell. To overwrite the default settings you have to create a file etc/.profile below the configuration directory. You may enter settings for the command prompt or abbreviations (so-called ``Aliases"') here.

Important: This file may not contain an exit!

Examples:

alias ll='ls -al'

8.10.6 redScripts in `/etc/profile.d/`

In the directory /etc/profile.d/ one may store scripts that will be executed when starting a shell and thus may influence the shell's environment. Typically OPT packages will place scripts there to define special evironment variables necessary for the programs they contain.

If both scripts in /etc/profile.d/ and the file /etc/.profile exist, scripts in /etc/profile.d/ will be executed after the script /etc/.profile.