Koozali.org: home of the SME Server

dialup with isdn

Ewald

dialup with isdn
« on: September 03, 2002, 12:56:49 AM »
Helo!

I want to make a dialup connection with an ISDN-Card. When i try to use an internal AVM Fritz! PCI i get the messages

....
Calling site 0.0.0.0
modprobe: modprobe: Can't locate module char-major-45
diald[997]: connector: /dev/isdninfo: No such device
last message repeated 5 times
diald[997]: Connect script failed.
diald[997]: Delaying 10 seconds before clear to dial.
console: Response to Internet test was: Can't connect to servertest.e-smith.....
diald[997]: Calling site 0.0.0.0
diald[997]: connector: /dev/isdninfo: No such device
.....

When i tra to use an external AVM Fritz!X connected to Com1 (or Com2) i get the messages

...Calling site 0.0.0.0
chat[1570]: abort on (BUSY)
chat[1570]: abort on (ERROR)
chat[1570]: abort on (NO CARRIER)
chat[1570]: abort on (NO DIALTONE)
chat[1570]: abort on (Login incorrect)
chat[1570]: report (CONNECT)
chat[1570]: send (ATZ^M)
chat[1570]: expect (OK)
chat[1570]: alarm
chat[1570]: Failed
diald[856]: Connect script failed.
diald[856]: Delaying 10 seconds before clear to dial.
diald[856]: Calling site 0.0.0.0
...

I inserted the internal card after installing the Server. Who can tell me what i made wrong?

Thanks for all answers, Ewald

Kees Blokland

Re: dialup with isdn
« Reply #1 on: September 03, 2002, 01:19:15 AM »
You write:
>I inserted the internal card after installing the Server. Who can tell me what i made wrong?

I would gues the problem is exactly that, your sme system does not know about your card.Do you see something that looks like this in your logfiles?
(straigth after power up.)

Aug  5 20:37:33 bigbox kernel: ISDN subsystem Rev:
1.114.6.7/1.94/1.140.6.3/1.85.6.2/1.21/1.5.6.2 loaded
Aug  5 20:37:34 bigbox kernel: HiSax: Linux Driver for passive ISDN cards
Aug  5 20:37:34 bigbox kernel: HiSax: Version 3.5 (module)
Aug  5 20:37:34 bigbox kernel: HiSax: Layer1 Revision 2.41.6.1
Aug  5 20:37:34 bigbox kernel: HiSax: Layer2 Revision 2.25
Aug  5 20:37:34 bigbox kernel: HiSax: TeiMgr Revision 2.17
Aug  5 20:37:34 bigbox kernel: HiSax: Layer3 Revision 2.17.6.1
Aug  5 20:37:34 bigbox kernel: HiSax: LinkLayer Revision 2.51
Aug  5 20:37:34 bigbox kernel: HiSax: Approval certification failed because
of
Aug  5 20:37:34 bigbox kernel: HiSax: unauthorized source code changes
Aug  5 20:37:34 bigbox kernel: HiSax: Total 1 card defined
Aug  5 20:37:34 bigbox kernel: HiSax: Card 1 Protocol EDSS1 Id=HiSax (0)
Aug  5 20:37:34 bigbox kernel: HiSax: Elsa driver Rev. 2.26.6.2
Aug  5 20:37:34 bigbox kernel: Elsa: Microlink PCI defined at 0xb800/0xd000
IRQ 5
Aug  5 20:37:34 bigbox kernel: Elsa: IPAC version 2
Aug  5 20:37:34 bigbox kernel: Elsa PCI: IRQ 5 count 0
Aug  5 20:37:34 bigbox kernel: Elsa PCI: IRQ 5 count 3
Aug  5 20:37:34 bigbox kernel: HiSax: DSS1 Rev. 2.30
Aug  5 20:37:34 bigbox kernel: HiSax: 2 channels added
Aug  5 20:37:34 bigbox kernel: HiSax: MAX_WAITING_CALLS added

Ewald

Re: dialup with isdn
« Reply #2 on: September 03, 2002, 10:09:21 AM »
OK, i will try to make a new install.

And whats about the external card? It is connected correct to a isdn plug. Should i use a speciall modem-init script?

Thanx Ewald

Ewald

Re: dialup with isdn
« Reply #3 on: September 03, 2002, 02:48:51 PM »
OK, now i know that the Fritz!x is not a normal external modem. So i try it with an external USR Sportster 28800. And - Surprise - i gat an error:

Who can help?

