Ray
Many thanks for your prompt reply. I tried as you suggested and the only
difference between the factory setting and the setting initialised by
minicom is that s7=50 (factory) as opposed to s7=45 (minicom).
I removed the initialisation string from minicom and issued the at&f
before trying the manual login and pppd startup. All was fine.
I then changed ppp-on to the following:
#!/bin/sh
#
# Script to initiate a ppp connection. This is the first part of the
# pair of scripts. This is not a secure pair of scripts as the codes
# are visible with the 'ps' command. However, it is simple.
#
<SNIP>
exec /usr/sbin/pppd debug /dev/ttyS0 38400 \
$LOCAL_IP:$REMOTE_IP \
connect 'chat -v -f /etc/ppp/isp.chat' &
with isp.chat as
""AT
OK ATDT9,333333
38400 /n
ogin: my_acc
word: my_pwd
I now get the following in messages:
Apr 28 10:59:23 testserver pppd[765]: pppd 2.3.3 started by root, uid 0
Apr 28 10:59:24 testserver chat[766]: send (AT^M)
Apr 28 10:59:24 testserver chat[766]: expect (OK)
Apr 28 10:59:24 testserver chat[766]: AT^M^M
Apr 28 10:59:24 testserver chat[766]: OK
Apr 28 10:59:24 testserver chat[766]: -- got it
Apr 28 10:59:24 testserver chat[766]: send (ATDT9,333333^M)
Apr 28 10:59:25 testserver chat[766]: expect (38400)
Apr 28 10:59:25 testserver chat[766]: ^M
Apr 28 11:00:00 testserver chat[766]: ATDT9,333333^M^M
Apr 28 11:00:00 testserver chat[766]: CONNECT 38400
Apr 28 11:00:00 testserver chat[766]: -- got it
Apr 28 11:00:00 testserver chat[766]: send (/n^M)
Apr 28 11:00:00 testserver chat[766]: expect (ogin:)
Apr 28 11:00:00 testserver chat[766]: ^M
Apr 28 11:00:02 testserver chat[766]: ^M
Apr 28 11:00:02 testserver chat[766]: login:
Apr 28 11:00:02 testserver chat[766]: -- got it
Apr 28 11:00:02 testserver chat[766]: send (my_acc^M)
Apr 28 11:00:02 testserver chat[766]: expect (word:)
Apr 28 11:00:02 testserver chat[766]: my_acc^M
Apr 28 11:00:02 testserver chat[766]: Password:
Apr 28 11:00:02 testserver chat[766]: -- got it
Apr 28 11:00:02 testserver chat[766]: send (my_pwd^M)
Apr 28 11:00:03 testserver pppd[765]: Serial connection established.
Apr 28 11:00:04 testserver pppd[765]: Using interface ppp0
Apr 28 11:00:04 testserver pppd[765]: Connect: ppp0 <--> /dev/ttyS0
Apr 28 11:00:06 testserver pppd[765]: local IP address 194.168.74.92
Apr 28 11:00:06 testserver pppd[765]: remote IP address 194.168.74.242
and everything is ok from thereon in.
So I assume it must be the chat script it doesn't like. What I thought
I'd do is rebuild the old one from the new one until I find the point at
which it chokes. I'll let you know how I get on.
A couple of other points.
The cut off on the old script occurs immediately the other end picks up,
with no time out.
I tried to alter parts of the old script,ppp-on-dialer, but each time the
output from messages remained the same. Specifically I tried to change
CONNECT '' /
to
CONNECT 38400 '' /
and
38400 '' /
but each time messages reports
Apr 28 10:59:25 testserver chat[766]: expect (CONNECT).
Not sure what all this means but seems odd to me.
Once again I'll let you know how I get on. Thanks for all you help. I
now understand a lot more about the modem side of things.
Paul
----------
From: Ray Olszewski
Sent: 27 April 1999 19:48
To: Rogers, Paul; Linux Newbie
Subject: Re: pppd problems
The problem you are having is that, after the modem dials and connects,
it
does not send the "CONNECT" message over the serial line for chat to see
(or, at least, chat doesn't see the message - I infer that this is
because
the modem isn't sending it). As a result, chat times out the connection
after 30 seconds of (apparent) inactivity.
You see this in this excerpt from the log you posted, on the lines I've
marked:
>Apr 27 14:23:39 testserver chat[419]: expect (OK)
>Apr 27 14:23:39 testserver chat[419]: ^M
>Apr 27 14:23:39 testserver chat[419]: ATH0^M^M
>Apr 27 14:23:39 testserver chat[419]: OK
>Apr 27 14:23:39 testserver chat[419]: -- got it
>Apr 27 14:23:39 testserver chat[419]: send (ATDT9,333333^M)
>Apr 27 14:23:39 testserver chat[419]: expect (CONNECT)
==>>>it wants this: ^^^^^^^^^^^^^^^^
>Apr 27 14:23:39 testserver chat[419]: ^M
(this is just from the prior OK) ^^
>Apr 27 14:24:09 testserver chat[419]: alarm
(this is the timeout after 30 sec) ^^^^^
>Apr 27 14:24:09 testserver pppd[418]: Connect script failed
>Apr 27 14:24:09 testserver chat[419]: Failed
>Apr 27 14:24:10 testserver pppd[418]: Exit.
Why might this be? You won't find out with your present minicom setup,
because most of the minicom init string consists of Hayes-standard
commands
that tell the modem to send messages like CONNECT in word form. SO,
here's
what I'd do.
Run minicom with NO init string, then do an "AT&V" to see what the stored
active profile in the modem is. Change any settings that are different
from
the ones in the minicom init string, then save the active profile (modem
command for this varies - one of my old modems uses AT&W0 to store it in
profile 0, then AT&Y0 to tell the modem to use profile 0 - but consult
your
modem documentation).
If your modem doesn't have non-volatile RAM in it to store profiles,
you'll
need to modify the chat script to add the necessary commands to its init
string, possibly on this line of ppp-on-dialer:
> '' \rAT \
(but I may have that detail wrong, so check your documentation for chat
on
init strings).
One last thing: no, your message wan't too detailed. Long messages can be
a
drag, but ones that leave out important information are a worse drag, and
when you don't know what's causing a problem, it's hard to know what to
include, what to omit. Generally, I wish people posting questions
included
*more* detail, not less.
At 03:38 PM 4/27/99 +0100, Rogers, Paul wrote [abridged]:
>I am having dificulty connecting to my ISP. Iam using Redhat 5.1 2.2.2
>with a Hayes Accura 56k Speakerphone (it's not been upgraded to V90). I
>have followed the PPP How To to the stage where I can :
[omitted]
>However, when I then try and automate this process using the following
>ppp-on and ppp-on-dialer scripts:
[omitted]
>the following occurs:
>
>i) Modem dials out.
>ii) As soon as the modem at the other end answers the connection is
>broken (by which end I don't know)
[omitted]
>i) just initialising the modem from minicom and then running ppp-on � no
>joy. Not sure if chat's ATH0 resets modem.
>ii) I also tried issuing the ATZ command in minicom and then dialing in
>manually, logging on etc. This all works fine.
>
>This leads me to suspect its not a modem setting problem(???)
[omitted]
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.328.4219 voice [EMAIL PROTECTED]
----------------------------------------------------------------
