Topic: Help Debugging ISDN Connection

[Graham]

Hi All,

Could anyone shed any light on the below ?

I now have nice Asus ISDN TA with pretty lights that actually
talks to my SME 5.5 - I get Link, Carrier Detect, Send Data
and Receieve Data.

What I dont get is any returnerd IP.

I ran ping on an external IP number. 100's of packets get sent
but non returned.

I have pasted some stuff below :-

Any pointer in the right direction woudl be very very much
appreciated !

Thanks !

File: accounting.log    Col 0              57641 bytes                                   100%
Tue Nov 19 19:15:50 2002 GMT: Calling site 0.0.0.0.
Tue Nov 19 19:15:55 2002 GMT: Connected to site 0.0.0.0.
Tue Nov 19 19:16:17 2002 GMT: Disconnected. Call duration 22 seconds.
      IP transmitted 2268 bytes and received 0 bytes.


File: messages          Col 0              1389248 bytes                                      100%
Nov 19 19:18:27 server chat[2115]: expect (OK)
Nov 19 19:18:27 server chat[2115]: ^M
Nov 19 19:18:27 server chat[2115]: ATL0M0^M^M
Nov 19 19:18:27 server chat[2115]: OK
Nov 19 19:18:27 server chat[2115]:  -- got it
Nov 19 19:18:27 server chat[2115]: send (ATD9,,,08456609282^M)
Nov 19 19:18:27 server chat[2115]: expect (CONNECT)
Nov 19 19:18:27 server chat[2115]: ^M
Nov 19 19:18:30 server chat[2115]: ATD9,,,08456609282^M^M
Nov 19 19:18:30 server chat[2115]: CONNECT
Nov 19 19:18:30 server chat[2115]:  -- got it
Nov 19 19:18:30 server diald[827]: connector: chat:  Nov 19 19:18:30 CONNECT 64000/HDLC
Nov 19 19:18:30 server diald[827]: Connected to site 0.0.0.0
Nov 19 19:18:30 server diald[827]: Running pppd (pid = 2116).
Nov 19 19:18:30 server diald[2116]: Running pppd: /usr/sbin/pppd -defaultroute -detach modem crtsc
ts mtu 1500 mru 1500 name uk2 noauth noipdefault ipparam diald
Nov 19 19:18:30 server modprobe: modprobe: Can't locate module char-major-108
Nov 19 19:18:30 server pppd[2116]: pppd 2.4.0 started by root, uid 0
Nov 19 19:18:30 server pppd[2116]: Using interface ppp0
Nov 19 19:18:30 server pppd[2116]: Connect: ppp0 <--> /dev/ttyS0
Nov 19 19:18:53 server pppd[2116]: Hangup (SIGHUP)
Nov 19 19:18:53 server pppd[2116]: Modem hangup
Nov 19 19:18:53 server pppd[2116]: Connection terminated.
Nov 19 19:18:53 server pppd[2116]: Exit.
Nov 19 19:18:53 server diald[827]: stop ppp0: RTNETLINK answers: No such process
Nov 19 19:18:53 server last message repeated 2 times
Nov 19 19:18:53 server diald[827]: stop ppp0: SIOCSIFFLAGS: No such device or address
Nov 19 19:18:53 server diald[827]: Disconnected. Call duration 23 seconds.
Nov 19 19:18:53 server diald[827]: IP transmitted 0 bytes and received 0 bytes.
Nov 19 19:18:54 server diald[827]: Delaying 10 seconds before clear to dial.


1Help   2UnWrap 3Quit   4Hex    5Line   6RxSrch 7Search 8Raw    9Unform 10Quit

[Graham]

Looking at other peoples logs on different subjects I see that the line :-

Nov 19 19:18:30 server diald[827]: Connected to site 0.0.0.0

actually contains the IP of the ISP and not 0.0.0.0 ??

[guestHH]

Hi,

There's an ISDN guru around here somwhere....

Call upon Kees Blokland and say the magic word

Regards,
guestHH

[Kees Blokland]

Hi Graham.

A thought just occured to me (but no immediate solution)

