Koozali.org: home of the SME Server

Debug ISDN card?

Rick Jones

Debug ISDN card?
« on: December 28, 2002, 02:26:29 PM »
I'm setting up e-smith for the first time, and got everything working with an external modem. I'm now switching over to ISDN using a card that has been working fine in Windows.

The card is  recognised when I run through config and select ISDN, but it won't connect. The log shows nothing but "Calling site 0.0.0.0." every 20 secs., and "Test access" just reports that it can't connect.

It's an Asuscom P-IN100 card, pretty common - config detects it, and reports the name correctly, so I'm assuming no extra drivers need loading. The card wasn't plugged in when I first installed e-smith though - should that matter?

Is there any way to debug what's going on in more detail, or any hidden configs that should be tweaked?

I'm totally stuck - help!

TIA
Rick Jones

guestHH

Re: Debug ISDN card?
« Reply #1 on: December 28, 2002, 04:39:12 PM »
Hi,

calling site 0.0.0.0 sounds okay, it's the default route to the outside world (your provider). What does /var/log/messages tell you?

Kees Blokland

Re: Debug ISDN card?
« Reply #2 on: December 28, 2002, 04:56:11 PM »
>The card is recognised when I run through config and select ISDN, but it won't >connect. The log shows nothing but "Calling site 0.0.0.0." every 20 secs., >and "Test access" just reports that it can't connect.

Which seems to suggest it is happy, and trying to call your ISP..

But to be sure: post the relevant bits from your log file (where it shows the ISDN card is detected etc) and the section where it is calling your isp.

Furthermore, search the forum there are many tips on getting it going!

If in doubt whether your card is recognized properly run 'kudzu' (man kudzu gives you the 'whats_this_then?') Any new hardware will be shown. If it finds anything, just say 'yes' to configure.

good luck

kees

Rick Jones

Re: Debug ISDN card?
« Reply #3 on: December 28, 2002, 05:46:44 PM »
Thanks for the replies. "messages" for card init on boot is:

Dec 28 11:33:39 smithy kernel: CSLIP: code copyright 1989 Regents of the University of California
Dec 28 11:33:39 smithy 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
Dec 28 11:33:39 smithy kernel: HiSax: Linux Driver for passive ISDN cards
Dec 28 11:33:39 smithy kernel: HiSax: Version 3.5 (module)
Dec 28 11:33:39 smithy kernel: HiSax: Layer1 Revision 2.41.6.1
Dec 28 11:33:39 smithy kernel: HiSax: Layer2 Revision 2.25
Dec 28 11:33:39 smithy kernel: HiSax: TeiMgr Revision 2.17
Dec 28 11:33:39 smithy kernel: HiSax: Layer3 Revision 2.17.6.1
Dec 28 11:33:39 smithy kernel: HiSax: LinkLayer Revision 2.51
Dec 28 11:33:39 smithy kernel: HiSax: Approval certification failed because of
Dec 28 11:33:39 smithy kernel: HiSax: unauthorized source code changes
Dec 28 11:33:39 smithy kernel: HiSax: Total 1 card defined
Dec 28 11:33:39 smithy kernel: HiSax: Card 1 Protocol EDSS1 Id=HiSax (0)
Dec 28 11:33:39 smithy kernel: HiSax: HFC-PCI driver Rev. 1.34.6.4
Dec 28 11:33:39 smithy kernel: HiSax: HFC-PCI card manufacturer: Asuscom/Askey card name: 675
Dec 28 11:33:39 smithy kernel: HFC-PCI: defined at mem 0xc48f3000 fifo 0xc2888000(0x2888000) IRQ 11 HZ 100
Dec 28 11:33:39 smithy kernel: HFC_PCI: resetting card
Dec 28 11:33:39 smithy kernel: HFC 2BDS0 PCI: IRQ 11 count 0
Dec 28 11:33:39 smithy kernel: HFC 2BDS0 PCI: IRQ 11 count 34
Dec 28 11:33:39 smithy kernel: HiSax: DSS1 Rev. 2.30
Dec 28 11:33:39 smithy kernel: HiSax: 2 channels added
Dec 28 11:33:39 smithy kernel: HiSax: MAX_WAITING_CALLS added
Dec 28 11:33:40 smithy kernel: PPP: version 2.3.7 (demand dialling)
Dec 28 11:33:40 smithy kernel: PPP line discipline registered.
Dec 28 11:33:40 smithy kernel: PPP BSD Compression module registered
Dec 28 11:33:40 smithy ippp: Configuring ippp interfaces:
Dec 28 11:33:40 smithy ippp:  diald
Dec 28 11:33:41 smithy ipppd[826]: Found 2 devices: ,
Dec 28 11:33:41 smithy ippp:
Dec 28 11:33:41 smithy ipppd[827]: ipppd i2.2.12 (isdn4linux version of pppd by MH) started
Dec 28 11:33:41 smithy ipppd[827]: init_unit: 0
Dec 28 11:33:41 smithy kernel: ippp, open, slot: 0, minor: 0, state: 0000
Dec 28 11:33:41 smithy kernel: ippp_ccp: allocated reset data structure c39e2800
Dec 28 11:33:41 smithy ipppd[827]: Connect[0]: /dev/ippp0, fd: 7
Dec 28 11:33:41 smithy ipppd[827]: init_unit: 1
Dec 28 11:33:41 smithy kernel: ippp, open, slot: 1, minor: 0, state: 0000
Dec 28 11:33:41 smithy kernel: ippp_ccp: allocated reset data structure c3d91000
Dec 28 11:33:41 smithy rc: Starting ippp:  succeeded

