Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!usenet.eel.ufl.edu!gatech!news.mathworks.com!fu-berlin.de!zrz.TU-Berlin.DE!news.tu-chemnitz.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Problem with PPPD dial script(s) Date: 9 Jul 1996 20:57:46 GMT Organization: Private BSD site, Dresden Lines: 39 Message-ID: <4ruh4a$5ho@uriah.heep.sax.de> References: <HUFF.96Jul7001252@sunspot.tiac.net> <4rrf2f$fg@anorak.coverform.lan> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E brian@awfulhak.demon.co.uk (Brian Somers) wrote: > This is one of the reasons I stopped using it. ijppp (prog: ppp) > is infinitely better - it dials, allows auto-connection, firewalling > etc. I'd advise this approach. > > When kermit exits, it closes the cua device and the driver drops DTR. > Your modem then drops carrier - a good default. You can configure ... Well, kermit is arguably not the best dialer for pppd. ;) Remember, chat(1) used to ship along with the pppd program. Wonder why? ;-) There's nothing wrong with using iijppp anyway, except one should also note that iijppp seems to be more buggy than pppd. Alas, it's even harder to find and fix the bugs, and i haven't seen the author of it around willing to fix them himself for a long time now. One of the bugs that bothered me quite some months ago led to an incompatibility between iijppp and the 2.1R (or was it post-2.1?) pppd. It turned out that iijppp continued to use predictor-1 compression even after an unsuccessful negotiation, for the sole reason that the CCP layer was still up (but without any matching compression protocol found). I eventually gave up searching for the bug in iijppp, and made pppd close down the CCP layer if no matching compression protocol has been found (which could not hurt either way). In case you wonder what i'm using myself: iijppp for client-side PPP (since it has demand-dialing and other interesting features), and pppd for server-side PPP (since it seems to be more robust, runs entirely in the kernel, and wouldn't benefit from iijppp's advantages in this case anyway). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)