From owner-freebsd-current Mon Jun 23 11:30:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA20377 for current-outgoing; Mon, 23 Jun 1997 11:30:04 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA20363 for ; Mon, 23 Jun 1997 11:30:00 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA01042; Mon, 23 Jun 1997 11:18:33 -0700 From: Terry Lambert Message-Id: <199706231818.LAA01042@phaeton.artisoft.com> Subject: Re: getty modem control To: adam@veda.is (Adam David) Date: Mon, 23 Jun 1997 11:18:33 -0700 (MST) Cc: terry@lambert.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199706212233.WAA19957@veda.is> from "Adam David" at Jun 21, 97 10:33:03 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Typically, command interchange with a modem does not involve data > > exchanges larger than the buffer size. The CTS/RTS should not be > > required until DCD is high, and thus the modem is doing data, not > > command, interchange. > > > > Typically, the symptoms are "no data back from modem until DCD > > is present". If you can't change the modem settings, then you > > will be limited to blind-dialing in all cases. > > I can cu the device and get a normal response without carrier present. > However, getty times out trying to send the data, with no flicker on the > modem TXD. I assume this is your modified getty, since regular getty doesn't send data, right? Look at how 'cu' opens the port. Pay special attention to the CLOCAL and HUPCL settings. Note that you MUST be -CLOCAL, HUPCL for correct dial-in operation (ie: a modem hangup without logout sends SIGHUP to all processes in the process group to cause a logout, and logging out drops DTR to modem to cause it to disconnect). Talking to the modem from getty is evil. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.