Mainpage
Searchform
History
Versions
Categories
Contents
Deutsch
SuSE Linux: Version 5.1
Kernel: Version 2.0.31
HiSax: Version 2.1
isdn4k-utils: Version 2.1b1
It is not the intention of this guide to describe every special feature. An attempt is made to describe approximately 94 % of all possible cases and to do this in a straight forward way.
For more information read the S.u.S.E. ISDN howto.
As a test a connection to the S.u.S.E. ISDN server is described. As soon as this works, you can for sure easily modify the setup for the connection to your Internet Service Provider (ISP) with the help of this example. You can avoid a large number of possible errors this way.
You can find a description in the handbook, how most of the settings can be entered directly using YaST.
/home/suse/README
on the server.
You get no access to the Internet on this server, since that would be too expensive for us ;-)
isdnlog
Before you make changes to the configuration files, make sure the system is in runlevel 1 (i.e. no network):
init 1Change into the runlevel 2 in order to test or start the configuration (i.e. with network):
init 2If you have a local network, deactivate it by setting
NETCONFIG=""in
/etc/rc.config
.
Important:
All messages of and about ISDN are stored in the file /var/log/messages
.
In an xterm or on the console say
tail -f /var/log/messagesThis way you can always check whether your actions were succesful.
lx-suse
.
A couple of necessary patches are already contained therein (e.g. the HiSax driver).
kernmod
. The package kernmod
contains all necessary
modules that are needed for ISDN.
i4l :
All scripts and tools required for ISDN.
i4ldoc :
Further documentation on ISDN, e.g. the
ISDN-FAQ. (See /usr/doc/packages/i4ldoc
).
Loading of modules is done through the script
/sbin/init.d/i4l_hardware
. It is executed automatically
at boot-time. The hardware specification must be entered by you into
the S.u.S.E. configuration file /etc/rc.config
.
Starting with S.u.S.E.-Linux 5.0 you can also do this with YaST.
Please see the corresponding section in the handbook for further information.
In /etc/rc.config
change the following :
i4l
and i4l_hardware
) are executed at all.
Set
# # start i4l? ("yes" or "no") # I4L_START="yes"
I4L_PROTOCOL=1
I4L_PROTOCOL=2
I4L_TELES_TYPE=1 I4L_TELES_IRQ=5 I4L_MEMBASE=0xd0000 I4L_TELES_PORT=0xd80
I4L_TELES_TYPE=2 I4L_TELES_IRQ=5 I4L_MEMBASE=0xd0000
I4L_TELES_TYPE=3 I4L_TELES_IRQ=12 I4L_TELES_PORT=0xd80The value
180
on the Teles card means 0xd80
, really !
I4L_TELES_TYPE=5 I4L_TELES_IRQ=5 I4L_TELES_PORT=0x300
I4L_TELES_TYPE=6If the autoprobing doesn't work you have to set additionally :
I4L_TELES_PORT=0x300
I4L_TELES_TYPE=7 I4L_TELES_IRQ= # (from isapnp setup) I4L_TELES_PORT= # (from isapnp setup)
I4L_TELES_TYPE=8 I4L_TELES_IRQ= # (from pcmcia setup) I4L_TELES_PORT= # (from pcmcia setup)
I4L_TELES_TYPE=9 I4L_TELES_IRQ=? I4L_TELES_PORT=?
isdnlog
isdnlog
should be configured. It is the job of this program to monitor all
activity on the S0 bus.
Adapt the following files according to your needs :
/etc/isdn/isdn.conf
:
The first entry specifies the country where isdn4linux is being used. For germany set the following :
[GLOBAL] COUNTRYPREFIX = + COUNTRYCODE = 49 AREAPREFIX = 0Also the
AREACODE
(the dialling code) is specified without leading 0
in the GLOBAL
-section. If your dialling code is for example 0911
, enter
AREACODE = 911In germany this is the only part that must be adapted.
/etc/isdn/callerid.conf
Here you can enter all known phone numbers. Then names will be listed instead of telephone
numbers in /var/log/messages
and by isdnrep
.
Example : Your own phone number is 4711
, the one of your provider
is 4712
:
[MSN] NUMBER = 4711 ALIAS = me ZONE = 1 [MSN] NUMBER = 4712 ALIAS = provider ZONE = 1
/etc/isdn/isdnlog.isdnctrl0.options
Here you can enter options for isdnlog
(see the comments there).
Normally this is not necessary.
init 2Check
/var/log/messages
whether the HiSax module was loaded succesfully.
If not, try out other hardware parameters.
If the module was loaded you can access the ISDN card. isdnlog
will show you
in /var/log/messages
whether you're currently calling or being called.
Continue with one of the topics
Start an arbitrary terminal program, e.g. minicom
.
Use the device /dev/ttyI0
.
Start it with minicom -s
.
At Serial port setup
enter /dev/ttyI0
for the device.
Press Exit
. You will get an error message because it is tried to
configure a serial modem.
Enter the commands
ATZ ATS14=0&E123Where
123
is one of your MSNs . You should get an OK
now.
Dial with
atd09113247114You get a message
CONNECT 64000/X.75
as well as a login prompt.
login with
README
:
less README
init 1The routes are defined in
/etc/route.conf
.
These specify on which way a maschine (IP number)
can be reached.
Set a hostroute and also the default route to the ISDN server :
# syncPPP Client 192.168.0.1 0.0.0.0 255.255.255.255 ippp0 default 192.168.0.1
/etc/rc.config
:
# syncPPP Client -> S.u.S.E. ISDN-Server NETDEV_2=ippp0 IPADDR_2="192.168.0.99" IFCONFIG_2="192.168.0.99 pointopoint 192.168.0.1" I4L_IDLETIME_2=60 I4L_REMOTE_OUT_2=09113206726 I4L_REMOTE_IN_2= I4L_DEBUG_2=4 I4L_L2_2="hdlc" I4L_L3_2="trans" I4L_ENCAP_2="syncppp" I4L_SECURE_2="on"Also set your own MSN. if you have for example the telephone number
012/123
, enter :
I4L_LOCALMSN_2=123Define, which net device should be configured :
NETCONFIG="_2"Hint: You can do this much more comfortably with YaST.
ipppd
is configured through the following files:
/etc/ppp/ioptions
: General settings.
/etc/ppp/options.ippp0
: Settings for the device ippp0 .
/etc/ppp/pap-secrets
: Password file for PAP.
/etc/ppp/ioptions.YaST
is used as a template for options.ippp0
.
init 2The configuration is complete now; You can now establish a connection by
telnet 192.168.0.1You get a login prompt. Login with
README
:
less READMETake a look at
/var/log/messages
in order to check, what
happens in your system.
/etc/route.conf
. It is specified this
way on wich way a machine (IP number) can be reached.
Set a hostroute and also a default route to the ISDN server :
192.168.0.2 0.0.0.0 255.255.255.255 isdn0 default 192.168.0.2
/etc/rc.config
: (you can
simply copy these lines at the end of the file. This way the
values above are overridden.)
# rawip Client IPADDR_3=192.168.0.98 NETDEV_3=isdn0 IFCONFIG_3="192.168.0.98 pointopoint 192.168.0.2" I4L_IDLETIME_3=60 I4L_DIALMAX_3=5 I4L_REMOTE_OUT_3="09113206728" I4L_REMOTE_IN_3="" I4L_LOCALMSN_3="3206726" I4L_DEBUG_3=4 I4L_L2_3="hdlc" I4L_L3_3="trans" I4L_ENCAP_3="rawip" I4L_SECURE_3="on"Define, which net devices should be configured:
NETCONFIG="_3"Hint : This can be done much more comfortably using YaST.
init 2The configuration is completed now. You can now establish a connection by
telnet 192.168.0.2You get a login prompt. Login with
README
:
less READMECheck the file
/var/log/messages
in order to check, what
happens in your system.
90 % of all failures on the S.u.S.E. ISDN test machine are caused by wrong user name / password. Please check this data (or the YaST mask) thoroughly.
Now simply try to change the phone number, the IP number and the user data and call your provider with this configuration.
Try to establish a connection using isdnctrl dial ippp0
(or some other
device) and monitor /var/log/messages
whether a connection
could really be established.
imon
or by monitoring /var/log/messages
.
0911 3247114
0911 3206726
0911 3206728
192.168.0.1
192.168.0.99
192.168.0.2
192.168.0.98
See also:
Keywords: ISDN, QUICK, ISDNSERVER, TEST MACHINE, SMALL
Categories:
Documentation
Feedback welcome: Send Mail to skfr@suse.de (Please give the following subject: SDB-isdnquick
)
Mainpage
Searchform
History
Versions
Categories
Contents
Deutsch