My bet would be that you shouldn't use plaintext login at all. Most ISPs use something similar to mgettys autoppp feature, to listen for PPP frames coming from the subscriber before presenting a login prompt. If you wait for the CONNECT string in the chat script, then bail back to pppd and give pppd a 'user' parameter matching that with your fathers passwords in /etc/ppp/pap-secrets, you might find an improvement. Below i've pasted the contents of debians /etc/chatscripts/pap Cheers James /etc/chatscripts/pap: # You can use this script unmodified to connect to sites which allow # authentication via PAP, CHAP and similar protocols. # This script can be shared among different pppd scripts. # To use it, add something like this to your /etc/ppp/peers/ file: # # connect "/usr/sbin/chat -v -f /etc/chatscripts/pap -T PHONE-NUMBER" # user YOUR-USERNAME-IN-PAP-SECRETS # noauth # Uncomment the following line to see the connect speed. # It will be logged to stderr or to the file specified with -r . #REPORT CONNECT ABORT BUSY ABORT VOICE ABORT "NO CARRIER" ABORT "NO DIALTONE" ABORT "NO DIAL TONE" "" ATZ OK ATDT\T CONNECT "" ----- Original Message ----- From: "Glenn Ramsey" <glenn(a)componic.co.nz> To: "Waikato Linux Users Group" <wlug(a)list.waikato.ac.nz> Sent: Tuesday, June 29, 2004 10:27 AM Subject: Re: [wlug] Trouble connecting linux to ValueNet
Thanks for all your suggestions. A few seemed promising but none worked. I was there yesterday and had a play with minicom and kppp and we did get it to connect and start ppp but it was very weird.
Here's what happens.
In minicom you get: atdt086733444 ... login: username password:<password>
now I'd expect to see something like ~(&*%$%*()&)&*%$&*%^ but nothing happens, it's as if the username/password is wrong, but it isn't. The ppp log also indicates that ppp is not starting when dialing with kppp.
Here's the weird thing: in kppp we put a Expect ~ / Send <nothing> in the chat script because that's what the howto said to do if it looks like ppp is taking a while to start up on the server. No go.
Then we took off the Send <nothing> and just had Expect <any old string>. This caused the chat script to time out waiting for the string and redial. On the second try it connects OK. If the connection is stopped and you try to reconnect then it does the same thing ie dials a second time and connects on the 2nd try.
The other puzzling thing is that it used to work fine and as far we know nothing had been changed. He currently has an internal Intel ham modem and I'm wondering if there is something going on with that, like an intermittant hardware failure. The next thing we are going try is an external modem.
Any more ideas?
g
-- Glenn Ramsey <glenn(a)componic.co.nz> 07 8627077 http://www.componic.co.nz
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug