From owner-freebsd-hackers Wed Aug 13 07:15:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA19170 for hackers-outgoing; Wed, 13 Aug 1997 07:15:04 -0700 (PDT) Received: from milo.cfw.com (milo.cfw.com [205.219.240.6]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA19165 for ; Wed, 13 Aug 1997 07:15:01 -0700 (PDT) Received: from RA26wb19.cfw.com by milo.cfw.com; (5.65v3.2/1.1.8.2/12Dec95-0403PM) id AA00194; Wed, 13 Aug 1997 10:15:57 -0400 Message-Id: <9708131415.AA00194@milo.cfw.com> From: "Paul Missman" To: Subject: Modem problem Date: Wed, 13 Aug 1997 09:53:39 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1008.3 X-Mimeole: Produced By Microsoft MimeOLE Engine V4.71.1008.3 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm having a problem with an internel modem which quits talking to the net after a period of heavy traffic. Is there a diagnostic which runs under FreeBSD that would put the modem into internal loopback and run data into and out of it for a long time? I'm trying to rule out the external net as the source of the problem. Thanks, Paul Missman