[1681] in linux-net channel archive
Re: PPP Problem...Please Help..
daemon@ATHENA.MIT.EDU (Georg Wiegand)
Wed Jan 24 12:53:05 1996
From: Georg Wiegand <gw@sabine.ruhr.de>
To: nando.net!dcoutts@sabine.ruhr.de
Date: Tue, 23 Jan 1996 09:50:35 +0100 (GMT+0100)
Cc: vger.rutgers.edu!linux-net@sabine.ruhr.de (Group)
In-Reply-To: <Chameleon.4.01.2.960121013247.dcoutts@dcoutts.nando.net> from "dcoutts@nando.net" at Jan 21, 96 01:23:03 am
>
> Hello,
>
> I keep dropping my connection after about 20 seconds. I have read the HOWTO
> and realize that this is probably a modem problem. I want to make sure there
> is no way around it before I buy a new modem. I can connect to my ISP through
(...)
Maybe you should rewrite your script to let pppd manage connecting to
the other side:
********* SCRIPT **********
#!/bin/sh
NAME=dcoutts
KEY=5
PASSWORD=<passwd>
CUA=cua0
NUMBER=*70,8293560
export NAME KEY PASSWORD CUA NUMBER
# I don't think this is necessary becouse pppd checks itself if the
# port is locked
if [ -f /var/spool/uucp/LCK..${CUA} ]
then
echo "Another process has locked your Modem"
exit 1
fi
exec {path}/pppd /dev/${CUA} 115200 kdebug 4 lock crtscts defaultroute \
noipdefault modem stty 19200 -tostop crtscts lock \
connect '{path}/chat -v ABORT "NO CARRIER" ABORT BUSY "" ATZ OK ATDT${NUMBER} CONNECT "\d\d\r" TIMEOUT 5 "name>" ${NAME} "word>" ${PASSWORD} "keys:" ${KEY}'
********* SCRIPT END **********
Alternate you could say: ... connect {path_to_connect_script}
========== connect_script ==========
#!/bin/sh
{path}/chat -v ABORT "NO CARRIER" \
ABORT BUSY \
"" ATZ OK \
ATDT${NUMBER} CONNECT \
"\d\d\r" \
TIMEOUT 5 \
"name>" ${NAME} \
"word>" ${PASSWORD} \
"keys:" ${KEY}
========== connect_script end ==========
1) You should verify the '115200' speed option. I'm not shure if pppd can
handle this. Alternate you could use 38400 and use setserial to
actually switch to 115200.
(from 'man setserial' : "(...) spd_vhi Use 115kb when the application
requests 38.4kb. This parameter may be specified by a non-privileged
user.(...)")
2) I've added 'lock' as option to pppd to avoid other processes to try to
talk to the modem. You should verify the location of the lock file in
'pppd_src_root/pppd/sys-linux.c', else you get (e.g. from mgetty
running on the same device) characters written to the same device as
there is no lock file visible. I've forgotten this and had problems
with init says: 'respawning too fast' and mgetty wrote some chars to
/dev/$modem_tty.
3) added paths to pppd/chat if they're not in your search-path (seems
to be no problem with your setup)
This should work.
BTW: what is the version number of your pppd? I've never seen a
startup file like yours (started with 2.2.0c).
Hope this helps
Bye
George
