From owner-freebsd-questions Thu Apr 22 8:27:32 1999 Delivered-To: freebsd-questions@freebsd.org Received: from pokey.local.net (tcs7-51.netwalk.net [206.175.76.179]) by hub.freebsd.org (Postfix) with ESMTP id 10EA414D6C for ; Thu, 22 Apr 1999 08:27:29 -0700 (PDT) (envelope-from jmutter@netwalk.com) Received: from insomnia.local.net (insomnia.local.net [192.168.2.3]) by pokey.local.net (8.9.2/8.9.2) with ESMTP id LAA20405; Thu, 22 Apr 1999 11:24:06 -0400 (EDT) (envelope-from jmutter@insomnia.local.net) Date: Thu, 22 Apr 1999 11:26:48 -0400 (EDT) From: "James A. Mutter" Reply-To: jmutter@netwalk.com To: Dean Hollister Cc: FreeBSD Questions Subject: Re: pppd problems in 2.2.8 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :ppp links that have been established for some time, usually more than a :couple hours and often days, and the link is idle, results in :ping/traceroute times of 8-11 seconds. The problem does not appear :confined to one machine either, with two of our machines displaying the :problem. This must reduce the likelyhood of it being a hardware problem. : :The ppp links are across modems, and in the case of one machine, permanent :links/Members. I've never noticed a problem like that which couldn't be traced back to the hardware. I havn't purchased a modem in quite some time but... Some modems had a problem where they would train down (due to poor line quality) but wouldn't train back up when the line quality improved. I think that this _could_ explain your problem. Can you duplicate the problem under another OS? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message