See if you can find info about the LCP packets (link control packets) that are continuously send back and forth on a 'live' link, and how to make them visible.
If you don't get them, the link is dropped.
There are also ways to increase the verbosity of the logging messages, look for 'kdebug' and related stuff, anything that will let you get more details on the actual packets being sent/received.

Saying that, it might not be so easy, because the LCP packets are possibley on the ISDN wires only, no idea if they would be visible internaly (=serial side) They might be stripped off..

What you describe looks what I had trying to connect a 'real' isdn card..

I'll mail you some stuff off list to have a look at, might be useful.
I've not tried serial-isdn, so I could be barking up the wrong tree..

kees

[Kees Blokland]

If you don't see something in the next 5 minutes, I mistyped your email address, let me know..

kees

[Graham]

Thanks for replies BUT - I know basic Linux - thats all !

Its hard from this level of skill to go further !

This part though got me thinking :-

Nov 19 19:18:30 server modprobe: modprobe: Can't locate module char-major-108

I read somewhere to add an alias to ppp to modules.conf

It got rid of the message but things didnt get any better.

I was wondering something about that.

Isnt it Linux saying "I dont support this!"

What is HDLC and is it supported in the stock kernel with SME 5.5 ?

Thanks a mill !

[Graham]

Got this from Suse help database :-

modprobe: Can't locate module char-major-108

Reason:
The PPP Daemon is capable of supporting generic devices (such as /dev/ppp), however, the current kernel version (in SuSE 6.3) is not. This feature will be available in future kernels. Even though the PPP Daemon complains about not being able to find this device, it still works fine.

----

I guess I was way of the mark with that one !

Thanks for those who mailed me so far . . .

[John Crisp]

Graham,

Edit your modules.conf by adding the following line. I think that you can do it directly as it doesn't get overwritten at boot. Alternatively add a custom template fragment blahg blah. Don't know why you do it, but it's in the forums somewhere   :

alias char-major-108 ppp


Re your link, who is you provider ?

I use Demon here in the UK. To connect to them you have to force the TA to use a PPP connection and not HDLC. Have a good read in your manual.

I had to add a ATB40 to my Hayes Accura - works a treat now. Add it to the modem setup commands.

Instead of "CONNECT 64000/HDLC"

You should get "CONNECT 64000/PPP"

Again, don't know why, but it works !

From my Hayes manual :


More & more ISP are offering services through dila-up ISDN lines fro higher data bandwidth. The equipment used at the ISP location are frequently ISDN LAN routers which, unlike TA's, do not have asynchronous capability. For this reason, TA's that support only V120 or asynchronous protocol will not work with this type of equipment. (I think from experience of some clients with BT they get a 64000/HDLC connection)

The Accura is able to convert teh asynchronus data it receives from your computer to the synchronus format in order to communcate with ISDN LAN routers. We call this process Asynchronous to Sychronus HDLC conversion. To simply, we call it Asyn-to-Sync PPP (Point-to-Point protocol).

Don't know what it means, but it seemed important in my case !

B. Rgds
John

[Filippo Carletti]

Add "debug 8" at the top of /etc/diald.conf and kdebug 1 at the end of the line with pppd options (things like noipdefault etc)

/etc/rc.d/init.d/diald restart

And send you logs for us to see.

[Graham]

OK many thanks for the suggestions here !!!

I will not be in the office again until Friday morning but will be
trying in ernest to get things up and running.

Will of course try out the debug options and mods as well as
posting my findings here.

As a side . . . .

This is the best online resource I have EVER used !!!

Its really makes my day to see some people (who you dont even
know try and help you)

 - the human race isnt such a bad place after all )

[Graham]

Hi Again !

I tried adding ATB4 [Man says ATB4 = Async PPP > Sync PPP Conversion]
to the init string field from the console :-

