Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.bhp.com.au!mel.dit.csiro.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.eng.convex.com!hermes.oc.com!news.spss.com!uunet!in2.uu.net!news3.digex.net!digex.net!not-for-mail From: dcmyers@access4.digex.net (David Myers) Newsgroups: comp.unix.bsd.freebsd.misc Subject: pppd fails to dial modem Date: 23 Jan 1996 16:57:36 -0500 Organization: Express Access Online Communications USA: 800-969-9090 Lines: 36 Message-ID: <4e3lkg$2mh@access4.digex.net> NNTP-Posting-Host: access4.digex.net Can anybody help me understand why pppd (or, more precisely, the chat script I invoke on the pppd command line) fails to dial? Basically what happens is that the modem (a 28.8) seizes the line, so that I can hear dial tone, but then is quickly cut off. It never gets a chance to dial. The On-Hook and Carrier-Detect lights just go out. Is this a cabling problem? I know on Macintosh systems that I've configured (including Macs running MacBSD), you need a special high-speed serial cable to handle DTR/CTS. Do PCs also need special cables? Right now, I'm using a straight-through DB25-to-DB25 cable. All my chat script does is: "" AT OK atdt2539500 Figuring some kind of DTR or CTS transition is causing problems, I also tried a chat script that ignores DTR/CTS transitions, like: "" AT OK atdt&c0&d0dt2539500 Neither one works. Note, however, that if I manually connect to the port (cu -l /dev/cuaa1 -s 57600), I have no problem telling the modem to dial. Any help would be greatly appreciated. -David -- ________________________________________ David C. Myers dcmyers@access.digex.net