At 11:35 PM 12/22/98 -0700, Charles Shoemaker wrote:
>If your modem allows it, continue to do the chat login scripts. This
>works with some providers, not with others. Try dialling with
>minicom and see what happens.
>
I suppose pap comes from the MLPPP the modem tries to setup. I
haven't been able to do the chat login with the isdn modem.
>At one client site, the isdn modem (in my case, a 3Com IQConnect)
>worked with my isp, using chat, but not with the client's isp, using
>only pap. What I ended up doing was a final line in the chat script
>like this:
>#expect send
>CONNECT "\d\d\d"
>
>or, wait for the word CONNECT, then pause 3 seconds, then exit the
>script and let pppd try to negotiate the pap connection.
>
Tried both with no success. Here is my ppp info when a failure
occurs:
Dec 23 08:03:13 gw connect: Dialing system
Dec 23 08:03:14 gw connect: Connected
Dec 23 08:03:14 gw diald[22992]: Running pppd (pid = 23019).
Dec 23 08:03:14 gw pppd[23019]: pppd 2.2.0 started by root, uid 0
Dec 23 08:03:14 gw pppd[23019]: Using interface ppp0
Dec 23 08:03:14 gw pppd[23019]: Connect: ppp0 <--> /dev/ttyS0
Dec 23 08:03:16 gw pppd[23019]: Hangup (SIGHUP)
Dec 23 08:03:16 gw pppd[23019]: Modem hangup
Dec 23 08:03:16 gw pppd[23019]: Connection terminated.
Dec 23 08:03:16 gw pppd[23019]: Exit.
>You could also test the pap parameters with your analog modem. Just
>end the chat script after the connect dialogs. I hope this helps.
Good suggestion. I'll try running a while with the analog...
If it still doesn't work, it looks like I may have a bad isdn
modem.
Thanks for the help,
Stefen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