which looks pretty much OK to me.

On connecting, it's essentially:

Dec 28 10:32:26 smithy chat[1618]: send (ATZ^M)
Dec 28 10:32:26 smithy chat[1618]: expect (OK)

then

Dec 28 10:33:11 smithy chat[1618]: alarm
Dec 28 10:33:11 smithy chat[1618]: Failed
Dec 28 10:33:11 smithy diald[844]: Connect script failed.

i.e. no response even from ATZ :(

kudzu doesn't report the card, so it looks like device detection is OK.

Any other ideas?

Thanks a lot
Rick Jones

Rick Jones

Re: Debug ISDN card (now working!)
« Reply #4 on: December 28, 2002, 07:56:14 PM »
Just an update - got it going at last

FYI - re-ran the config and got different messages, no "chat" stuff, but got ISDN error E001B. Looks like this was down to a faulty cable - maybe the only original problem :(
Changed the cable and all is well.

Cheers, and HNY
Rick

Kees Blokland

Re: Debug ISDN card (now working!)
« Reply #5 on: December 28, 2002, 08:42:22 PM »
>but got ISDN error E001B

Yep, that means it has no active ISDN wires...

Rick Jones

Re: Debug ISDN card (now working!)
« Reply #6 on: December 28, 2002, 11:16:06 PM »
Kees Blokland wrote:
>
> >but got ISDN error E001B
>
> Yep, that means it has no active ISDN wires...

I read that as one possible cause of that error, so it was a good place to start :)

BUT - still a problem. The throughput to clients is abysmal. Less that 1 kB/sec :(

I've run an FTP to an Internet site direct on the e-smith server, and the throughput is reasonable (5 kB/s - not good, but might have been the remote server, I haven't checked any other servers yet).

But the equivalent retrieval on a client machine is dog slow. When I had e-smith using a modem there was no problem, the throughput was what I'd expect from a directly connected modem. With ISDN it's just horrible. It's only an old machine, P150 64 MB, but it's been used as an ISDN gateway with Windows and performed fine. I'm switching to Linux for better security and up-time, but I didn't expect this kind of performance hit.

I suspect it's a config issue, but I don't know what I should be looking to change.

Any suggestions?

TIA again
Rick Jones