Package ISDN
OPT_ISDN CIRCUITS OPT_TELMOND

In each FLI4L configuration several connections can be defined via ISDN. A maximum of two connections are possible per ISDN adaptor.

Definition of such connections is done per so called circuits. Each connection is done with one circuit.

In the sample file config.txt two of these circuits are defined:

Circuit 1: Dial-out via Internet-By-Call-Provider Planet Interkom, Sync-PPP
Circuit 2: Dial-in/Dial-out to an ISDN-Router (ex.: FLI4L :-) via Raw-IP for example as access way to a companyīs network from anywhere. In my situation this is a Linux box with isdn4linux as "partner".

If the FLI4L router is meant as internet gateway, you will only need one circuit. Exception: You want to use the LC router features of FLI4L. In this case all allowed circuits for different time intervals must be defined; see below.

top

ISDN_CIRCUITS_N

Number of used ISDN circuits. If FLI4L will be used as DSL router without ISDN adaptor, you will have to enter:

ISDN_CIRCUITS_N='0'
    

If the FLI4L router will be used as ISDN gateway to the internet, onecircuit will be enough. Exception: LC routing; see below.

top

ISDN_CIRC_x_NAME

Here you should enter a name for the circuit - max. 15 characters. This name will then be displayed in the imon client imonc.exe instead of the dialed telephone number. Blanks are not allowed!
Example:

ISDN_CIRC_x_NAME='Planet-Interkom'
    
top

ISDN_CIRC_x_USEPEERDNS

This entry will control transfer and (temporary) storage of providerīs name server entries (for duration of this online session) to the local name server ens.
This option only makes any sense when you are using circuits for internet providers.
In the meantime almost every provider supports this kind of transfer.

After having transferred the name server IP addresses, all name servers which were entered into DNS_FORWARDERS, will be deleted from file ens.conf and IP addresses from your provider will be filled into the file ens.conf. After this the local name server will be forced to re-read its configuration. All names which had been resolved up to this time will not be lost/removed from name serverīs cache.

This option offers the opportunity to work with the nearest mane servers, if the provider transmits the correct IP addresses - this will fasten name resolution.

If one of the DNS servers failed, the transmitted DNS server addresses will usually be corrected quite fast by the provider.

But, nevertheless you will have to give - before first connection - a valid name server via DNS_FORWARDERS. Otherwise there will be no correct resolution for the first attempt of access. Additionally the original configuration of the local name server will be restored when the connection is closed!

Default setting: ISDN_CIRC_x_USEPEERDNS='no'

top

ISDN_CIRC_x_TYPE

ISDN_CIRC_x_TYPE contains the type of the x-th connection. The following values are possible/allowed:

'raw'        RAW-IP
'ppp'        Sync-PPP
    

In most cases PPP is used. RAW-IP is a bit more efficient, because there will be no PPP overhead. An authentification is not possible with RAW-IP, but you can define - via variable ISDN_CIRC_x_DIALIN - an access restriction to specific ISDN numbers (keyword: "Clip").

top

ISDN_CIRC_x_BUNDLING

The wide spread MPPP protocol (RFC 1717) is used for channel bundling. This means there will be the following restrictions (which are not elevant in most cases):

The second channel may be switched manually via client imonc or activated automatically via bandwith control; see also the description for: ISDN_CIRC_x_BANDWIDTH.

Default setting: ISDN_CIRC_x_BUNDLING='no'

top

ISDN_CIRC_x_BANDWIDTH

If channel bundling was activated per: ISDN_CIRC_x_BUNDLING='yes' ,you may define - with variable ISDN_CIRC_x_BANDWIDTH - an automatic switching of the second ISDN channel. You will have to enter two numeric parameters:

  1. Threshold in kBytes/second (kbs)
  2. time interval in seconds (nsec)

If threshold kbs will be exceeded by nsec seconds, the control process imond will automatically switch on the second channel. If threshold kbs will be below the (above) given value for nsec seconds, the second channel will automatically de-activated. In this case there will only be the possibility to manually switch on the second channel via client imonc.

Examples:

ISDN_CIRC_1_BANDWIDTH='6144  30'
    

&If transfer rate exceeds a value of 6kBytes/second for 30 seconds, the second channel will be switched on.

ISDN_CIRC_1_BANDWIDTH='0 0'
    

The second channel will be switched on immediately (but max. 10 seconds after establishing the connection) and will stay established until the complete connection will be ended.

ISDN_CIRC_1_BANDWIDTH=''
    

The second ISDN channel can only be switched manually; but nevertheless: ISDN_CIRC_1_BUNDLING must be set to 'yes'.

