*BSD News Article 21219


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!spool.mu.edu!olivea!news.bbn.com!hsdndev!nmr-z!andy
From: andy@dbe.mgh.harvard.edu (Andrew Wieckiewicz)
Subject: Re: help: modem dial-in getty not working [NetBSD 0.9]
Message-ID: <andy.748544558@nmr-z.mgh.harvard.edu>
Keywords: modem getty dialup
Sender: usenet@nmr-z.mgh.harvard.edu (User for USENET news postings)
Nntp-Posting-Host: abu.mgh.harvard.edu
Organization: Mass General Hospital
References: <CDLqMo.AKw@filetek.com>
Date: Mon, 20 Sep 1993 17:02:38 GMT
Lines: 25

jan@filetek.com (Jan Morales) writes:

>I'm running NetBSD 0.9 and I'm trying to get a dial-in line to work.
>I see getty come up but when I dial in I see nothing on the remote
>end.  I can tip on both ends and see characters when I type so I know
>the modems can talk.  I can also dial out on this modem with no trouble.

You don't say if the modem picks up the line.  If it doesn't, set it up
for hardware handshaking,  make sure you set the port "-clocal" before you
invoke getty (on 386bsd its: "stty -f /dev/tty01 -clocal").  
I also found it necessary to do "crtscts" on the port.

>ats0=1		[autoanswer after one ring]
>atq1		[disable responses]
>ate0		[disable echo]

You can use:
atc1
atd3
to enable proper DTR handling and hardware handshaking.

--
| Andrew Wieckiewicz		        
| andy@dbe.mgh.harvard.edu            
| Massachusetts General Hospital