Delaying 10 seconds before clear to dial.
Sep  3 12:12:17 zilla diald[867]: Calling site 0.0.0.0
Sep  3 12:12:18 zilla chat[2236]: abort on (BUSY)
Sep  3 12:12:18 zilla chat[2236]: abort on (ERROR)
Sep  3 12:12:18 zilla chat[2236]: abort on (NO CARRIER)
Sep  3 12:12:18 zilla chat[2236]: abort on (NO DIALTONE)
Sep  3 12:12:18 zilla chat[2236]: abort on (Invalid Login)
Sep  3 12:12:18 zilla chat[2236]: abort on (Login incorrect)
Sep  3 12:12:18 zilla chat[2236]: report (CONNECT)
Sep  3 12:12:18 zilla chat[2236]: send (ATZ^M)
Sep  3 12:12:18 zilla chat[2236]: expect (OK)
Sep  3 12:12:18 zilla chat[2236]: ATZ^M^M
Sep  3 12:12:18 zilla chat[2236]: OK
Sep  3 12:12:18 zilla chat[2236]:  -- got it
Sep  3 12:12:18 zilla chat[2236]: send (ATL0M0^M)
Sep  3 12:12:19 zilla chat[2236]: expect (OK)
Sep  3 12:12:19 zilla chat[2236]: ^M
Sep  3 12:12:19 zilla chat[2236]: ATL0M0^M^M
Sep  3 12:12:19 zilla chat[2236]: OK
Sep  3 12:12:19 zilla chat[2236]:  -- got it
Sep  3 12:12:19 zilla chat[2236]: send (ATD019088333^M)
Sep  3 12:12:19 zilla chat[2236]: expect (CONNECT)
Sep  3 12:12:19 zilla chat[2236]: ^M
Sep  3 12:12:50 zilla chat[2236]: ATD019088333^M^M
Sep  3 12:12:50 zilla chat[2236]: CONNECT
Sep  3 12:12:50 zilla chat[2236]:  -- got it
Sep  3 12:12:50 zilla diald[867]: connector: chat:  Sep 03 12:12:50 CONNECT 28800/ARQ
Sep  3 12:12:50 zilla diald[867]: Connected to site 0.0.0.0
Sep  3 12:12:50 zilla diald[867]: Running pppd (pid = 2251).
Sep  3 12:12:50 zilla diald[2251]: Running pppd: /usr/sbin/pppd -defaultroute -detach modem crtscts mtu 1500 mru 1500 name loginname@uta1002.at noauth noipdefault ipparam diald
Sep  3 12:12:50 zilla modprobe: modprobe: Can't locate module char-major-108
Sep  3 12:12:50 zilla pppd[2251]: pppd 2.4.0 started by root, uid 0
Sep  3 12:12:50 zilla pppd[2251]: Using interface ppp0
Sep  3 12:12:50 zilla pppd[2251]: Connect: ppp0 <--> /dev/ttyS0
Sep  3 12:13:17 zilla pppd[2251]: Serial line is looped back.
Sep  3 12:13:17 zilla pppd[2251]: Connection terminated.
Sep  3 12:13:17 zilla pppd[2251]: Exit.
Sep  3 12:13:17 zilla diald[867]: stop ppp0: RTNETLINK answers: No such process
Sep  3 12:13:17 zilla kernel: ppp: ppp0 not active
Sep  3 12:13:17 zilla diald[867]: stop ppp0: SIOCSIFFLAGS: No such device or address
Sep  3 12:13:17 zilla diald[867]: Disconnected. Call duration 27 seconds.
Sep  3 12:13:17 zilla diald[867]: IP transmitted 136 bytes and received 0 bytes.
Sep  3 12:13:18 zilla diald[867]: Delaying 10 seconds before clear to dial.

Kees Blokland

Re: dialup with isdn
« Reply #4 on: September 03, 2002, 09:06:36 PM »
>Sep 3 12:12:50 zilla diald[867]: connector: chat: Sep 03 12:12:50 CONNECT 28800/ARQ
>Sep 3 12:12:50 zilla diald[867]: Connected to site 0.0.0.0

you seem to be connected, now switching to ppp.. and there something strange happens.


I did a google and found this:


>/usr/src/linux/Documentation/devices.txt says char-major-108 is ppp, so
>you probably need to add an alias in /etc/conf.modules. probably along
>the lines of:
>       alias char-major-108 ppp
>This may or may not work.

Could you let us know whether or not it did? I agree that it may work or
that it may not.

My first ideas on this problem are

1. I believe that it is more or less specific to Red Hat
2. Red Hat detects a dependency when it tries to run pppd & calls modprobe
to resolve it
3. That dependency is not satisfied (evidence of the missing char-major module)

My understanding is that this occurs when the kernel and the modules
have somehow got out of sync. A good cure is to recompile the kernel
and recompile and re-install the modules. I presume that this is what you
did. I don't know why the second attempt to dial succeeds.

The 108 refers to a number that identifies /dev/ppp with ppp.o;
and the problem might be as simple as your not having the correct version
of ppp.o in the requisite directory. You will find more details in the
guide for writing Linux Device Drivers.

.

I don't have a system set up with a modem, so I cannot say if an extra alias is created .. (not without digging into the code.) but given the fact that 5.x has been chewed over by so many people, I would not expect a problem.

just a random thought before dinner ..