ISDN_CIRC_1_BANDWIDTH='10000 30'
    

This meant: switch on the second channel after 30 seconds if transfer rate will be in this time interval reaching 10000 kB/sec. This will never happen, since ISDN will only allow transfer rates at about 8 kB/sec. ;-)

If ISDN_CIRC_x_BUNDLING='no', the contents of variable ISDN_CIRC_x_BANDWIDTH are irelevant!

Default setting: ISDN_CIRC_x_BANDWIDTH=''

top

ISDN_CIRC_x_LOCAL ISDN_CIRC_x_REMOTE

In these variables you may store the local and remote IP addresses. When you get dynamic addresses, these values must be *empty*. When connecting these IP addresses will be arranged.

In most cases internet providers will give you dynamic IP addresses. If you use fixed IP addresses, you must enter them here.

top

ISDN_CIRC_x_NETMASK

Defines the netmask on ISDN side. In most cases this would be: 255.255.255.0 (former: Class-C).

top

ISDN_CIRC_x_MTU ISDN_CIRC_x_MRU

With these variables you may set the so called "maximum transmission units" and the "maximum receive units". Values in sample file (1024 and 1524) are default values and should not be changed in normal cases.

top

ISDN_CIRC_x_COMPRESSION

ISDN_CIRC_x_COMPRESSION='yes' will switch on the Van-Jacobson compression or header compression. Not all providers will support this. If you encounter any problems with compression switched on, you should set: ISDN_CIRC_x_COMPRESSION='no' .

Default setting: ISDN_CIRC_x_COMPRESSION='yes'

top

ISDN_COMP_x_FRAMECOMP (EXPERIMENTAL)

This parameter will only be used if the following was set: OPT_LZS='yes' . It arranges frame compression.

The following values are possible:

'no"                    No frame compression
'default"               LZS according RFC1974(std) and BSDCOMP 12
'all"                   Negotiate lzs and bsdcomp
'lzs"                   Negotiate lzs only
'lzsstd                 LZS according RFC1974 Standard Mode ("Sequential Mode")
'lzsext"                LZS according RFC1974 Extended Mode
'bsdcomp"               Negotiate bsdcomp only
    

You will have to try out, which value you will have to use for each provider. As far as we know (for example) T-Online will only work with 'lzsext'. Most other providers should be o.k. with 'default'.

Important: If you want to use LZS compression, you must set: ISDN_CIRC_x_MTU='1500' ! ISDN_CIRC_1_COMPRESSION sshould be set to 'yes' .

Default setting: ISDN_CIRC_x_COMPRESSION='yes'

top

ISDN_CIRC_x_IPX_NETWORK

If IPX is to be routet via ISDN, enter IPX network number here. Otherwise leave variable *empty*.

Analog to IPX configuration enter network number for ipppX device here.

Please notice: the interfaces must use the same network number;, see also: chapter about OPT_IPX.

If IPX shall be used via ISDN, a setting which would make sense is (ex.): ISDN_CIRC_x_IPX_NETWORK='0x0ABCDEF2'

Default setting (no IPX): ISDN_CIRC_x_IPX_NETWORK=' '

top

ISDN_CIRC_x_IPX_NODE

If IPX shall be routed via ISDN, enter IPX address of NODE here. Otherwise leave variable *empty*.

The default setting for the FLI4L router is NODE number 2. The remote partner is still undefined with NODE number 0 and will arranged via ipxcp automatically.

If you want to use IPX via ISDN, a setting that would make sense is: ISDN_CIRC_x_IPX_NODE='2:0'

In the appendix of the documentation you may find an IPX configuration (IPX example).

Default setting (no IPX): ISDN_CIRC_x_IPX_NODE=' '

top

ISDN_CIRC_x_REMOTENAME

This variable usually is relevant only when configuring FLI4L as dial-in router. You may enter the name of the remote host here (not needed).

Default setting: ISDN_CIRC_1_REMOTENAME=' '

top

ISDN_CIRC_x_USER ; ISDN_CIRC_x_PASS

Enter provider date here. In the above mentioned example it the provider "Planet-Interkom".

ISDN_CIRC_x_USER contains the user ID, ISDN_CIRC_x_PASS contains the password.

IMPORTANT:

For an access via T-Online please notice the following:

User name AAAAAAAAAAAATTTTTT#MMMM is built from the 12-character user number, the T-Online number and the user name/counter. After the T-Online number a '#' must be entered, if length of T-Online number is less than 12 characters.

