From owner-freebsd-isdn Wed Apr 28 1:51:27 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from brain.element-5.de (brain.element-5.de [195.185.111.1]) by hub.freebsd.org (Postfix) with ESMTP id AE1871562F for ; Wed, 28 Apr 1999 01:51:24 -0700 (PDT) (envelope-from pherman@element-5.de) Received: from brain.element-5.de (brain.element-5.de [195.185.111.1]) by brain.element-5.de (8.9.3/8.9.3) with ESMTP id KAA10785; Wed, 28 Apr 1999 10:51:11 +0200 (CEST) Date: Wed, 28 Apr 1999 10:51:11 +0200 (CEST) From: Paul Herman To: Dirk Meyer Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: i4b memory leak? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Paul Herman schrieb:, > > > ping returns "no buffers available" -- until I restart the computer, and > > then everything works fine for the next 15 days or so. > > ifconfig isp0 down > ifconfig isp0 up > > should fix this condition. I do this as cronjob every night: ifconfig isp0 down sleep 1; spppcontrol isp0 myauthname=$login myauthsecret=$pass ifconfig isp0 up to rotate dialup login accounts, but if it "locks up" like this, and I'm not around to reset the interface, then people get angry because they can't surf. :) Martin Husemann tipte anmütig ein: > It's a very old router tradition to simply drop packets if you can't > push them through, the queues in i4b are there only to help for the > one or two seconds while establishing the link, they could be pruned > on a regular basis. Good idea. If that's the case in i4b, then this should be fixed. Paul Herman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message