ISDN connection fails - Help!
I have a SuSE 6.3 system with the updates to ISDN4Linux. The ISDN T/A is an
internal PCI card based on the HFC chipset. It is detected by the driver
and everything loads correctly at boot up. I have set up the ISDN
configuration files using YaSt and checked them manually. My ISP uses PAP
authentication and pap-secrets seems to be configured correctly. I can
connect using an analogue modem without difficulty. When trying to
establish an ISDN link, the system dials the number, a connection is
established briefly, and then it appears the remote server hangs up. The
relevant extract from the log files follows below (i enabled debug and +pword), and I would be grateful
for help, as I have tried everything I can think of to fix this problem,
and I don't know what to do next.
Thanks!
Grant.
isdnlog: Apr 26 10:40:33 * tei 113 calling 2548000, with ? RING (Data)
isdnlog: Apr 26 10:40:34 tei 113 calling 2548000, with ? Time:Wed Apr 26
10:39:00 2000
isdnlog: Apr 26 10:40:34 tei 113 calling 2548000, with ? CONNECT (Data)
isdnlog: Apr 26 10:40:34 tei 113 calling 2548000, with ? Unknown provider 33
ipppd[114]: Local number: 0, Remote number: 2548000, Type: outgoing
ipppd[114]: PHASE_WAIT -> PHASE_ESTABLISHED, ifunit: 0, linkunit: 0, fd: 7
ipppd[114]: sent [0][LCP ConfReq id=0x1
Am Don, 27 Apr 2000 schrieb Grant Walton:
I have a SuSE 6.3 system with the updates to ISDN4Linux. The ISDN T/A is an internal PCI card based on the HFC chipset. It is detected by the driver and everything loads correctly at boot up. I have set up the ISDN configuration files using YaSt and checked them manually. My ISP uses PAP authentication and pap-secrets seems to be configured correctly. I can connect using an analogue modem without difficulty. When trying to establish an ISDN link, the system dials the number, a connection is established briefly, and then it appears the remote server hangs up. The relevant extract from the log files follows below (i enabled debug and +pword), and I would be grateful for help, as I have tried everything I can think of to fix this problem, and I don't know what to do next.
ipppd[114]: rcvd [0][LCP ConfReq id=0x9f <auth chap md5>
] ipppd[114]: sent [0][LCP ConfNak id=0x9f <auth pap>] ipppd[114]: rcvd [0][LCP ConfReq id=0xa0 <auth chap md5> ] ipppd[114]: sent [0][LCP ConfNak id=0xa0 <auth pap>] ipppd[114]: rcvd [0][LCP ConfReq id=0xa1 <auth chap md5> ] ipppd[114]: sent [0][LCP ConfNak id=0xa1 <auth pap>] ipppd[114]: rcvd [0][LCP ConfReq id=0xa2 <auth chap md5> ] ipppd[114]: sent [0][LCP ConfNak id=0xa2 <auth pap>] ipppd[114]: rcvd [0][LCP ConfReq id=0xa3 <auth chap md5> ] ipppd[114]: sent [0][LCP ConfNak id=0xa3 <auth pap>] ipppd[114]: rcvd [0][LCP ConfReq id=0xa4 <auth chap md5> ipppd[114]: sent [0][LCP ConfRej id=0xa4 <auth chap md5>]
Hello Grent, there is a problem with the authentification: you receive a request for CHAP-Auth. (seems your provider uses this), but you (better your PC) donŽt agree and try the PAP-Auth. This happens five times until hangup. You have to set up your system for CHAP (see yast and /etc/ppp/chap-secrets Bye Thomas
participants (2)
-
Grant Walton
-
Thomas Mueller