From owner-freebsd-questions@FreeBSD.ORG  Fri Jan 21 07:28:02 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D2F9716A4CE
	for <freebsd-questions@freebsd.org>;
	Fri, 21 Jan 2005 07:28:02 +0000 (GMT)
Received: from knife.dreamhost.com (knife.dreamhost.com [66.33.219.6])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8DDB743D54
	for <freebsd-questions@freebsd.org>;
	Fri, 21 Jan 2005 07:28:02 +0000 (GMT)
	(envelope-from lists@tntluoma.com)
Received: from [192.168.2.2] (adsl-68-252-59-232.dsl.wotnoh.ameritech.net
	[68.252.59.232])
	by knife.dreamhost.com (Postfix) with ESMTP id C5B40E488D
	for <freebsd-questions@freebsd.org>;
	Thu, 20 Jan 2005 23:28:00 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v619)
Content-Transfer-Encoding: 7bit
Message-Id: <F790C2AB-6B7D-11D9-A085-000D93AD26C8@tntluoma.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: FreeBSD-Questions Questions <freebsd-questions@freebsd.org>
From: Timothy Luoma <lists@tntluoma.com>
Date: Fri, 21 Jan 2005 02:27:55 -0500
X-Mailer: Apple Mail (2.619)
Subject: mgetty force-init-chat
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jan 2005 07:28:03 -0000

(I am still trying to solve my "connected but can't get anywhere" 
dialin to FreeBSD problem)

Last time I connected but couldn't get anywhere, I believe this was the 
mgetty log:

01/21 01:52:55 yd0  mgetty: experimental test release 1.1.31-Jul24
01/21 01:52:55 yd0  check for lockfiles
01/21 01:52:55 yd0  locking the line
01/21 01:52:55 yd0  lowering DTR to reset Modem
01/21 01:52:56 yd0  send: \dATQ0V1H0[0d]
01/21 01:52:57 yd0  waiting for ``OK''
01/21 01:52:57 yd0  found action string: ``NO CARRIER''
01/21 01:52:57 yd0  init chat failed, exiting...: Invalid argument
01/21 01:52:57 ##### failed in mg_init_data, dev=ttyd0, pid=77061

So I'm wonder if I should use the "force-init-chat" with mgetty config.

All the examples I see say:

QUOTE:
To get the modem back into a "sane" state, you can use the 
force-init-chat chat sequence. The default setup will send the DLE ETX 
characters, to revive voice modems, then the (pause)+++(pause)ATH0 
sequence to pull the modem from data mode to command mode.
UNQUOTE

OK, that sounds great, but how to I use the default setup?  What is the 
force-init-chat line that I should use for 'default'?  I didn't see 
anything in the mgetty.conf file or in Google, except a lot of places 
quoting the above. It doesn't say how to use the default, or how to 
enter "pause" in the expect/send pairing, or how to send the DLE ETX 
characters

TjL