#pppd call /etc/ppp/peers/lg, what is wrong with it ?

Any advice will be appreciated.
Here is my configuration and log(what else should I provide for futher
help?):


################################################## #



#minicom information
0=0 L1 V1 X4 &c1 &D1 E1 Q0 +FCLASS=0
OK

################################################## #
#/etc/ppp/chat-lg

#"" "AT"
#OK "ATZ"
#OK "ATE0V1"
#OK "AT+IFC=2,2"
#OK "ATDT#777"
TIMEOUT 3
ABORT '\nBUSY\r'
ABORT '\nNO ANSWER\r'
ABORT '\nRINGING\r\n\r\nRINGING\r'
'' AT
OK-+++\c-OK ATH0
TIMEOUT 30
OK ATDT#777
CONNECT ''
ogin:--ogin: CARD
password: CARD

################################################## #
#/etc/ppp/peers/lg

/dev/usb/ttyUSB0
#230400
115200
mtu 576
mru 576
modem
lock
crtscts
defaultroute
lcp-echo-failure 0
lcp-echo-interval 0
novj
persist
connect '/usr/sbin/chat -v -f /etc/ppp/chat-lg'

################################################## #

#tail -f /var/log/messages information
May 22 21:15:07 liucheng-zte kernel: CSLIP: code copyright 1989 Regents of
the University of California
May 22 21:15:07 liucheng-zte kernel: PPP generic driver version 2.4.2
May 22 21:15:07 liucheng-zte pppd[4265]: pppd 2.4.1 started by root, uid 0
May 22 21:15:08 liucheng-zte chat[4266]: timeout set to 3 seconds
May 22 21:15:08 liucheng-zte chat[4266]: abort on (\nBUSY\r)
May 22 21:15:08 liucheng-zte chat[4266]: abort on (\nNO ANSWER\r)
May 22 21:15:08 liucheng-zte chat[4266]: abort on
(\nRINGING\r\n\r\nRINGING\r)
May 22 21:15:08 liucheng-zte chat[4266]: send (AT^M)
May 22 21:15:08 liucheng-zte chat[4266]: expect (OK)
May 22 21:15:08 liucheng-zte chat[4266]: T^M^M
May 22 21:15:08 liucheng-zte chat[4266]: OK
May 22 21:15:08 liucheng-zte chat[4266]: -- got it
May 22 21:15:08 liucheng-zte chat[4266]: send (ATH0^M)
May 22 21:15:08 liucheng-zte chat[4266]: timeout set to 30 seconds
May 22 21:15:08 liucheng-zte chat[4266]: expect (OK)
May 22 21:15:08 liucheng-zte chat[4266]: ^M
May 22 21:15:08 liucheng-zte chat[4266]: ATH0^M^M
May 22 21:15:08 liucheng-zte chat[4266]: OK
May 22 21:15:08 liucheng-zte chat[4266]: -- got it
May 22 21:15:08 liucheng-zte chat[4266]: send (ATDT#777^M)
May 22 21:15:08 liucheng-zte chat[4266]: expect (CONNECT)
May 22 21:15:08 liucheng-zte chat[4266]: ^M
May 22 21:15:09 liucheng-zte chat[4266]: ATDT#777^M^M
May 22 21:15:09 liucheng-zte chat[4266]: CONNECT
May 22 21:15:09 liucheng-zte chat[4266]: -- got it
May 22 21:15:09 liucheng-zte chat[4266]: send (^M)
May 22 21:15:09 liucheng-zte chat[4266]: expect (ogin
May 22 21:15:09 liucheng-zte chat[4266]: ^M
May 22 21:15:39 liucheng-zte chat[4266]: alarm
May 22 21:15:39 liucheng-zte chat[4266]: send (^M)
May 22 21:15:39 liucheng-zte chat[4266]: expect (ogin
May 22 21:16:09 liucheng-zte chat[4266]: alarm
May 22 21:16:09 liucheng-zte chat[4266]: Failed
May 22 21:16:09 liucheng-zte pppd[4265]: Connect script failed
May 22 21:16:41 liucheng-zte chat[4270]: timeout set to 3 seconds
May 22 21:16:41 liucheng-zte chat[4270]: abort on (\nBUSY\r)
May 22 21:16:41 liucheng-zte chat[4270]: abort on (\nNO ANSWER\r)
May 22 21:16:41 liucheng-zte chat[4270]: abort on
(\nRINGING\r\n\r\nRINGING\r)
May 22 21:16:41 liucheng-zte chat[4270]: send (AT^M)
May 22 21:16:41 liucheng-zte chat[4270]: expect (OK)
May 22 21:16:41 liucheng-zte chat[4270]: T^M^M
May 22 21:16:41 liucheng-zte chat[4270]: OK
May 22 21:16:41 liucheng-zte chat[4270]: -- got it
May 22 21:16:41 liucheng-zte chat[4270]: send (ATH0^M)
May 22 21:16:41 liucheng-zte chat[4270]: timeout set to 30 seconds
May 22 21:16:41 liucheng-zte chat[4270]: expect (OK)
May 22 21:16:41 liucheng-zte chat[4270]: ^M
May 22 21:16:41 liucheng-zte chat[4270]: ATH0^M^M
May 22 21:16:41 liucheng-zte chat[4270]: OK
May 22 21:16:41 liucheng-zte chat[4270]: -- got it
May 22 21:16:41 liucheng-zte chat[4270]: send (ATDT#777^M)
May 22 21:16:41 liucheng-zte chat[4270]: expect (CONNECT)
May 22 21:16:41 liucheng-zte chat[4270]: ^M
May 22 21:16:41 liucheng-zte chat[4270]: ATDT#777^M^M
May 22 21:16:41 liucheng-zte chat[4270]: CONNECT
May 22 21:16:41 liucheng-zte chat[4270]: -- got it
May 22 21:16:41 liucheng-zte chat[4270]: send (^M)
May 22 21:16:41 liucheng-zte chat[4270]: expect (ogin
May 22 21:16:41 liucheng-zte chat[4270]: ^M
May 22 21:17:11 liucheng-zte chat[4270]: alarm
May 22 21:17:11 liucheng-zte chat[4270]: send (^M)
May 22 21:17:11 liucheng-zte chat[4270]: expect (ogin
May 22 21:17:41 liucheng-zte chat[4270]: alarm
May 22 21:17:41 liucheng-zte chat[4270]: Failed
May 22 21:17:41 liucheng-zte pppd[4265]: Connect script failed


################################################## #

lc <(E-Mail Removed)> wrote:
> Any advice will be appreciated.
> Here is my configuration and log(what else should I provide for futher
> help?):

> ################################################## #

> #minicom information
> 0=0 L1 V1 X4 &c1 &D1 E1 Q0 +FCLASS=0
> OK

Information via what AT command in minicom?

> ################################################## #
> #/etc/ppp/chat-lg

> #"" "AT"
> #OK "ATZ"
> #OK "ATE0V1"
> #OK "AT+IFC=2,2"
> #OK "ATDT#777"
> TIMEOUT 3
> ABORT '\nBUSY\r'
> ABORT '\nNO ANSWER\r'
> ABORT '\nRINGING\r\n\r\nRINGING\r'
> '' AT
> OK-+++\c-OK ATH0
> TIMEOUT 30
> OK ATDT#777
> CONNECT ''
> ogin:--ogin: CARD
> password: CARD

What is CARD?

Do you really expect a login/password prompt? Most ISPs use PAP or
CHAP authentication done within PPP negotiation. If you are not trying
to establish an ISP connection then describe exactly what you are trying
to do.

If you are not sure about the prompt then add the pppd option
"user Your_ISP_Username" and configure both of the files
/etc/ppp{pap,chap}-secrets with the line

Your_ISP_Username * Your_ISP_Password

Also replace the chat-lg script lines

> CONNECT ''
> ogin:--ogin: CARD
> password: CARD

with the single line

CONNECT \d\c

This line adds a 1-second delay before starting pppd and prevents chat
from sending a carriage-return which can cause trouble with some ISPs,
triggering a login prompt (apparently not the case here), or a menu to
be presented at the remote end.

> ################################################## #
> #/etc/ppp/peers/lg

> /dev/usb/ttyUSB0
> #230400
> 115200
> mtu 576
> mru 576
> modem
> lock
> crtscts
> defaultroute
> lcp-echo-failure 0
> lcp-echo-interval 0
> novj
> persist
> connect '/usr/sbin/chat -v -f /etc/ppp/chat-lg'

You don't need

> lcp-echo-failure 0
> lcp-echo-interval 0

and setting

> mtu 576
> mru 576

isn't recommended, especially mru.

The novj is probably not necessary either.

Adding a modem initialization string you know should work is recommended.

> ################################################## #

> #tail -f /var/log/messages information
> May 22 21:15:07 liucheng-zte kernel: CSLIP: code copyright 1989 Regents of
> the University of California
> May 22 21:15:07 liucheng-zte kernel: PPP generic driver version 2.4.2
> May 22 21:15:07 liucheng-zte pppd[4265]: pppd 2.4.1 started by root, uid 0
> May 22 21:15:08 liucheng-zte chat[4266]: timeout set to 3 seconds
> May 22 21:15:08 liucheng-zte chat[4266]: abort on (\nBUSY\r)
> May 22 21:15:08 liucheng-zte chat[4266]: abort on (\nNO ANSWER\r)
> May 22 21:15:08 liucheng-zte chat[4266]: abort on
> (\nRINGING\r\n\r\nRINGING\r)
> May 22 21:15:08 liucheng-zte chat[4266]: send (AT^M)
> May 22 21:15:08 liucheng-zte chat[4266]: expect (OK)
> May 22 21:15:08 liucheng-zte chat[4266]: T^M^M
> May 22 21:15:08 liucheng-zte chat[4266]: OK
> May 22 21:15:08 liucheng-zte chat[4266]: -- got it
> May 22 21:15:08 liucheng-zte chat[4266]: send (ATH0^M)
> May 22 21:15:08 liucheng-zte chat[4266]: timeout set to 30 seconds
> May 22 21:15:08 liucheng-zte chat[4266]: expect (OK)
> May 22 21:15:08 liucheng-zte chat[4266]: ^M
> May 22 21:15:08 liucheng-zte chat[4266]: ATH0^M^M
> May 22 21:15:08 liucheng-zte chat[4266]: OK
> May 22 21:15:08 liucheng-zte chat[4266]: -- got it
> May 22 21:15:08 liucheng-zte chat[4266]: send (ATDT#777^M)
> May 22 21:15:08 liucheng-zte chat[4266]: expect (CONNECT)
> May 22 21:15:08 liucheng-zte chat[4266]: ^M
> May 22 21:15:09 liucheng-zte chat[4266]: ATDT#777^M^M
> May 22 21:15:09 liucheng-zte chat[4266]: CONNECT
> May 22 21:15:09 liucheng-zte chat[4266]: -- got it
> May 22 21:15:09 liucheng-zte chat[4266]: send (^M)
> May 22 21:15:09 liucheng-zte chat[4266]: expect (ogin
> May 22 21:15:09 liucheng-zte chat[4266]: ^M
> May 22 21:15:39 liucheng-zte chat[4266]: alarm
> May 22 21:15:39 liucheng-zte chat[4266]: send (^M)
> May 22 21:15:39 liucheng-zte chat[4266]: expect (ogin
> May 22 21:16:09 liucheng-zte chat[4266]: alarm
> May 22 21:16:09 liucheng-zte chat[4266]: Failed
> May 22 21:16:09 liucheng-zte pppd[4265]: Connect script failed

The remote doesn't present a login prompt (at least not one ending in
"ogin:"). What does minicom show when you call the same number with it?

-- Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* In his wisdom RMS decided that people need no man pages when they
can use GNU's beautiful info system.
Unfortunately, everybody I know greatly prefers man pages.
- From the man-pages-1.55/man1/README */

On Sat, 22 May 2004 21:39:35 +0800, lc
<(E-Mail Removed)> wrote:
> Any advice will be appreciated.
> Here is my configuration and log(what else should I provide for futher
> help?):
>
> May 22 21:15:09 liucheng-zte chat[4266]: CONNECT
> May 22 21:15:09 liucheng-zte chat[4266]: -- got it
> May 22 21:15:09 liucheng-zte chat[4266]: send (^M)
> May 22 21:15:09 liucheng-zte chat[4266]: expect (ogin
> May 22 21:15:09 liucheng-zte chat[4266]: ^M
> May 22 21:15:39 liucheng-zte chat[4266]: alarm
> May 22 21:15:39 liucheng-zte chat[4266]: send (^M)
> May 22 21:15:39 liucheng-zte chat[4266]: expect (ogin
> May 22 21:16:09 liucheng-zte chat[4266]: alarm

You aren't getting a login: prompt. Are you sure the host doesn't use
PAP or CHAP? Do you see a "login:" if you use minicom?

--
Stupidity got us into this mess -- why can't it get us out?

"Clifford Kite" <(E-Mail Removed)> дÈëÓʼþ
news(E-Mail Removed)...


> > #minicom information
> > 0=0 L1 V1 X4 &c1 &D1 E1 Q0 +FCLASS=0
> > OK

> Information via what AT command in minicom?

It display automaticly in minicom after initializing,
I think it is caused by my init string ,which is configured using minicom -s
And I did as your said(I do really need an ISP connection!):
1,add the pppd option "user CARD"
2,configure both of the files /etc/ppp{pap,chap}-secrets with the line
"CARD" * "CARD"
3,Also replace the chat-lg script lines
> CONNECT ''
> ogin:--ogin: CARD
> password: CARD
with the single line

CONNECT \d\c





There was a big progress with this method, but I encouterd a new problem
Following section is my /var/log/debug
I hope i need not recompile the kernel, because after I recompiled the 2.6.5
kernel,
minicom cannot detect /dev/usb/ttyUSB0
##################################################

May 23 09:45:30 liucheng-zte pppd[4727]: pppd 2.4.1 started by root, uid 0
May 23 09:45:33 liucheng-zte pppd[4727]: Serial connection established.
May 23 09:45:33 liucheng-zte pppd[4727]: using channel 5
May 23 09:45:33 liucheng-zte pppd[4727]: Using interface ppp0
May 23 09:45:33 liucheng-zte pppd[4727]: Connect: ppp0 <--> /dev/usb/ttyUSB0
May 23 09:45:34 liucheng-zte pppd[4727]: sent [LCP ConfReq id=0x1 <asyncmap
0x0> <magic 0x47cded24> <pcomp> <accomp>]
May 23 09:45:40 liucheng-zte last message repeated 2 times
May 23 09:45:40 liucheng-zte pppd[4727]: rcvd [LCP ConfReq id=0x1 <asyncmap
0x0> <auth chap MD5> <magic 0x4d0a1988>]
May 23 09:45:40 liucheng-zte pppd[4727]: sent [LCP ConfRej id=0x1 <auth chap
MD5>]
May 23 09:45:40 liucheng-zte pppd[4727]: rcvd [LCP ConfAck id=0x1 <asyncmap
0x0> <magic 0x47cded24> <pcomp> <accomp>]
May 23 09:45:40 liucheng-zte pppd[4727]: rcvd [LCP ConfAck id=0x1 <asyncmap
0x0> <magic 0x47cded24> <pcomp> <accomp>]
May 23 09:45:40 liucheng-zte pppd[4727]: rcvd [LCP ConfReq id=0x2 <asyncmap
0x0> <auth chap MD5> <magic 0x4d0a1988>]
May 23 09:45:40 liucheng-zte pppd[4727]: sent [LCP ConfRej id=0x2 <auth chap
MD5>]
May 23 09:45:40 liucheng-zte pppd[4727]: rcvd [LCP ConfAck id=0x1 <asyncmap
0x0> <magic 0x47cded24> <pcomp> <accomp>]
May 23 09:45:40 liucheng-zte pppd[4727]: rcvd [LCP ConfReq id=0x3 <asyncmap
0x0> <magic 0x4d0a1988>]
May 23 09:45:40 liucheng-zte pppd[4727]: sent [LCP ConfAck id=0x3 <asyncmap
0x0> <magic 0x4d0a1988>]
May 23 09:45:40 liucheng-zte pppd[4727]: sent [IPCP ConfReq id=0x1 <addr
0.0.0.0>]
May 23 09:45:40 liucheng-zte modprobe: modprobe: Can't locate module
ppp-compress-21
May 23 09:45:40 liucheng-zte modprobe: modprobe: Can't locate module
ppp-compress-21
May 23 09:45:40 liucheng-zte pppd[4727]: sent [CCP ConfReq id=0x1 <deflate
15> <deflate(old#) 15>]
May 23 09:45:40 liucheng-zte pppd[4727]: rcvd [IPCP ConfReq id=0x1 <addr
220.192.20.17>]
May 23 09:45:40 liucheng-zte pppd[4727]: sent [IPCP ConfAck id=0x1 <addr
220.192.20.17>]
May 23 09:45:41 liucheng-zte pppd[4727]: rcvd [IPCP ConfRej id=0x1 <addr
0.0.0.0>]
May 23 09:45:41 liucheng-zte pppd[4727]: sent [IPCP ConfReq id=0x2 <addrs
0.0.0.0 0.0.0.0>]
May 23 09:45:41 liucheng-zte pppd[4727]: rcvd [LCP ProtRej id=0x4 80 fd 01
01 00 0c 1a 04 78 00 18 04 78 00]
May 23 09:45:41 liucheng-zte pppd[4727]: rcvd [IPCP ConfRej id=0x2 <addrs
0.0.0.0 0.0.0.0>]
May 23 09:45:41 liucheng-zte pppd[4727]: sent [IPCP ConfReq id=0x3]
May 23 09:45:41 liucheng-zte pppd[4727]: rcvd [IPCP ConfAck id=0x3]
May 23 09:45:41 liucheng-zte pppd[4727]: Could not determine local IP
address
May 23 09:45:41 liucheng-zte pppd[4727]: sent [IPCP TermReq id=0x4 "Could
not determine local IP address"]
May 23 09:45:41 liucheng-zte pppd[4727]: rcvd [IPCP TermAck id=0x4]
May 23 09:45:41 liucheng-zte pppd[4727]: sent [LCP TermReq id=0x2 "No
network protocols running"]
May 23 09:45:41 liucheng-zte pppd[4727]: rcvd [LCP TermAck id=0x2]
May 23 09:45:41 liucheng-zte pppd[4727]: Connection terminated.
May 23 09:45:41 liucheng-zte pppd[4727]: Connect time 0.2 minutes.
May 23 09:45:41 liucheng-zte pppd[4727]: Sent 50 bytes, received 38 bytes.
May 23 09:45:42 liucheng-zte pppd[4727]: Exit.





Thanks!

"Clifford Kite" <(E-Mail Removed)> дÈëÓʼþ
news(E-Mail Removed)...


> > #minicom information
> > 0=0 L1 V1 X4 &c1 &D1 E1 Q0 +FCLASS=0
> > OK

> Information via what AT command in minicom?

It display automaticly in minicom after initializing,
I think it is caused by my init string ,which is configured using minicom -s
And I did as your said(I do really need an ISP connection!):
1,add the pppd option "user CARD"
2,configure both of the files /etc/ppp{pap,chap}-secrets with the line
"CARD" * "CARD"
3,Also replace the chat-lg script lines
> CONNECT ''
> ogin:--ogin: CARD
> password: CARD
with the single line

CONNECT \d\c





There was a big progress with this method, but I encouterd a new problem
Following section is my /var/log/debug
##################################################

May 23 09:45:30 liucheng-zte pppd[4727]: pppd 2.4.1 started by root, uid 0
May 23 09:45:33 liucheng-zte pppd[4727]: Serial connection established.
May 23 09:45:33 liucheng-zte pppd[4727]: using channel 5
May 23 09:45:33 liucheng-zte pppd[4727]: Using interface ppp0
May 23 09:45:33 liucheng-zte pppd[4727]: Connect: ppp0 <--> /dev/usb/ttyUSB0
May 23 09:45:34 liucheng-zte pppd[4727]: sent [LCP ConfReq id=0x1 <asyncmap
0x0> <magic 0x47cded24> <pcomp> <accomp>]
May 23 09:45:40 liucheng-zte last message repeated 2 times
May 23 09:45:40 liucheng-zte pppd[4727]: rcvd [LCP ConfReq id=0x1 <asyncmap
0x0> <auth chap MD5> <magic 0x4d0a1988>]
May 23 09:45:40 liucheng-zte pppd[4727]: sent [LCP ConfRej id=0x1 <auth chap
MD5>]
May 23 09:45:40 liucheng-zte pppd[4727]: rcvd [LCP ConfAck id=0x1 <asyncmap
0x0> <magic 0x47cded24> <pcomp> <accomp>]
May 23 09:45:40 liucheng-zte pppd[4727]: rcvd [LCP ConfAck id=0x1 <asyncmap
0x0> <magic 0x47cded24> <pcomp> <accomp>]
May 23 09:45:40 liucheng-zte pppd[4727]: rcvd [LCP ConfReq id=0x2 <asyncmap
0x0> <auth chap MD5> <magic 0x4d0a1988>]
May 23 09:45:40 liucheng-zte pppd[4727]: sent [LCP ConfRej id=0x2 <auth chap
MD5>]
May 23 09:45:40 liucheng-zte pppd[4727]: rcvd [LCP ConfAck id=0x1 <asyncmap
0x0> <magic 0x47cded24> <pcomp> <accomp>]
May 23 09:45:40 liucheng-zte pppd[4727]: rcvd [LCP ConfReq id=0x3 <asyncmap
0x0> <magic 0x4d0a1988>]
May 23 09:45:40 liucheng-zte pppd[4727]: sent [LCP ConfAck id=0x3 <asyncmap
0x0> <magic 0x4d0a1988>]
May 23 09:45:40 liucheng-zte pppd[4727]: sent [IPCP ConfReq id=0x1 <addr
0.0.0.0>]
May 23 09:45:40 liucheng-zte modprobe: modprobe: Can't locate module
ppp-compress-21
May 23 09:45:40 liucheng-zte modprobe: modprobe: Can't locate module
ppp-compress-21
May 23 09:45:40 liucheng-zte pppd[4727]: sent [CCP ConfReq id=0x1 <deflate
15> <deflate(old#) 15>]
May 23 09:45:40 liucheng-zte pppd[4727]: rcvd [IPCP ConfReq id=0x1 <addr
220.192.20.17>]
May 23 09:45:40 liucheng-zte pppd[4727]: sent [IPCP ConfAck id=0x1 <addr
220.192.20.17>]
May 23 09:45:41 liucheng-zte pppd[4727]: rcvd [IPCP ConfRej id=0x1 <addr
0.0.0.0>]
May 23 09:45:41 liucheng-zte pppd[4727]: sent [IPCP ConfReq id=0x2 <addrs
0.0.0.0 0.0.0.0>]
May 23 09:45:41 liucheng-zte pppd[4727]: rcvd [LCP ProtRej id=0x4 80 fd 01
01 00 0c 1a 04 78 00 18 04 78 00]
May 23 09:45:41 liucheng-zte pppd[4727]: rcvd [IPCP ConfRej id=0x2 <addrs
0.0.0.0 0.0.0.0>]
May 23 09:45:41 liucheng-zte pppd[4727]: sent [IPCP ConfReq id=0x3]
May 23 09:45:41 liucheng-zte pppd[4727]: rcvd [IPCP ConfAck id=0x3]
May 23 09:45:41 liucheng-zte pppd[4727]: Could not determine local IP
address
May 23 09:45:41 liucheng-zte pppd[4727]: sent [IPCP TermReq id=0x4 "Could
not determine local IP address"]
May 23 09:45:41 liucheng-zte pppd[4727]: rcvd [IPCP TermAck id=0x4]
May 23 09:45:41 liucheng-zte pppd[4727]: sent [LCP TermReq id=0x2 "No
network protocols running"]
May 23 09:45:41 liucheng-zte pppd[4727]: rcvd [LCP TermAck id=0x2]
May 23 09:45:41 liucheng-zte pppd[4727]: Connection terminated.
May 23 09:45:41 liucheng-zte pppd[4727]: Connect time 0.2 minutes.
May 23 09:45:41 liucheng-zte pppd[4727]: Sent 50 bytes, received 38 bytes.
May 23 09:45:42 liucheng-zte pppd[4727]: Exit.





Thanks!

lc <(E-Mail Removed)> wrote:

> "Clifford Kite" <(E-Mail Removed)> дÈëÓʼþ
> news(E-Mail Removed)...

>> > #minicom information
>> > 0=0 L1 V1 X4 &c1 &D1 E1 Q0 +FCLASS=0
>> > OK

>> Information via what AT command in minicom?

> It display automaticly in minicom after initializing,
> I think it is caused by my init string ,which is configured using minicom -s

Okay, then it's not a stored profile that could be easily used by pppd
(e.g., AT&F, AT&F1).

> And I did as your said(I do really need an ISP connection!):
> 1,add the pppd option "user CARD"
> 2,configure both of the files /etc/ppp{pap,chap}-secrets with the line
> "CARD" * "CARD"

Again, what is CARD? It would be unusual for both an ISP user name
and password to be the same. And also again, if something special is
being attempted then please explain.

> 3,Also replace the chat-lg script lines
>> CONNECT ''
>> ogin:--ogin: CARD
>> password: CARD
> with the single line

> CONNECT \d\c

> There was a big progress with this method, but I encouterd a new problem
> Following section is my /var/log/debug
> I hope i need not recompile the kernel, because after I recompiled the 2.6.5
> kernel,
> minicom cannot detect /dev/usb/ttyUSB0

Pppd found it. Was 2.6.5 running when the log below was generated?

> ##################################################

> May 23 09:45:30 liucheng-zte pppd[4727]: pppd 2.4.1 started by root, uid 0
> May 23 09:45:33 liucheng-zte pppd[4727]: Serial connection established.
> May 23 09:45:33 liucheng-zte pppd[4727]: using channel 5
> May 23 09:45:33 liucheng-zte pppd[4727]: Using interface ppp0
> May 23 09:45:33 liucheng-zte pppd[4727]: Connect: ppp0 <--> /dev/usb/ttyUSB0
> May 23 09:45:34 liucheng-zte pppd[4727]: sent [LCP ConfReq id=0x1 <asyncmap
> 0x0> <magic 0x47cded24> <pcomp> <accomp>]
> May 23 09:45:40 liucheng-zte last message repeated 2 times
> May 23 09:45:40 liucheng-zte pppd[4727]: rcvd [LCP ConfReq id=0x1 <asyncmap
> 0x0> <auth chap MD5> <magic 0x4d0a1988>]
> May 23 09:45:40 liucheng-zte pppd[4727]: sent [LCP ConfRej id=0x1 <auth chap
> MD5>]

Here pppd rejects CHAP authentication requested by the peer.

What followed showed that was the only authentication method the peer
would accept. The peer is broken as evidenced by the fact that it did
not send a Terminate-Request but instead hung in until IPCP reached the
open state on your host with no IP addresses assigned. Ugh.

> May 23 09:45:41 liucheng-zte pppd[4727]: sent [IPCP ConfReq id=0x3]
> May 23 09:45:41 liucheng-zte pppd[4727]: rcvd [IPCP ConfAck id=0x3]
> May 23 09:45:41 liucheng-zte pppd[4727]: Could not determine local IP
> address

....

> May 23 09:45:41 liucheng-zte pppd[4727]: sent [IPCP TermReq id=0x4 "Could
> not determine local IP address"]
> May 23 09:45:41 liucheng-zte pppd[4727]: rcvd [IPCP TermAck id=0x4]
> May 23 09:45:41 liucheng-zte pppd[4727]: sent [LCP TermReq id=0x2 "No
> network protocols running"]
> May 23 09:45:41 liucheng-zte pppd[4727]: rcvd [LCP TermAck id=0x2]
> May 23 09:45:41 liucheng-zte pppd[4727]: Connection terminated.

Then pppd requested Termination, and the peer agreed.

I'm not sure what's happening. With the user option and the secrets
line CHAP should have been accepted even if it subsequently failed.
Maybe "refuse-chap" or the old version of that option, -chap, in
a privileged options file?

Add the pppd option dryrun and post the output.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/

I have to admit that i had made some mistakes-----I missed option user CARD
in pppd
login:CARD
password:CARD
is really the u/p of the carrier in our country.

NOW everything goes well, Thank you very much.