DIP won't work together with diald. This does not mean you cannot use SLIP. Diald does the slip code by itself. The connect script is only needed to dial the remote site and send the appropriate commands to get it into slip or ppp mode. It must not attempt to manipulate the line discipline on the local end. Diald or pppd will take care of that. Get ``chat'' from the pppd distribution and use that to establish your connections.
Now, a slightly longer explanation about the conflicts between DIP and diald. Diald needs a program that can dial the remote site and negotiate the connection. DIP can do this. BUT, diald has a few more requirements. First, diald may try dial out on more than one serial line, it therefore starts up the connection program with its standard input and output connected to the serial line it chose. DIP cannot, as far as I can see deal with this, since you must explicitly set the device to use in the DIP script. Second, diald must own the controlling terminal on the serial line in order for pppd to work correctly. This appears to conflict with DIP which also tries to get the controlling terminal (at least in some versions of DIP). Finally, DIP will always try to lock the serial line it opens. This conflicts with diald's file locking.
Yes. See the ``bootp'' argument to the dslip-mode option.
Next Chapter, Previous Chapter
Table of contents of this chapter, General table of contents
Top of the document, Beginning of this Chapter