From owner-freebsd-isp Wed Oct 22 09:20:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA08741 for isp-outgoing; Wed, 22 Oct 1997 09:20:42 -0700 (PDT) (envelope-from owner-freebsd-isp) Received: from tabby.kudra.com (gw.kudra.com [199.6.44.145]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA08732 for ; Wed, 22 Oct 1997 09:20:37 -0700 (PDT) (envelope-from robert@kudra.com) Received: (from robert@localhost) by tabby.kudra.com (8.8.6/8.6.12) id MAA01205 for freebsd-isp@freebsd.org; Wed, 22 Oct 1997 12:20:35 -0400 (EDT) From: Robert Sexton Message-Id: <199710221620.MAA01205@tabby.kudra.com> Subject: ijppp grief - instant hangup To: freebsd-isp@freebsd.org Date: Wed, 22 Oct 1997 12:20:34 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Howdy. I'm using ijppp with a USR sportster 33.6, connected to Com2 (16550A), at 57600. /dev/ttyd1 The port is not used for dial out. The port works great for shell use, but exhibits a strange behaviour when used with ppp. Everything works normally, except that whan you dial in after closing a session, you get an immediate hangup after connect. Dial in again, and everything is back to normal. Modem is set up with the usual stuff: cts/rts, &C1 &D2, E0 Q1. also -clocal, hupcl. Is mdmbuf appropriate? As another data point: when using ppp with ppp -direct, if you simply execute it, as opposed to exec'ing. Dropped carrier kills ppp, but not the shell. Just how is the sighup getting blocked? Thanks for any suggestions. -- Robert Sexton - robert@kudra.com, Cincinnati OH, USA There's safety in numbers... Large prime numbers. - John Gilmore