PPP Authentication problem

[Bill Thorsteinson]

Your login failed, and you are not getting PPP started
on the far end. You should get a series of writing, read
messages along with sending, recieved messages as
PPP negotiates the connection.

The log captures the authorization failed message from
login. Try skipping the login in the chat script, and
see if PPP comes up. If they are using autoPPP they
will switch to PPP if the see an LPC packet instead of
a login id.

[Bill Thorsteinson]

Sorry I didn't reply sooner.

It looks like you are getting failing to get or keep the
carrier. It could be a setting on the modem causing
CD or DTR to be toggled when the line comes up
and you leave command mode.

The SIGHUP shouldn't happen until you are shutting
the connection down. Either the connection is dropped
immediately, or there is a singaling problem between
the Modem and HP box.

You may need a specially wired cable for the Modem.
I haven't connected a modem to an HP box for a
long time, but last time I did I had to custom build
the cable.

The chat after the connect should have messages
about recieved PPP frames as well as the sent frames
It recognizes the hangup state and tries redialing.

[Enrico Venegoni]

Hi Bill,

in the last few days, I have tried other tests.

I have another login/passwd (lent by a friend) on another provider. With this one there isn't any problem. The authentication phase has success, I set DNS, routing and netscape. Than I'm in internet.

The curious thing, if I connect to this provider with "cu -l cul0p0" and insert login and passwd when request, I'm connect since the outputs on terminal are a few rows like this:

^H}#@!}!e} }<}"}&} }*} } }%}&})}/}?K}$}(@%} } }#h}'}"}(}"f+
...................
...................
...................

Ok, after this, I'm forced to hungup.

Instead with the other provider I have "Authentication failed" and login request still appears. This is exact behaviour like pppd.

How can be this?

-Enrico

[Daniel Depascale]

Forgive me if this is obvious but have you tried to change the authentication to other than CHAP.

In your other case, those strange lines received ~~ }#.!}.... are normal. Does your chat-script wait until they are received ? Or take into account possible extra lines (welcome or additional info messages) from your ISP provider ?

I hope you have worked it out by now and don't need this.

Dan