Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!nrl-cmf!ames!amdahl!pacbell!att!cuuxb!fmcgee
From: fmcgee@cuuxb.ATT.COM (Netnews Administrator)
Newsgroups: comp.sys.att
Subject: Re: connecting 2400 modem to 3b2/310 in auto-answer
Summary: use /etc/gettydefs
Keywords: getty modems baud
Message-ID: <2680@cuuxb.ATT.COM>
Date: 3 Apr 89 03:32:22 GMT
Expires: 15 Apr 89 23:00:00 GMT
References: <16215@oberon.USC.EDU>
Reply-To: fmcgee@cuuxb.UUCP (Frank W. McGee)
Followup-To: comp.sys.att
Distribution: comp.sys.att
Organization: AT&T, Data Systems Group, Lisle, IL
Lines: 28

In article <16215@oberon.USC.EDU> ami@kodkod.usc.edu () writes:
>I am trying to connect a 2400 baud Hayes-compatible modem to
>a 3b2/310 running 3.2.2 -- and I am having a problem:

>I can originate calls (using cu, uucp, or manually via kermit) at 2400 baud
>But if I put a "getty" on the port, it echoes junk to the remote terminal.
>Issuing "break"s at the remote terminal does get it to cycle through the baud
>rates (I check it by sending a break on the sending port, and then running
>"stty </dev/ttyxx" on the receiving port), but it never logs the user in.

This is really strange; it *SOUNDS* like you have everything set up
okay, especially since the only thing that doesn't work on the port is
getty. 

>To start "getty" I have a script that (1) talks to the modem over the port (get
>it into answer-mode, cancel echo, etc.), (2) edits /etc/inittab to respawn
>"/etc/getty 2400 /dev/ttyxx" and (3) call "telinit q".

This is probably unnecessary.  You can set up a sequence of baud
rates that you'd like your tty's to go through as the calling process
sends BREAKS down the line.  It's described in gettydefs(4).  Any
particular reason you chose to do it this way ?

I'd also try uugetty if you have it.
-- 
Frank McGee, AT&T
Tier 3 Indirect Channel Sales Support
attmail!fmcgee