Next: 3.13 General circuit configuration Up: 3. Base configuration Previous: 3.11 Domain configuration
Default setting: START_IMOND='no'
START_IMOND controls whether to start the imond server or not. The imond server is responsible for monitoring/controlling the fli4l router and for the so-called least cost routing. You can find a detailed description of the Client/Server interface imond in a separate appendix.
Important: The least cost routing funtionality of fli4l can only be used when imond is running. Time-based switching of connections is impossible without imond!
Starting with version 1.5, imond is mandatory for ISDN and DSL routing. In this case you have to set START_IMOND='yes'. If you use fli4l as a router between LANs only, you should set START_IMOND='no'.
The TCP/IP port where imond should wait for connections. You shouldn't change the default value `5000' unless in very exceptional cases.
Default setting: IMOND_PASS=''
This variable can be used to set a user password for imond. If a client connects to imond at port 5000, imond expects the client to provide this password before processing any requests, with the exception of the commands ``quit'', ``help'', and ``pass''. If you leave IMOND_PASS empty, no password is necessary.
The variables
control whether providing the user password is sufficient to execute the control commands like Dial, Hangup, Reboot, or Changing the Default Route, or whether you need a special admin password for these requests (see below).
Default setting: IMOND_ADMIN_PASS=''
Using the Admin Passwords the client receives all the rights and can thus use all control functions of the server imond - regardless of the content of the variables IMOND_ENABLE, IMOND_DIAL etc. If you leave IMOND_ADMIN_PASS empty, the user password is sufficient to gain all rights!
The imond server is able to display the router's online/offline state via a LED. This LED is connected to a serial port as follows:
25 pin connector:
20 DTR -------- 1kOhm ----- >| ---------- 7 GND
9 pin connector:
4 DTR -------- 1kOhm ----- >| ---------- 5 GND
The LED is on if an ISDN or DSL connection is established, otherwise it is off. If you want this the other way round you have to reverse the polarity of the LED. You can reduce the dropper resistor down to 470 ohm if the LED is lit too dimly.
It is also possible to use two different coloured LEDs. In this case you have to connect the second LED together with a dropper resistor between DTR and GND too, but with reversed polarity. Then either the first or the second LED will be lit depending on the router's state. Another possibility is to use a DUO LED (two-coloured, three pins).
Currently, the serial port's RTS pin behaves exactly as the DTR pin. You could even attach a third LED for displaying the online/offline state. However, this behaviour may change in the future.
The variable IMOND_LED has to be set to the name of the serial port to where the LED is attached; possible values are `com1', `com2', `com3', and `com4'. Leave the variable empty if you don't use an LED.
If setting IMOND_BEEP='yes', imond will emit a two-tone sound over the PC speaker whenever the router's state changes from offline to online and the other way round. In the first case, the higher tone follows the lower one. In the second case, the higher tone is emitted before the lower one.
Default setting: IMOND_LOG='no'
You can set IMOND_LOG='yes' in order to log connections in the
file /var/log/imond.log. This file can be copied i.e. by scp to
another host e.g. for statistical purposes. However, using scp requires
you to install and configure the sshd package appropriately.
The structure of the log file entries is described in Table 3.10.
| Entry | Meaning |
| Circuit | the name of the circuit for which the entry has been created |
| Start time | the date and time of dialing this circuit |
| Stop time | the date and time of hanging up this circuit |
| Online time | the time this circuit was online |
| Billed time | the time for which the provider will charge you (depends on the timing) |
| Costs | the costs the provider will charge to your account |
| Bandwidth | the bandwidth used, separated into ``in'' and ``out''
(``in'' coming first), presented as two unsigned integer numbers
for which the following applies: Bandwidth =
4GiB * <first number> + <second number> |
| Device | the device used for communication |
| Invoice pulse | the invoice pulse used by the provider for charging (taken from the circuit configuration) |
| Call charge | the fee charged per invoice pulse (taken from the circuit configuration) |
The costs are denoted in Euro. These values are only meaningful if you correctly define the corresponding circuit variables ISDN_CIRC_x_TIMES.
If the imond log is activated, this variable can be used to choose an alternative log directory instead of the default /var/log, e.g. /boot. This is useful in order to make the log persistent on the boot medium. However, this requires the boot medium to be mounted read/write.
The default value is 'auto' which lets the fli4l router to determine the storage location automatically. Depending on further configuration, the storage path is /boot/persistent/base or some other path determined by the FLI4L_UUID variable. If neither FLI4L_UUID is set nor /boot is mounted read/write, the log file can be found under /var/run.
These variables make certain imond commands available in user mode (enabling/disabling the ISDN interface, dialing/hanging up, changing the default route, rebooting the router).
Default settings:
IMOND_ENABLE='yes'
IMOND_DIAL='yes'
IMOND_ROUTE='yes'
IMOND_REBOOT='yes'
All other features of imond's Client-Server interface are described in a separate chapter.