--
Howard.
______________________________________________________
LANNet Computing Associates <http://www.lannet.com.au>
On Tue, 12 Dec 2000, Ian Ward wrote:
> try setting the debug option in the connect script.
Done that. That's how I saw what is going on.
>
> You might find the problem is timing. Sometimes, even though the prompt has
> been output, the system is just not ready to strart accepting characters and
> it misses the first couple of characters.
I'm begining to think this is the case.
>
> If the error in the log file says something like "Is the line looped?" then
> this is probably the cause, you are sending LCP's at the login prompt and it
> is echoing them back
Yes, I am certainly getting that.
>
> when I configure chat scripts that must login I *always* put a small delay
> before entering data.
>
> ie:
> 'OK' 'ATDT333'
> 'CONNECT' ''
> 'ogin:' '\dusername'
> 'word:' '\dpassword'
It seems to do this bit OK, but I think I am being to quick between this
point and the "server" actually firing up pppd and being ready to receive
LCP packets.
I shall have to go back to the man page, I seem to recall an option to
force the "client" to wait for the peer to send a packet before I start
sending.
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
