Hi
Now I understand how 'chat' knows which device the modem is (it was
something that eluded me for a while). Which in turn explains why my stand
alown 'chat' tests failed. I've since solved all my dialup problems
(though there are others: more posts from me :)
Thanx for all those that replied.
Paolo
On Wed, 16 Jun 1999, Clifford Kite wrote:
> On Wed, 16 Jun 1999, Paolo Supino wrote:
>
> |When I use 'cu'/'seyon'/'minicom' the modem works fine and every command
> |it receives it sends an echo back to the terminal. The script is a very
> |simple one: "chat -v '' ATZ OK ATDT5551234". The only thing syslog shows
> |is that it sends the ATZ and then expects an 'OK', but it times out,
> |alarms and fails.
>
> Chat was really made to use with pppd. Pppd will supply it with the modem
> device file that you specified as a pppd argument, and chat needs to know
> which device file to use. If all you aren't using pppd and chat but just
> execute the line you show above, then the ATZ never reaches the modem.
>
> You may be able to play with command line stuff by redirecting standard
> output:
>
> chat '' ATZ OK 'ATDTsomenumber;' OK < /dev/modem > /dev/modem
>
> This should dial and then disconnect. You can omit the `;' and it won't
> disconnect but then you'll need to use control-c to stop chat. Also don't
> assume that /dev/modem is automatically pointed at the device file your
> modem actually uses - although if minicom works there's a good chance
> that it is a link to the right one.
>
> ---
> Clifford Kite Not a guru. (tm)
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
