Regarding my problem getting chat to do anything, even though the serial
line is OK, evidenced by successful cu sessions and the ability to get
pppd going on the slackware install on the same machine.
On 19 Sep 1999, John Hasler wrote:
> I just had a thought. Try changing the line
>
> '' ATZ
>
I just had a thought. Try changing the line
'' ATZ
to
'' \dATZ
The '\d' tells chat to pause for one second. The modem may need some time
to get ready.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
Robert King writes:
> OK - so you're pretty sure this is a chat issue
It is possible that pppd isn't getting chat properly hooked to the serial
port, but that seems unlikely.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
On 18 Sep 1999, John Hasler wrote:
> Robert King writes:
> > The modem responds fine from cu. I get an OK back from AT&F.
>
> What does it do if you send it ATZ from cu?
I get OK back.
> Try replacing ATZ with AT&F
> in /etc/chatscripts/provider.
OK, I'll try that after this session. (I'm
Robert writes:
> I thought I was asking it to use ttyS1
Robert
You are.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
Robert King writes:
> The modem responds fine from cu. I get an OK back from AT&F.
What does it do if you send it ATZ from cu? Try replacing ATZ with AT&F
in /etc/chatscripts/provider.
> I think it could be a problem with changes to pppd.
At the point at which your problem occurs pppd isn't d
On Sat, 18 Sep 1999, Jesse Jacobsen wrote:
> --BwCQnh7xodEAoBMC
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: quoted-printable
>
> I wonder if you've set up Debian to use /dev/cua1. It should use
> /dev/ttyS1 instead, since the cua- "callout" devices are being phased
On Sat, 18 Sep 1999, Marcin Owsiany wrote:
> first thing: should there be any chat script at all if you authenticate
> using cu? (i've never used cu, so i may be wrong)
> Should the chat script try to reset the modem if it has already connected??
> (the ATZ and AT)
This is using pon on the new
On 18 Sep 1999, John Hasler wrote:
> Robert King wrote:
> > I'm fairly sure that the serial conifg is OK, as I can get out with cu -l
> > /dev/ttyS1, but when I try to start pppd, it complains about cu having
> > the serial line and won't let it at it.
>
> Odd. I just tried cu on this system and
On Sat, Sep 18, 1999 at 05:06:18PM +1000, [EMAIL PROTECTED] wrote:
> Hi,
>I'm typing this from my old slackware install. I connect on this
> installation using cu -l /dev/cua1 then negotiating my way through my
> ISP's login manually, then start pppd in another window, then quitting
> from cu.
On 09/18/99 at 17:06:18, [EMAIL PROTECTED] wrote concerning "ppp failure under
debian (slakware with pppd 2.2 patch level 0 works)":
> Hi,
>I'm typing this from my old slackware install. I connect on this
> installation using cu -l /dev/cua1 then negotiating my way
> I'm fairly sure that the serial conifg is OK, as I can get out with cu -l
> /dev/ttyS1, but when I try to start pppd, it complains about cu having
> the serial line and won't let it at it.
Odd. I just tried cu on this system and it complains that the line is in
use. Pon works fine. Is there a
Hi,
I'm typing this from my old slackware install. I connect on this
installation using cu -l /dev/cua1 then negotiating my way through my
ISP's login manually, then start pppd in another window, then quitting
from cu. This worked fine whne this machine was a 486 and now works with
a new mothe
13 matches
Mail list logo