If you sonīt succeed with these settings (in single cases this may depend on Telekomīs nodes), you will have to insert another '#' character between user number and T-Online number.

Otherwise (12-character-T-Online number) you wonīt have to enter '#' characters.

Example:

ISDN_CIRC_1_USER='123456#123'
    

When using Raw-IP circuits, these variables are meaningless.

top

ISDN_CIRC_x_ROUTE

Route or routes for this circuit. Enter '0.0.0.0' (default route) for internet access. To dial in company or university routers you will have to enter the network(s), you really want to reach there; ex.:

'192.168.8.0 192.168.9.0'
    

More than one networks must be separated by blanks.
General syntax: ISDN_IRC_x_ROUTE='network[:netmask] ...', i.e.: additionally to the network route you may enter a netmask - if necessary.

If you want to use LC routing features of FLI4L, you may assign a default route to *several* circuits. The selection of the really used circuit will be done via: ISDN_CIRC_x_TIMES ; see below.

top

ISDN_CIRC_x_DIALOUT ; ISDN_CIRC_x_DIALIN

ISDN_CIRC_x_DIALOUT contains telephone number to be dialed.

If the circuit shall be used for dialing in, the telephine number of the caller will be written in ISDN_CIRC_x_DIALIN - including area code, but *without* leading zero. When you use connections "behind" a telephone machine the may be different; one or two leading zeroes must be entered here.

If you want this circuit for dialing-in of several users, you may enter numbers with separating blanks. Nevertheless it would be better to have defined one circuit per user. Otherwise collisions concerning the IP addresses may occur, if two users want to dial-in at the same time (is possible when using two ISDN channels).

If the caller does not transmit the telephone number, you must enter a '0'. But, be careful: This means, that everybody who does not transmit a telephone number would be able to dial-in. If you want to realize a dial-in independent from the MSN of the caller, you must enter a '*' as value for this variable.

top

ISDN_CIRC_x_CALLBACK

Setting for callback operation; possible values:

'in' :  fli4l will be called and calls back,
'out':  fli4l dials, hangs up and waits for callback,
'off':  no callback
    

Default value: 'off'

top

ISDN_CIRC_x_CBDELAY

This variable contains the delay in seconds to wait when callback is switched on. Depending on the direction of callback, the meaning of this variable slightly differs.

ISDN_CIRC_x_CALLBACK='in':
    

If FLI4L is called and shall call back, ISDN_CIRC_x_CBDELAY contains the waiting time until callback shall be done. A good value would be (ex.): ISDN_CIRC_x_CBDELAY='3'. Depending on the "partner" a smaller value might be working. This may fasten establishing the connection.

ISDN_CIRC_x_CALLBACK='out':
    

In this case ISDN_CIRC_x_CBDELAY will contain the time how long FLI4L shall wait for the "partner" to accept the call. Again ISDN_CIRC_x_CBDELAY='3' would be a good/approved value. I noticed the following: You will have to wait up to three seconds in a long distance call before the other router will "see" the call. For short distance/local calls this value may be smaller. If in doubt: try some values!

If variable ISDN_CIRC_x_CALLBACK is set to 'off' , ISDN_CIRC_x_CBDELAY will be ignored.

top

ISDN_CIRC_x_EAZ

In the example the MSN (here: EAZ) is set to: 81330. YOu should enter your own MSN *without* area code here.

If you use a connection "behind" a telephine connecting machine, you may be successful (in most cases) when setting just the extension number. But: I also read about people who entered a '0' if there were any problems with the machinery :-)

top

ISDN_CIRC_x_DEBUG

If ipppd shall output additional debug information, you will have to set ISDN_CIRC_x_DEBUG to 'yes'. If that is the case, ipppd will write additional information via the syslog interface.

IMPORTANT: To get also an output on the console, variable OPT_SYSLOGD must also be set to 'yes'.

ISDN_CIRC_x_DEBUG will be without any meaning it using Raw-IP circuits.

top

ISDN_CIRC_x_AUTH

If this circuit will also be used for dialing-in and authentification shall be forced from the "incoming partner" via PAP or CHAP, ISDN_CIRC_x_PAP must be set to 'pap' or 'chap' - and *only* then. Otherwise always leave empty !

Reason:
An internet provider you connected to will always deny to send further information :-)

This variable is without any meaning for Raw-IP circuits.

top

ISDN_CIRC_x_HUP_TIMEOUT

ISDN_CIRC_x_HUP_TIMEOUT will control the time interval after which the FLI4L computer shall end the connection to the provider, if there is no traffic on this line. In the example the connection will be ended after 40 seconds of idle time - to save money. When re-accessing the internet, the connection will be re-established within seconds. That may be useful when calling providers who calculate the charging costs on a second base.

