From owner-freebsd-isp  Fri Mar 14 01:12:37 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA08840
          for isp-outgoing; Fri, 14 Mar 1997 01:12:37 -0800 (PST)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id BAA08832;
          Fri, 14 Mar 1997 01:12:30 -0800 (PST)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA24358; Fri, 14 Mar 1997 10:12:24 +0100
Received: (from j@localhost)
	by uriah.heep.sax.de (8.8.5/8.8.5) id KAA28689;
	Fri, 14 Mar 1997 10:08:15 +0100 (MET)
Message-ID: <19970314100814.TS02670@uriah.heep.sax.de>
Date: Fri, 14 Mar 1997 10:08:14 +0100
From: j@uriah.heep.sax.de (J Wunsch)
To: adonai@jump.net (Lee Crites)
Cc: freebsd-isp@freebsd.org, hackers@freebsd.org
Subject: Re: How are you setting your modems????
References: <1.5.4.32.19970314065412.006970d4@jump.net>
X-Mailer: Mutt 0.60_p2-3,5,8-9
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
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
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <1.5.4.32.19970314065412.006970d4@jump.net>; from Lee Crites on Mar 14, 1997 00:54:12 -0600
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

As Lee Crites wrote:

> The closest thing to success I've had so far is with the cu command.  I'm
> doing something like:
> 
>   #cu -l /dev/cuaD00 dir
>   ATwhatever
>   ~.
> 
> I can see the lights on the modem blinking, but nothing shows up on the
> screen.

You must be close.  What exactly means `dir' in your command?  Also,
make sure to define the speed, e.g. by -s 57600.

For the rest, you probably need what we call over here ``Mäusekino'',
such a small gadget to monitor the V.24 lines.

> When I've used /dev/ttyD00 I get nothing back, and the ~. command
> doesn't work.

Have a look at the ps -alx output: you would have seen a "siodcd" as
the WCHAN.  Means its waiting for carrier to arrive (DCD).  That's the
normal way a getty works, it tries to open the ttyd device, and blocks
for carrier.

> I'm sort of getting the impression from some of the tidbits
> around that the ttyD device goes one way (in?) and the cuaD device goes the
> other way (out?).

You're totally right.  The cua devices are the ``callout units''.
They don't block on carrier (but interlock with the pending open on
the ttyd device, so the waiting getty won't get the device while you
are dialing out), and they behave similar to CLOCAL until the carrier
first arrived.  After this, they behave like -CLOCAL, thus you get a
SIGHUP when carrier drops.

-- 
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. ;-)