A. Searching for errors

The first thing which may be helpful for search for errors is the console output of your FLI4L router. These messages will often be written too fast to the console; and thatīs too fast for a human being to read! Tip: use page-up and page-down keys to scroll screen contents/outputs.

proc files may be useful for search for errors, too. The command:

cat /proc/interrupts

for example will display interrupts used by drivers - not those which are really used by the hardware!

More interesting files in directory /proc are devices, dma, ioports, kmsg, meminfo, modules, uptime, version and pci (if the router has a PCI bus).

In most cases there will exist a connection problem in ipppd, especially during authentification. If that is so, the following variables may be helpful:

OPT_SYSLOGD='yes'

bzw.

ISDN_CIRC_x_DEBUG='yes' (see package ISDN)

in config.txt weiter.

Errors concerning the ISDN adaptor: See error code in file isdn-cause.txt (see package ISDN).

[ top ]