Technical data

8. Documentation for Developers
Important: Since no separate process is created for these scripts, they may not invoke
“exit” as well!
Hint: If a script wants to check for ip-up scripts being executed the variable ip_up_events
may be sourced from rc400 and up. If it is set to “yes” dialup-connections exist and ip-up
scripts will be executed. No dialup-connections are configured if it is set to “no” and ip-up
scripts will not get executed. There is an exeception to this rule: If an Ethernet router is
configured without dialup-connections but a default-Route (0.0.0.0/0) exists, ip-up scripts
will get executed only once at the end of the boot process. (And as well the ip-down scripts
on rooter shutdown.)
Variables
Due to the special call concept of the ip-up and ip-down scripts the following variables apply:
real_interface the real interface, ie. ppp0, ippp0, . . .
interface the IMOND interface, ie. pppoe, ippp0, . . .
tty terminal connected, may be empty!
speed connection speed, for ISDN ie. 64000
local own IP address
remote IP address of the Point-To-Point partner
is_default_route specifies if the current ip-up/ip-down is for the interface of
the default route (may be “yes” or “no”)
Default Route
As of version 2.1.0 ip-up/ip-down scripts are executed for all connections, not only for the
interface of the default route. To emulate the old behaviour you have to include the following
in ip-up and ip-down scripts:
# is a default-route-interface going up?
if [ "$is_default_route" = "yes" ]
then
# actions to be taken
fi
Of course, the new behaviour can also be used for specific actions.
8.8. Package “template"’
To illustrate some of the things described before the fli4l distribution provides the package
“template"’. This explains by small examples how:
• a configuration files has to look like (config/template.txt)
• a check files is designed (check/template.txt)
• the extended checking mechanisms are used (check/template.ext)
336