Nov 22 13:54:54 server diald[826]: Delaying 10 seconds before clear to dial.
Nov 22 13:55:04 server diald[826]: Calling site 0.0.0.0
Nov 22 13:55:05 server chat[1989]: abort on (BUSY)
Nov 22 13:55:05 server chat[1989]: abort on (ERROR)
Nov 22 13:55:05 server chat[1989]: abort on (NO CARRIER)
Nov 22 13:55:05 server chat[1989]: abort on (NO DIALTONE)
Nov 22 13:55:05 server chat[1989]: abort on (Invalid Login)
Nov 22 13:55:05 server chat[1989]: abort on (Login incorrect)
Nov 22 13:55:05 server chat[1989]: report (CONNECT)
Nov 22 13:55:05 server chat[1989]: send (ATZ^M)
Nov 22 13:55:05 server chat[1989]: expect (OK)
Nov 22 13:55:05 server chat[1989]: ATZ^M^M
Nov 22 13:55:05 server chat[1989]: OK
Nov 22 13:55:05 server chat[1989]:  -- got it
Nov 22 13:55:05 server chat[1989]: send (ATATB4^M)
Nov 22 13:55:06 server chat[1989]: expect (OK)
Nov 22 13:55:06 server chat[1989]: ^M
Nov 22 13:55:06 server chat[1989]: ATATB4^M^M
Nov 22 13:55:06 server chat[1989]: NO CARRIER
Nov 22 13:55:06 server chat[1989]:  -- failed
Nov 22 13:55:06 server chat[1989]: Failed (NO CARRIER)
Nov 22 13:55:06 server diald[826]: Connect script failed.

I noticed that after change of this field I was NOT asked to re-boot
so I made some changes to the connect times options which did
force a reboot and subsequently changed the init string.

With that init string in I got no link or carrier light. It looks above as
thought the script is sending ATATB4 and NOT ATB4.

I will check the SME man for correct syntax or even just try entering
B4 and see what happens !

I then took Filippos advices and this is the result :-


