From owner-freebsd-bugs Thu May 24 19: 2:17 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from ns1.springwoodsys.com (ns1.springwoodsys.com [12.38.17.16]) by hub.freebsd.org (Postfix) with ESMTP id 4A5FC37B423; Thu, 24 May 2001 19:02:14 -0700 (PDT) (envelope-from bill@springwoodsys.com) Received: from hq4.hq.springwoodsys.com (nat32@n08h3032.ex-pressnet.com [24.239.31.32]) by ns1.springwoodsys.com (8.9.3/8.9.3) with ESMTP id WAA29936; Thu, 24 May 2001 22:07:49 -0400 (EDT) (envelope-from bill@springwoodsys.com) Message-Id: <200105250207.WAA29936@ns1.springwoodsys.com> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200105241706.f4OH6TF39843@hak.lan.Awfulhak.org> Date: Thu, 24 May 2001 22:02:08 -0400 (EDT) From: "Bill O'Connell" To: Brian Somers Subject: Re: bin/27283: netstat -i missing IPv4 input packet count for tu Cc: freebsd-gnats-submit@FreeBSD.ORG, "Josef L. Karthauser" , freebsd-bugs@FreeBSD.ORG, brian@FreeBSD.ORG Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org No, the IP address has not changed on any of the interfaces. And that wouldn't explain why ipkts is always zero for IPv4 on the tun interface. The tun interface is used by pipsecd, by the way. Bill On 24-May-01 Brian Somers wrote: > Hmm, I think I know what the problem is. > > Recently, the network traffic counters were changed so that they > count things on a per-ip basis. I'd guess that your tun interface > changed IP number and therefore lost all of the old packet counts. > > WRT the other interfaces, I can't say for sure. Maybe Joe (cc'd) can > comment on this - he did the changes :) Perhaps this is also due to > an IP number change.... I've just done some quick tests here, and it > looks as if just ifconfig'ing the interface with the same IP number > that it currently has will reset the traffic counts. This doesn't > sound good... > > Comments Joe ? > >> Yes, the link was definitely functional. And yes, now that you >> mention it, the IPv4 opkts -- as well as almost all of the IPv4 >> counts -- are too low. The only IPv4 count that could possibly be >> accurate is sis1 opkts, but all of the link-layer counts look good. >> >> As an aside, all of my other systems, from 3.2-RELEASE through >> 4.2-STABLE, have the same count for the link-layer and IPv4 rows >> under each column. Starting with 4.3, the code appears to have >> changed in terms of how packets are classified. I see the same thing >> on one of my 5.0-CURRENT boxes. > > -- > Brian > > Don't _EVER_ lose your sense of humour ! > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message