From owner-freebsd-questions  Sat Sep 27 17:29:31 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id RAA22978
          for questions-outgoing; Sat, 27 Sep 1997 17:29:31 -0700 (PDT)
Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA22973
          for <questions@FreeBSD.ORG>; Sat, 27 Sep 1997 17:29:26 -0700 (PDT)
Received: (from grog@localhost)
	by freebie.lemis.com (8.8.7/8.8.5) id JAA04848;
	Sun, 28 Sep 1997 09:59:18 +0930 (CST)
Message-ID: <19970928095918.25225@lemis.com>
Date: Sun, 28 Sep 1997 09:59:18 +0930
From: Greg Lehey <grog@lemis.com>
To: Kevin Keyser <keyser@clio.rice.edu>
Cc: questions@FreeBSD.ORG
Subject: Re: netstat -i for lo0
References: <9709270102.AA04983@clio.rice.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.81e
In-Reply-To: <9709270102.AA04983@clio.rice.edu>; from Kevin Keyser on Fri, Sep 26, 1997 at 08:02:26PM -0500
Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8250
Fax: +61-8-8388-8250
Mobile: +61-41-739-7062
WWW-Home-Page: http://www.lemis.com/~grog
Fight-Spam-Now: http://www.cauce.org
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Fri, Sep 26, 1997 at 08:02:26PM -0500, Kevin Keyser wrote:
> I am running 2.2.2R at home on a P5/60/PCI/EISA, 32M, Adaptec 2742,
> 3com 3c592.  OS/2 is on one SCSI disk, FreeBSD on the other, using
> OS/2's boot manager.
>
> I have been seeing some strange behavior in my "netstat -i" numbers
> for the loopback.  Each time I run "netstat -i", ipkts and opkts are
> incremented by 48.  Note that it does not matter how long or short I
> wait between invocations; the change is always 48, like running
> netstat causes it.  In the example below, the machine is otherwise
> *very* idle, no cron jobs other than the install defaults, and is
> the only node up on my net.

Sorry for the last message--finger trouble.

Gary Jennejohn suggested the correct answer: you're probably running a
name server on this system.  I get the same results on my machine with
netstat -i, but not with netstat -in:

$ netstat -bin |grep lo0
lo0   16384 <Link>                            4338     0     620116     4338     0     620116     0
lo0   16384 255&0x7f00000 127.0.0.1           4338     0     620116     4338     0     620116     0
$ netstat -bin |grep lo0
lo0   16384 <Link>                            4338     0     620116     4338     0     620116     0
lo0   16384 255&0x7f00000 127.0.0.1           4338     0     620116     4338     0     620116     0
$ netstat -bi |grep lo0
lo0   16384 <Link>                            4346     0     621184     4346     0     621184     0
lo0   16384 255&0x7f00000 localhost           4346     0     621184     4346     0     621184     0
$ netstat -bi |grep lo0
lo0   16384 <Link>                            4358     0     622739     4358     0     622739     0
lo0   16384 255&0x7f00000 localhost           4358     0     622739     4358     0     622739     0
$ netstat -bi |grep lo0
lo0   16384 <Link>                            4370     0     624294     4370     0     624294     0
lo0   16384 255&0x7f00000 localhost           4370     0     624294     4370     0     624294     0
$ netstat -bi | grep lo0
lo0   16384 <Link>                            4406     0     629471     4406     0     629471     0
lo0   16384 255&0x7f00000 localhost           4406     0     629471     4406     0     629471     0
$ netstat -bi | grep lo0
lo0   16384 <Link>                            4418     0     631026     4418     0     631026     0
lo0   16384 255&0x7f00000 localhost           4418     0     631026     4418     0     631026     0

Don't worry about the number of packets--that depends on your configuration.

Greg