Hi-
Being a newbie and trying to get diald with slip working, I changed this
and that until it worked but I didn't really understand what the heck I was
doing.
Then a roadblock when it came to ethertap. I kept getting an error that
read <terminal error, invalid argument> or something similar. I had seen on
this list that others were having the same problem. So I accepted this.
In using diald /slip my diald was using the contents of diald.conf as a
pointer to /etc/diald/connect as the modem script to interface to the modem.
When I modified conf.modules to work on ethertap, I assumed that diald was
in fact <still> using diald.conf as a pointer to /etc/diald/connect as the
modem script. This was found as not the case. Regardless of what I had in
diald.conf that pointed to my modem script, it did not use it.
When I changed my diald to use ethertap, it used another script. This
script was <not> setup correctly, therefore the error <terminal error,
invalid argument> Once I setup the <other> script correctly I no longer
received the terminal error when I switched to ethertap.
This <other> script that was being used when ethertap was activated in
conf.modules was at /etc/sysconfig/network-scripts/chat-ppp0 which in turn
looks at ifcfg-ppp0 <I think>..
I'm not saying that this fixes the terminal argument but in my case it
did. Hopefully it will allow others who also have the terminal argument
problem an avenue to check.
-Randall
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
