Dominik <(E-Mail Removed)> wrote:
> Here I send the log you wanted, and the modem is winmodem and it
> works fine when I manually dial to isp either with wvdial or kppp:
> May 17 22:23:06 pc pppd[1729]: pppd 2.4.1 started by root, uid 0
> May 17 22:23:06 pc pppd[1729]: Using interface ppp0
> May 17 22:23:06 pc pppd[1729]: local IP address 10.64.64.64
> May 17 22:23:06 pc pppd[1729]: remote IP address 10.112.112.112
> May 17 22:23:08 pc pppd[1729]: Starting link
> May 17 22:23:09 pc chat[1739]: report (CONNECT)
> May 17 22:23:09 pc chat[1739]: abort on (NO CARRIER)
> May 17 22:23:09 pc chat[1739]: abort on (BUSY)
> May 17 22:23:09 pc chat[1739]: abort on (NO DIAL TONE)
> May 17 22:23:09 pc chat[1739]: abort on (ERROR)
> May 17 22:23:09 pc chat[1739]: abort on (RING)
> May 17 22:23:09 pc chat[1739]: send (ATX3^M)
> May 17 22:23:09 pc chat[1739]: timeout set to 1 seconds
> May 17 22:23:09 pc chat[1739]: expect (OK)
> May 17 22:23:09 pc chat[1739]: ATX3^M^M
> May 17 22:23:09 pc chat[1739]: OK
> May 17 22:23:09 pc chat[1739]: -- got it
> May 17 22:23:09 pc chat[1739]: send (ATDT077100000^M)
> May 17 22:23:09 pc chat[1739]: timeout set to 40 seconds
> May 17 22:23:09 pc chat[1739]: expect (CONNECT)
> May 17 22:23:09 pc chat[1739]: ^M
> May 17 22:23:48 pc chat[1739]: ATDT077100000^M^M
> May 17 22:23:48 pc chat[1739]: CONNECT
> May 17 22:23:48 pc chat[1739]: -- got it
> May 17 22:23:48 pc chat[1739]: send (^M)
Sending a carriage-return (^M) can lead to the ISP presenting a prompt or
a menu, not starting PPP on it's end, and echoing pppd LCP negotiations.
> May 17 22:23:48 pc pppd[1729]: Serial connection established.
> May 17 22:23:48 pc pppd[1729]: Connect: ppp0 <--> /dev/modem
> May 17 22:23:59 pc pppd[1729]: Serial line is looped back.
> May 17 22:23:59 pc pppd[1729]: Connection terminated.
> May 17 22:24:00 pc pppd[1729]: Exit.
The time between "Connect: ppp0 <--> /dev/modem" and "Serial line is
looped back" is only 11 seconds. Either the pppd configuration for LCP
requests is not the default one and you didn't carefully read the first
sentence in
Add the chat -v option and the pppd dump and debug options. Follow the
recipe below to get a proper log and post an exact copy of it.
or the serial line is really looped back. Since the dump option would
have shown the pppd option configured before the PPP negotiations began
it would seem that you didn't carefully read the first sentence.
We need to know what pppd options are used and see LCP negotiations to
be sure that the carriage-return is eliciting a prompt/menu at the ISP
instead of immediately starting PPP negotiation, which often prevents
the ISP from starting PPP. But, from what I see above, that would be
my guess as to the most likely cause of your problem.
In order to avoid sending a carriage return and to wait a second for the
serial connection to stabilize (usually) the chat script should end with
the expect-send
CONNECT \d\c
if it is in a file specified by the chat -f option and
CONNECT \\d\\c
if it is specified on the chat command line.
To answer the question in your second reply, the IP addresses above can
be supplied by pppd when IPCP negotiation completes without IP addresses
being negotiated, or pppd is started in demand mode. It appears that
in this case pppd was started in demand mode.
IPCP negotiation should result in a remote IP address and a local
IP address as shown by ifconfig. This usually happens without any
further pppd configuration.
--
Clifford Kite Email: "echo
xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads:
http://ckite.no-ip.net/