Topic: ISDN/ISP Problems

[Danny]

I'm trying to configure e-smith to connect via ISDN. The system works fine with another ISP, but as soon as i try and use Plusnet i get the following error:-

Jan 18 12:11:14 e-smith kernel: lldata_handler unknown primitive 0x232
Jan 18 12:11:16 e-smith kernel: lldata_handler unknown primitive 0x232

Does anyone know what this means or how to fix it?

thanks in advance,

Danny.

Full log bellow:
Jan 18 12:11:10 e-smith chat[866]: abort on (NO CARRIER)
Jan 18 12:11:10 e-smith chat[866]: abort on (NO DIALTONE)
Jan 18 12:11:10 e-smith chat[866]: abort on (Invalid Login)
Jan 18 12:11:10 e-smith chat[866]: abort on (Login incorrect)
Jan 18 12:11:10 e-smith chat[866]: send (ATZ^M)
Jan 18 12:11:11 e-smith chat[866]: expect (OK)
Jan 18 12:11:11 e-smith chat[866]: ATZ^M^M
Jan 18 12:11:11 e-smith chat[866]: OK
Jan 18 12:11:11 e-smith chat[866]: -- got it
Jan 18 12:11:11 e-smith chat[866]: send (ATDT08440404101^M)
Jan 18 12:11:11 e-smith chat[866]: expect (CONNECT)
Jan 18 12:11:11 e-smith chat[866]: ^M
Jan 18 12:11:14 e-smith kernel: lldata_handler unknown primitive 0x232
Jan 18 12:11:16 e-smith kernel: lldata_handler unknown primitive 0x232
Jan 18 12:11:17 e-smith chat[866]: ATDT08440404101^M^M
Jan 18 12:11:17 e-smith chat[866]: NO CARRIER
Jan 18 12:11:17 e-smith chat[866]: -- failed
Jan 18 12:11:17 e-smith chat[866]: Failed (NO CARRIER)
Jan 18 12:11:17 e-smith diald[363]: Connect script failed.
Jan 18 12:11:18 e-smith diald[363]: Delaying 10 seconds before clear to dial.

[Philip Stinson]

I had similar problems with ISDN,

What you need to check is what protocol your isp uses for ISDN dial in.
Is it v.120 or something like that or is it ppp that they need, you will need to change your init string (the atz part) for the TA.

Also things like PAP or CHAP or PAP/CHAP authentication can cause trouble.

Hope this helps,

Philip

[Danny]

Many thanks for you help philip,

I changed the AT string to include ATS14=3 which sorted the lldata problem, but i'm still stuck.  

I think its still to do with CHAP/PAP as you said, it connects ok, waits, then just hangs up.  I've have checked my secrets files, and have tried changing the '-chap +pap' options in /etc/ppp/ppplogin.

Can you tell me which files to set DEBUG and KDEBUG in to get a bit more information (tried a few, and it made no difference to the log detail:), or point me in the right direction.

My log now looks like this:)

Jan 24 07:47:26 iserver diald[363]: Delaying 10 seconds before clear to dial.
Jan 24 07:47:37 iserver diald[363]: Calling site 192.168.1.2
Jan 24 07:47:38 iserver chat[717]: abort on (BUSY)
Jan 24 07:47:38 iserver chat[717]: abort on (ERROR)
Jan 24 07:47:38 iserver chat[717]: abort on (NO CARRIER)
Jan 24 07:47:38 iserver chat[717]: abort on (NO DIALTONE)
Jan 24 07:47:38 iserver chat[717]: abort on (Invalid Login)
Jan 24 07:47:38 iserver chat[717]: abort on (Login incorrect)
Jan 24 07:47:38 iserver chat[717]: send (ATZ&E123456S14=3^M)
Jan 24 07:47:38 iserver chat[717]: expect (OK)
Jan 24 07:47:38 iserver chat[717]: ATZ&E123456S14=3^M^M
Jan 24 07:47:38 iserver chat[717]: OK
Jan 24 07:47:38 iserver chat[717]:  -- got it
Jan 24 07:47:38 iserver chat[717]: send (ATDT08451400101^M)
Jan 24 07:47:38 iserver chat[717]: expect (CONNECT)
Jan 24 07:47:38 iserver chat[717]: ^M
Jan 24 07:47:40 iserver chat[717]: ATDT08451400101^M^M
Jan 24 07:47:40 iserver chat[717]: CONNECT
Jan 24 07:47:40 iserver chat[717]:  -- got it
Jan 24 07:47:40 iserver diald[363]: Connected to site 192.168.1.2
Jan 24 07:47:40 iserver pppd[718]: pppd 2.3.11 started by root, uid 0
Jan 24 07:47:40 iserver diald[363]: Running pppd (pid = 718).
Jan 24 07:47:40 iserver pppd[718]: Using interface ppp0
Jan 24 07:47:40 iserver pppd[718]: Connect: ppp0 <--> /dev/ttyI0
Jan 24 07:48:04 iserver pppd[718]: Hangup (SIGHUP)
Jan 24 07:48:04 iserver pppd[718]: Modem hangup
Jan 24 07:48:04 iserver pppd[718]: Connection terminated.
Jan 24 07:48:04 iserver pppd[718]: Exit.
Jan 24 07:48:04 iserver diald[363]: start sl0: SIOCSIFMTU: Invalid argument
Jan 24 07:48:04 iserver diald[363]: start sl0: SIOCADDRT: File exists
Jan 24 07:48:04 iserver diald[363]: stop ppp0: SIOCDELRT: No such process
Jan 24 07:48:04 iserver kernel: ppp: ppp0 not active
Jan 24 07:48:04 iserver diald[363]: stop ppp0: SIOCSIFFLAGS: Device not configured
Jan 24 07:48:05 iserver diald[363]: Delaying 10 seconds before clear to dial.

[Danny]

I dont know wether this helps, but i have tried doin a manual PPP connection via minicom/ppp and i get the following:-

[root@iserver ppp]# pppd -d -detach /dev/ttyI0 38400
Using interface ppp0
Connect: ppp0 <--> /dev/ttyI0
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
Modem hangup
Connection terminated.
[root@iserver ppp]#

[Danny]

I dont know wether this helps, but i have tried doin a manual PPP connection via minicom/ppp and i get the following:-

[root@iserver ppp]# pppd -d -detach /dev/ttyI0 38400
Using interface ppp0
Connect: ppp0 <--> /dev/ttyI0
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
Modem hangup
Connection terminated.
[root@iserver ppp]#

[Charlie Brady]

Danny wrote:
>
> I dont know wether this helps, but i have tried doin a manual
> PPP connection via minicom/ppp and i get the following:-
>
> [root@iserver ppp]# pppd -d -detach /dev/ttyI0 38400
> Using interface ppp0
> Connect: ppp0 <--> /dev/ttyI0
> sent [LCP ConfReq id=0x1
> ]
> sent [LCP ConfReq id=0x1
> ]
...

This indicates that your PPP peer is not sending anything - you should get ConfAck or ConfNak in response.

You really should be asking your questions in the Experienced User forum. And be sure to read the documentation at http://www.e-smith.org/custom/ so that you make your changes correctly.

Regards

Charlie