----- Original Message -----
From: Federico Heinz <[EMAIL PROTECTED]>
To: <unlisted-recipients:; (no To-header on input)>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, October 21, 1999 6:58 AM
Subject: Re: Using the tap device breaks chat??? (NOT the usual "can't
locate module" problem)
> Well, I don't think this is my problem. In my frantic debugging efforts, I
went
> as far as
>
> cd /usr/bin
> mv chat chat.orig
> cat >chat
> #!/bin/sh
> echo $* >>/tmp/chat-args
> ^D
> chmod +x chat
>
> and tried to connect. Of course, it didn't succceed, but after the attempt
> /tmp/chat-args did contain the correct arguments to dial my ISP. It looks
to me
> like diald dosen't set up chat's environment correctly when working with a
tap
> device. With environment I mean all of it stdin, stdout, etc, not just the
> environment strings (which, by the way, were correct---I checked).
After your attempt did you get the same error message ref bad arguments?
If you did, there must be something in the script that chat doesn't like. I
found that to setup chat script correctly I had to use linuxconf and setup
PPP/SLIP/PLIP.
This in turn setup chat-ppp0 and my line in diald.conf when using tap
reads as follows:
connect "/usr/sbin/chat -f /etc/sysconfig/network-scripts/chat-ppp0"
This may be a backwards way of doing things cause of my lack of experience
with linux but it did clear up the bad arguments error and then tap worked.
Below is my somewhat simple chat script.
'' 'AT&U29&N29'
'OK' 'ATDT*70,xxxxxxx'
'CONNECT' ''
'ogin:' 'xxxxxx'
'sword:' 'xxxxxx'
Hope that helps
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
