From owner-freebsd-questions  Tue Feb  3 13:02:36 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA02622
          for questions-outgoing; Tue, 3 Feb 1998 13:02:36 -0800 (PST)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02601
          for <questions@FreeBSD.ORG>; Tue, 3 Feb 1998 13:02:27 -0800 (PST)
          (envelope-from dwhite@gdi.uoregon.edu)
Received: from localhost (dwhite@localhost)
          by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id NAA13550;
          Tue, 3 Feb 1998 13:02:15 -0800 (PST)
          (envelope-from dwhite@gdi.uoregon.edu)
Date: Tue, 3 Feb 1998 13:02:14 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: "M. Monninger" <markem@primenet.com>
cc: questions@FreeBSD.ORG
Subject: Re: netstat -m
In-Reply-To: <3.0.5.32.19980201210854.0098aba0@pop.primenet.com>
Message-ID: <Pine.BSF.3.96.980203125508.13454G-100000@gdi.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe questions"

On Sun, 1 Feb 1998, M. Monninger wrote:

> Can someone explain (or point me to some info on) the values displayed by
> netstat -m?

Sure.  The number you are want to watch is this one:

32/194 mbuf clusters in use

Those numbers should never get closer than 3/4 of the total mubs in the
system.  I can't find the system default number, but you can set it using
`options "NMBCLUSTERS=xxx"' in your kernel config.  If that is hitting the
limt then strange network things can happen.

> I'm running FBSD 2.2.5 on a old 486 box, using it as a
> gateway/firewall between my home LAN and my xdsl line to my ISP. It's
> dedicated to that function...runs only natd and dhcpc, no users except for
> a console session via the serial port. It works very well except that every
> two or three days it locks up. No console messages or log messages, it just
> freezes, requiring a punch of the reset button. 

Check your memory out too, it could be bad.  Or your NIC is unhappy.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major