See section msn.
Have a look in section hardware.
If you have a SuSE distribution, and you can not find your card in yast,
then select card generic
and enter the exact parameters in the
special case line, like: type=27 protocol=2
for Fritz!PCI and
Euro ISDN. Get a newer kernel if the desired type is not yet supported.
The new ISDN drivers in 2.0.36 defaults to manual dialmode, not autodial. This is done to prevent unexpected (and unnoticed) dialouts.
To enable autodial for a given interface e.g. ippp0, use
isdnctrl dialmode ippp0 auto
The meaning of the values for dialmode is:
means that you (or the system) cannot make any connection (neither incoming nor outgoing connections are possible). Use this if you want to be sure that no connections will be made.
means that the interface is in auto-dial mode, and will attempt to make a connection whenever a network data packet needs the interface's link. Note that this can cause unexpected dialouts, and lead to a high phone bill! Some daemons or other pc's that use this interface can cause this. Incoming connections are also possible.
(DEFAULT) is a dial mode created to prevent the unexpected dialouts. In this mode, the interface will never make any connections on its own. You must explicitly initiate a connection with:
isdnctrl dial ippp0
huptimeout
may still end the connection
automatically! To ensure that you have to hang up manually, you have to switch
this off:
isdnctrl huptimeout ippp0 0
isdnctrl hangup ippp0
ISDN usage depends on the permissions to the devices /dev/ttyI*
and
/dev/cui*
. You have several choices to selectively allow users to do
ISDN transactions.
/etc/group
, and do:
chgrp isdn /dev/ttyI* /dev/cui* chmod o-rw /dev/ttyI* /dev/cui*
/etc/su1.priv
. Add these lines if they (or similar ones) are not yet
there, to allow users XXXX and YYYY to initiate dialups/hangups:
# log all dialouts in syslog syslog all define PPPUSER XXXX YYYY alias dial /sbin/isdnctrl dial ippp0 alias hangup /sbin/isdnctrl hangup ippp0 ask never allow PPPUSER prefix dial allow PPPUSER prefix hangup
ln -s /usr/bin/su1 /usr/local/bin/dial ln -s /usr/bin/su1 /usr/local/bin/hangup
dial
, and hangup with
hangup
.
For PCI cards Plug and Play works automatically, they don't need any manual configuration if the correct card type is provided. ISA PNP cards will require some manual configuration:
pnpdump > /etc/isapnp.conf
/etc/isapnp.conf
has to be set by
hand. Set the following values:
isapnp /etc/isapnp.conf
modprobe hisax io=4,2,INT,IO0,IO1
kerneld does not work well with the ISDN modules, since the ISDN modules can not store their status, and could miss important messages on the D channel. Newer versions of i4l ensure that they won't be unloaded by kerneld, but you should not try to use kerneld with any version of i4l.
Yes, you can define two different run level for this (under SysVInit) in
/etc/inittab
. One run level includes the ISDN processes, where the
other one does not.
Increase the parameter ISDN_MAX_CHANNELS in
/usr/src/linux/include/linux/isdn.h
and rebuild the isdn stuff. Don't
forget to create the additional devices with makedev.sh (part of isdn4k-utils)
or by hand.
Set up async PPP with a normal pppd on a ttyI* device. Additionally to setting
the msn, you have to initialize the ttyI* device with ATS19=0
for V.110.
The rate should be set to 9600 with AT&R9600
. pppd needs to be
called with noccp
and require-pap
. For a mini-howto see:
http://www.oltom.com/Linux/Docs/GSM%20over%20V.110%20Mini-HOWTO.txt
These are helpful links that are currently available on how to configure isdn4linux:
Please note: the following link list may be outdated, they have not been checked for a long while.
http://www.rosat.mpe-garching.mpg.de/~web/ISDN.html
http://www.lrz-muenchen.de/~ui161ab/www/isdn/
http://www.sfs.nphil.uni-tuebingen.de/~hipp/isdn/
http://www.provi.de/~gvz/chargeint.html
http://www.techfak.uni-kiel.de/~stn/i4l/
http://fb4-1112.uni-muenster.de/pub/ffwd/
http://www.datenhighway.com/isdn4linux.html
ftp://ftp.franken.de/pub/isdn4linux/
ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ
http://www.rosat.mpe-garching.mpg.de/~web/ISDN.html
http://www.lrz-muenchen.de/~ui161ab/www/isdn/
http://www.fzi.de/sim/people/trautw/i4l/index.html
ftp://ftp.hamburg.pop.de/pap/LOCAL/linux/i4l-eft/
The reason is that tcpdump does not always understand the special encapsulations that are possible with isdn4linux, especially syncppp. To change this, you need to patch tcpdump.
Michael Stiller
michael@toyland.ping.de
wrote on 23 Oct 1996:
Tip for ftp:
ftp://ftp.gwdg.de/pub/misc/isdn/linux/isdn4linux-gwdg
There is the patch: "tcpdump-3.0.4-1-isdn.dif.gz"
and the rest is at:
/pub/linux/mirrors/funet/PEOPLE/Linus/net-source/tools/tcpdump-3.0.4-1.tar.gz
You might need to hack some, depending on the name of your ISDN interface (mine is bri0). By default, it recognizes only isdn* and isdnY* as interface names.
Henning Schmiedehausen
henning@pong.iconsult.com
further wrote on
30 Oct 1996:
After finding the patch from Eberhard Moenkeberg at ftp.gwdg.de cannot dump cisco HDLC, I made my own patch for tcpdump-3.0.4 that asks the interface which encapsulation it used and sets itself accordingly. The patch is against a tcpdump-3.0.4-1.tar.gz distribution, for example at
ftp://ftp.funet.fi/pub/Linux/PEOPLE/Linus/tools
This patch recognizes rawIP, ISDN-IP and CISCO-HDLC and can dump these packets.(The patch was attached to the message - it should be easy to find in the mailing list archive - Ed.)
Sascha Ottolski
sascha@alzhimer.isdn.cs.tu-berlin.de
gave the following
tip on 5 Nov 1996:
This is a isdn4k-utils-2.0/tcpdump-3.0.3-isdn.diff ! It work, if one makes some changes: In the file tcpdump-3.0.3-isdn/libpcap-0.0/pcap-linux.c after patching you find the following: else if (strncmp("ppp", device, 3) == 0) Either you name your ppp devices pppX instead of ipppX, or change this line, e.g. else if (strncmp("ippp", device, 4) == 0) ^^^^ ^^ Then tcpdump will also recognize syncPPP. At least it does for me.