Mainpage
Searchform
History
Versions
Categories
Contents
Deutsch
This guide is targeted at all those who want to connect a stand-alone workstation via ISDN to a provider.
Especially if you run a local network you have to pay attention to certain differences from this guide, e.g. how the default route must be set in this case. It is then recommended to ignore the local network first and to adapt the corresponding files manually later on.
Currently supported cards :
HiSax-driver 2.1
/etc/rc.config
).
There are historical reasons for this, the driver was called teles
in the beginning. Only teles cards were supported by it. The new improved driver
is called HiSax
and supports almost all Siemens based ISDN cards
(ISAC_S 2085/2086/2186 HSCX SAB 82525)
ICN-driver
B1-driver
Cards that are known to be unsupported :
The necessary drivers (-> modules) are bound dynamically to the kernel when needed (and
only then). Make sure that the modules isdn
and hisax
are available
(package kernmod
) or compile and install them. For sync-PPP the module
slhc
is needed in addition.
Don't compile the driver directly into the kernel but use modules ! This way you can avoid some adjustments of the scripts and you can work much more flexible. For example it is not necessary to reboot the system in order to access the card.
First there is the wellknown PPP protocol (however in the synchronous version -- syncPPP).
A special daemon (ipppd) is included for it in the i4l
package.
Then there is rawip/HDLC (a low level protocol) which uses many of the features of ISDN (data security). Thus it has very little overhead.
Which one you should use depends on your provider. Normally only syncPPP is offered.
Nevertheless there are providers (e.g. in Austria) that also offer asynchronous PPP via ISDN. Please see the article about asynchronous PPP via ISDN in the support-db .
If you can choose, rawip/HDLC is the simpler protocol and is recommended IMHO. A list of features :
init 2
, see below), a connection to the partner can be established
any time by normal activity such as telnet
, WWW
, ftp
, etc .
Only then a dialing connecion is established, which takes approximately 2-3 seconds. This makes it possible
for other users than root
to start a connection. The variable I4L_IDLETIME
specifies,
after how many seconds of inactivity the connection shut be hung up. One can comfortably stay logged in,
programs won't be interrupted. As soon as a button is pressed one will be online again. However never stay
logged in for longer periods of time since then a connection might be established by the opposite side.
Attention : Control your configuration and check whether the connection is hung up and when connections are being established. One can easily stay online for days without recognizing it. After all no dialing tone can be heard as was the case with the good old modem. (However this didn't happen to us for a long time ...)
Hints for the selection of IRQs :
Check with the command cat /proc/interrupts
, which IRQs are available and
which are already in use. The latter are represented by the first column.
Often the delivered DOS/Win program with the call-back test is a reliable test, but IRQ 12 and 15 are not possible with a lot of mainboards (586, PCI, 2. IDE-adapter).
isapnp
two programs are included that carry out the configuration
of the cards, before the card can be accessed by the module. In short you have
to do the following :
pnpdump
, your PnP devices should be identified.
pnpdump > /etc/isapnp.conf
/etc/isapnp.conf
. There is a section for every card. Only the ISDN card
is of interest here. A couple of different hardware configurations is proposed here.
Choose one and remove the comment signs in front of the necessary lines.
isapnp /etc/isapnp.confThe output of this command will show you whether it worked or not.
/etc/isapnp.conf
exists, the
configuration is done automatically at boot time.
Further information about isapnp
is available at
file://localhost/usr/doc/packages/isapnp/README.SuSE
Active cards need a firmware (i.e. the software that is used by the card to run the S0 bus). This firmware is downloaded onto the card by the operating system.
For the above mentioned cards the necessary firmware files are contained
in the package i4lfirm
(series n
, courtesy
Thinking Objects and AVM) and will be installed in /usr/lib/isdn
.
The Init script will download this firmware automatically onto the card
(according to the statements in /etc/rc.config
).
Set the variables with the prefix I4L_ICN_
(or
I4L_USE_B1_
and I4L_B1_
) according to the comments.
Then start /sbin/init.d/i4l_hardware start
(or change the runlevel)
just like with the Hisax driver and monitor /var/log/messages
.
After the hardware driver is loaded (HiSax, icn, b1-capi) isdn4linux will always behave the same.
Exception :
Active cards run the S0 bus autonomously so the information isn't available to isdnlog.
There are plans and ongoing work for an interface to isdnlog for the B1 driver.
/sbin/init.d/i4l stop /sbin/init.d/i4l_hardware stopA sudden hang up in conjunction with rawip can be achieved with
/sbin/isdnctrl hangup isdn0or in conjunction with PPP with
/sbin/isdnctrl hangup ippp0
So how do I configure the network (ifconfig) if the IP number is not known yet ?
The real IP number will be registered by ipppd
as soon as the connection is established
succesfully.
Either enter 192.168.0.1
for the local IP number or a number out of the range
that will be assigned by the server. You can choose any desired value for the server's IP number, though.
Don't use 0.0.0.0
!
If you have fixed IP numbers you must of course enter these (known) numbers.
The following excerpts define a syncPPP connection to Eunet (Nürnberg)
with dynamical assignment of IP numbers in the subnet 193.102.150.0
,
gateway 193.102.150.13
and the nameserver 192.76.144.66
.
/etc/rc.config
:
/etc/route.conf
:
/etc/ppp/options.ippp0
(or ippp1
etc.) the ipppd
is being started with the command line
/sbin/ipppd file /etc/ppp/options.ippp0otherwise only with the net device. This way you can store one separate configuration per device.
Matthias Mohr (SysDesign@T-Online.DE) reports, that in /etc/ppp/options
additionally the following options must be set :
With the clients a PAP authentication is performed. The option
dns-addr
is only necessary for MS clients. This way the nameserver
is reported to them (you have to adapt this).
When the keyword login
isn't used, the file
/etc/ppp/pap-secrets
will be read.
Meanwhile the Hisax driver is officially part of the kernel (since 2.0.31).
However there is a separate patch available at ftp://ftp.franken.de/pub/isdn4linux/HiSax. An up to date version can also be found at ftp://ftp.suse.com/pub/isdn4linux
On S.u.S.E.-Linux 5.1 there are two different packages of kernel sources :
linux
lx-suse
.
It is strongly recommended to use lx-suse
since the whole distributions fine tuning assumes its existance.
The following parameters are relevant, at least these should be set. Besides the Hisax driver also the other drivers can be generated as modules.
Hint : At least one ISDN protocol (EURO/DSS1 or german 1TR6) must be selected !
If you use the Hisax driver you can of course leave out the unused card types as well as the unnecessary ISDN protocol.
Compile and install the kernel as usual and don't forget the modules :
make modules make modules_install
Once again : Life is easier with modules and only this variant is tested.
However if you really need it the other way round :
Set the above mentioned parameters to Y
instead of M
.
All parameters for the card must be defined when compiling the kernel or they must be passed as parameters to the kernel at boot-up.
Some values in /etc/rc.config
must be set in a different way, see
the comments in that file.
The rest of the procedure stays the same. Please make sure that your card
is recogniced at boot time, see /var/log/boot.msg
.
imon
.
imon
, but will show the status only once.
Start it with isdnmon
select
command of wishx
is used, thus only minimal CPU time is
consomed.
Start it with isdnmonp
xload
. It is always shown the throughput over the ISDN line as
well as the number. It is also easy to see whether you're online or not.
/etc/isdnlog/isdnlog.conf
,
so the caller can be listed by name.isdnrep
or isdnrep -a
/var/log/isdn.log
which is written by isdnlog
.
Check whether isdnlog
is really running. If not, /etc/isdn/isdn.conf
may be wrong.
/usr/X11R6/lib/X11/app-defaults/XOsview
:
xosview*network: 8000This way
xosway
will show full load at 100%.ipfwadm
must be installed and the kernel
must support IP accounting (CONFIG_IP_ACCT=y
).
isdnlog
:
Even if you don't have ISDN but use an analog modem connected to a
telecommunication system, you can see the callers phone number
before you answer. This data is stord by isdnlog
in
/var/log/messages
. Run tail -f /var/log/messages
on the console or in an xterm (which is recommended anyway).
/var/log/isdncalls
, /var/log/isdn.log
/usr/doc/packages/i4l
i4l_s
As a device use /dev/ttyI0
(or ttyI1 ... ttyI64) instead of
/dev/modem
. Use ATZ&E123
for the initialization string,
where 123 is your own MSN (i.e. phone number).
Two protocols can be used : HDLC and X.75 . The default is X.75 . Please inform yourself what the opposite side expects since otherwise this may leed to confusion there (I believe that the Hisax driver does it right now). The protocol can be changed with
See also /usr/src/linux/Documentation/isdn/README
.
Tip :Set the variable I4L_IPROFD="yes"
in
/etc/rc.config
. This daemon stores via AT&W0
the current configuration
in /etc/isdnlog/modemsettings
and will restore it at the next start-up automatically.
mgetty
:/usr/etc/mgetty+sendfax/megtty.config
and enter a device
ttyI0
(or some other device) :
Enter into /etc/inittab
:
mo:23:respawn:/usr/sbin/mgetty -s 38400 ttyI0Activate the changes in
inittab
with the command
init q
, i.e. mgetty should run now. In
/tmp/log_mg.ttyI0
you will see the protocol.
As is described above you can now call yourself. This is somehow senseless and costs money but it is a good test.
/etc/rc.config
. All those that are not
defined there will be refused (thanks god).
Please see http://www.suse.de/Support/sdb/isdn_charge.html.
It is possible to use the rawip/HDLC protocol instead of PPP in conjunction with a Cisco.
However you have to choose cisco-h
for the level-2 protocol instead of hdlc
then.
Create the file /etc/rc.config
manually and enter the values as is described above. This file is
the central configuration file for all init scripts in the S.u.S.E. system .
Advantage : Parameters (phone numbers, IP numbers, etc.) and universal programs are separated
from each other, you only have to backup this single file.
Hint about the used programs : You need
Currently used programs :
i4l
package directly
from the net, package : i4l.tgz
,
ftp://ftp.gwdg.de/pub/linux/install/suse/.
The used init scripts can be found on our web server under http://www.suse.de/Support/sdb/isdn_netscripts.html
See also:
Keywords: ISDN, HOWTO, FRITZ, HISAX, PPP, HDLC, RAWIP, MGETTY, EUNET
Categories:
Documentation
Feedback welcome: Send Mail to kfr@suse.de (Please give the following subject: SDB-isdn
)
Mainpage
Searchform
History
Versions
Categories
Contents
Deutsch