Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!math.fu-berlin.de!fub!geminix.in-berlin.de!gemini
From: gemini@geminix.in-berlin.de (Uwe Doering)
Newsgroups: comp.unix.sysv386
Subject: Re: FAS 2.09 PROBLEMS
Message-ID: <650R8QP@geminix.in-berlin.de>
Date: 27 Jun 91 19:15:52 GMT
References: <1991Jun26.214742.18042@unixland.natick.ma.us>
Organization: Private UNIX Site
Lines: 31

bill@unixland.natick.ma.us (Bill Heiser) writes:

>I installed FAS209 a couple of days ago, and ahve been experiencing 
>problems.  Out-dialing seems to work OK most of the time, although
>I've experienced a number of "lost line" messages from UUCP.  
>
>Inbound calls seem to be experiencing difficulties -- now when someone
>calls in via uucp, for example, a couple of login banners appear, and
>then a string of bell characters (control-G's).  Then it just hangs 
>and times out.

This looks as if your modem throws some junk characters at getty,
which thereafter is too confused to let you log in. Are you sure
that your modem is quiet by default (`ATE0Q1')?

On the other hand, I've seen this behaviour myself when I dialed
up a _non_-MNP modem with an MNP modem. The MNP modem sends out
a test sequence to let the remote modem know that it wishes to
establish an MNP connection. This test sequence looks to a _non_-
MNP modem like a string of garbage characters, which it happily
passes to getty. getty then behaves the same way as you described.

Maybe something other than just FAS changed in your configuration
at the same time. All I can say is that I've never seen such
behaviour of FAS (or rather getty) without an external cause for it.

      Uwe
-- 
Uwe Doering  |  INET : gemini@geminix.in-berlin.de
Berlin       |----------------------------------------------------------------
Germany      |  UUCP : ...!unido!fub!geminix.in-berlin.de!gemini