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).
Federico
Randall wrote:
>
> > > chat: the same chat invokation that works when using the slip proxy
> > dies
> > > with the message "Can't get terminal parameters: Invalid argument"
> > when
> > > run using tap. The same problem occurs if I compile tap into the
> > kernel.
>
> Federico:
> I received the same message when first trying to get Tap working. Slip
> worked great. Found that my Slip was not using the same script that tap was
> trying to. Made the script work that Tap wanted to use and the error message
> went away.
> -Randall
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