Nov 22 14:16:26 server diald[827]: Calling site 0.0.0.0
Nov 22 14:16:27 server chat[1924]: abort on (BUSY)
Nov 22 14:16:27 server chat[1924]: abort on (ERROR)
Nov 22 14:16:27 server chat[1924]: abort on (NO CARRIER)
Nov 22 14:16:27 server chat[1924]: abort on (NO DIALTONE)
Nov 22 14:16:27 server chat[1924]: abort on (Invalid Login)
Nov 22 14:16:27 server chat[1924]: abort on (Login incorrect)
Nov 22 14:16:27 server chat[1924]: report (CONNECT)
Nov 22 14:16:27 server chat[1924]: send (ATZ^M)
Nov 22 14:16:27 server chat[1924]: expect (OK)
Nov 22 14:16:27 server chat[1924]: ATZ^M^M
Nov 22 14:16:27 server chat[1924]: OK
Nov 22 14:16:27 server chat[1924]:  -- got it
Nov 22 14:16:27 server chat[1924]: send (ATL0M0^M)
Nov 22 14:16:27 server chat[1924]: expect (OK)
Nov 22 14:16:27 server chat[1924]: ^M
Nov 22 14:16:27 server chat[1924]: ATL0M0^M^M
Nov 22 14:16:27 server chat[1924]: OK
Nov 22 14:16:27 server chat[1924]:  -- got it
Nov 22 14:16:27 server chat[1924]: send (ATD9,,,08456609282^M)
Nov 22 14:16:28 server chat[1924]: expect (CONNECT)
Nov 22 14:16:28 server chat[1924]: ^M
Nov 22 14:16:32 server chat[1924]: ATD9,,,08456609282^M^M
Nov 22 14:16:32 server chat[1924]: CONNECT
Nov 22 14:16:32 server chat[1924]:  -- got it
Nov 22 14:16:32 server diald[827]: connector: chat:  Nov 22 14:16:32 CONNECT 64000/HDLC
Nov 22 14:16:32 server diald[827]: Connected to site 0.0.0.0
Nov 22 14:16:32 server diald[827]: Running pppd (pid = 1925).
Nov 22 14:16:32 server diald[1925]: Running pppd: /usr/sbin/pppd -defaultroute -detach modem crtscts mtu 1500 mru 1500 name uk2 noauth noipdefault ipparam diald
Nov 22 14:16:32 server pppd[1925]: pppd 2.4.0 started by root, uid 0
Nov 22 14:16:15 server kernel: ppp: ppp0 not active
Nov 22 14:16:32 server kernel: ppp_ioctl: set dbg flags to 10000
Nov 22 14:16:32 server kernel: ppp_ioctl: get unit: 0
Nov 22 14:16:32 server kernel: ppp_ioctl: set flags to 10000
Nov 22 14:16:32 server pppd[1925]: Using interface ppp0
Nov 22 14:16:32 server pppd[1925]: Connect: ppp0 <--> /dev/ttyS0
Nov 22 14:16:32 server kernel: ppp_tty_ioctl: set xasyncmap
Nov 22 14:16:32 server kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Nov 22 14:16:32 server kernel: ppp_ioctl: set flags to 10000
Nov 22 14:16:32 server kernel: ppp_ioctl: set mru to 5dc
Nov 22 14:16:32 server kernel: ppp_tty_ioctl: set rcv asyncmap ffffffff
Nov 22 14:16:32 server pppd[1925]: sent [LCP ConfReq id=0x1 ]
Nov 22 14:16:55 server kernel: ppp: channel ppp0 closing.
Nov 22 14:16:55 server kernel: ppp0 released
Nov 22 14:16:55 server kernel: ppp0: ccp closed
Nov 22 14:16:53 server last message repeated 7 times
Nov 22 14:16:55 server pppd[1925]: Hangup (SIGHUP)
Nov 22 14:16:55 server pppd[1925]: Modem hangup
Nov 22 14:16:55 server pppd[1925]: Connection terminated.
Nov 22 14:16:55 server pppd[1925]: Exit.
Nov 22 14:16:55 server diald[827]: stop ppp0: RTNETLINK answers: No such process
Nov 22 14:16:55 server kernel: ppp: ppp0 not active
Nov 22 14:16:55 server diald[827]: stop ppp0: SIOCSIFFLAGS: No such device or address
Nov 22 14:16:55 server diald[827]: Disconnected. Call duration 23 seconds.
Nov 22 14:16:55 server diald[827]: IP transmitted 270 bytes and received 0 bytes.
Nov 22 14:16:56 server diald[827]: Delaying 10 seconds before clear to dial.
Nov 22 14:17:06 server diald[827]: Calling site 0.0.0.0

I kind of expected to see much more detail here but am offering it up
for comment / further help - many thanks !!!

[Graham]

Thanks for all the help here guys - finally got
things up and running this after noon !

John Crisp - I owe you a few pints !!!

It was indeed down to the Async to Sync PPP init
setting.

I entered just 'B4' into the init string field at the server
console and am now happily typing this from a PC
in the upstairs office !

Thanks again !

Regards

Graham

ps I have LMK 9.0 and RH 8.0 here - submit
postal for copies !!!

[Graham]

Small note on init strings :-

If I entered ATB4 (as specified in the TA manual) the output result was in fact "ATATB4" [cant rememeber which file now]

This may be a bug I dont know about but in any case it seems I could miss off the leading AT as that was inserted for me.

I havent searched on this nor read the man pages so dont flame me if its already dead obvious - I am just trying to help in case any one else is having probs with init strings and reads this thread

[John Crisp]

Glad you got it working - I had hell & all trouble too. Different providers have different connection types, so you need to have a play.

>If I entered ATB4 (as specified in the TA manual) the output result was in >fact "ATATB4" [cant rememeber which file now]

I think that this is because the server assumes you are dumb and only wants the relevant commands as it will prefix the 'AT' command itself.

Most Hayes commands are prefixed AT for Attention but you can have several on one line - e.g ATB4L0M0&C1&D2  or whatever.

I guess the question in Setup should be slightly rephrased e.g provide any additional commands required without the AT prefix.

LMK9 & RH8 ? Drop me a mail

B. Rgds

John

[Andy]

Thank you all, gentlemen.
This may assist me in my attempts to get my isdn working too.