During testing you should have a look on automatic dialing/hanging-up of the FLI4L router (either on the console or in imon client for Windows). Thatīs only to avoid a "steady line" because of an errorness configuration of your ISDN connection ;-)

If the value is set to '0', an idle time will not be considered. That means: FLI4L will not disconnect automatically any more. Please be careful with this variable!

I recognized, that - when exiting Netscape on a computer in the local network - there will be a re-connection - even if the last connection was ended (the routerīs connection was offline) ! It looks like Netscape knows the connection to the last called web server and re-opens it when exiting !?...

top

ISDN_CIRC_x_CHARGEINT

Charge-Interval: Hier ist der Zeittakt in Sekunden anzugeben. Dieser wird dann für die Kosten-Berechnung verwendet.

Die meisten Provider rechnen minutengenau ab. In diesem Fall ist der Wert '60' richtig. Compuserve verwendet einen 3-Minuten-Takt (Stand Juni 2000), also ISDN_CIRC_x_CHARGEINT='180'. Bei Providern mit sekundengenauer Abrechnung (z.B. Planet-Interkom) setzt man besser ISDN_CIRC_x_CHARGEINT auf '1'.

Erweiterung für ISDN_CIRC_x_CHARGEINT >= 60 Sekunden:

Wurde ISDN_CIRC_x_HUP_TIMEOUT Sekunden lang kein Traffic bemerkt, wird ca. 2 Sekunden vor Ablauf des Taktes eingehängt. Die vom Provider berechnete Zeit wird also fast komplett ausgenutzt. Ein wirklich tolles Feature von isdn4linux!

Bei sekundengenau abgerechneten Verbindungen hat das natürlich keinen Sinn - daher gilt diese Regelung erst ab Zeittakten von 60 Sekunden.

nach oben

ISDN_CIRC_x_TIMES

This section gives information about times when this circuit shall be activated and at which time it will be a connection at which costs. This will enable you to use different circuits with default routes at different times (least-cost-routing). Daemon imond will control the route assignments.

Syntax of variable:

ISDN_CIRC_x_TIMES='times-1-info [times-2-info] ...'
    

Each field times-?-info consists of four sub-fields - divided by colons (':')

1st field: W1-W2

day of the week interval, ex.: Mo-Fr or Sa-Su, etc.This data may be written in german or english syntax. If you want to enter one single day of the week, this must be done like this: Su-Su.

2nd field: hh-hh

Hours interval; ex.: 09-18 or 18-09. 18-09 is the same as: 18-24 plus 00-09. 00-24 means: the whole day.

3rd field: Charge

Here you may enter (in DM values) costs per minute; ex.: 0.032 for 3.2 Pfennig per minute. These will be calculated, depending on charge time/interval, for real existing costs, which will then be displayed in imon client.

4th field: LC-Default-Route

Content can be: 'Y' or 'N'. Meanings are:

N: The given time interval is only used for costs calculation; it will not be used for automatic LC routing.

Y: The given time interval will be used as default route for LC routing. Important: In this case there MUST be: ISDN_CIRC_x_ROUTE='0.0.0.0'
N:

Example:

ISDN_CIRC_1_TIMES='Mo-Fr:09-18:0.049:N Mo-Fr:18-09:0.044:Y Sa-Su:00-24:0.044:Y'
ISDN_CIRC_2_TIMES='Mo-Fr:09-18:0.019:Y'
    

Bedeutung:

Circuit 1 (provider: Planet-Interkom) shall be used on working days in the evening and during the complete weekend. During the day on working days the circuit 2 shall be used (provider: Compuserve).

Important:

If the time intervals of all LC default route circuits ("Y") summed up do not contain the complete week (time), there will be no default route for the remaining time. Surfing the internet is FORBIDDEN during these times!

Example:

ISDN_CIRC_1_TIMES='Sa-Su:00-24:0.044:Y'
ISDN_CIRC_2_TIMES='Mo-Fr:09-18:0.019:Y'

Working days/times from 18-09 h are missing in this example. During these times there will be no route to the internet: Surfing forbidden :-)))

Another simple example:

ISDN_CIRC_1_TIMES='Mo-Su:00-24:0.0:Y'

for those who use a flatrate.

One last remark to LC routing:

Holidays will be treated like Sundays.

On page/site http://www.heise.de/itarif/ you may find technical data of lots of Internet-by-call providers; i.e.: telephone numbers, user IDs, passwords, DNS servers, etc.

top
» To documentation «