From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 19 15:10:06 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C98A16A49A for ; Fri, 19 Oct 2007 15:10:06 +0000 (UTC) (envelope-from ghelmer@palisadesys.com) Received: from magellan.palisadesys.com (magellan.palisadesys.com [192.188.162.211]) by mx1.freebsd.org (Postfix) with ESMTP id D0C8313C45D for ; Fri, 19 Oct 2007 15:10:05 +0000 (UTC) (envelope-from ghelmer@palisadesys.com) Received: from [172.16.2.242] (cetus.palisadesys.com [192.188.162.7]) (authenticated bits=0) by magellan.palisadesys.com (8.14.1/8.14.1) with ESMTP id l9JEoGaQ016345 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 19 Oct 2007 09:50:16 -0500 (CDT) (envelope-from ghelmer@palisadesys.com) Message-ID: <4718C43B.2040504@palisadesys.com> Date: Fri, 19 Oct 2007 09:50:35 -0500 From: Guy Helmer User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (magellan.palisadesys.com [192.188.162.5]); Fri, 19 Oct 2007 09:50:16 -0500 (CDT) X-Palisade-MailScanner-Information: Please contact the ISP for more information X-Palisade-MailScanner: Found to be clean X-Palisade-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (not cached, score=-3.799, required 6, ALL_TRUSTED -1.80, BAYES_00 -2.60, J_CHICKENPOX_53 0.60) X-Palisade-MailScanner-From: ghelmer@palisadesys.com Subject: Netgraph ng_bridge status message missing last three values? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Oct 2007 15:10:06 -0000 I'm diagnosing a system that uses the Netgraph ng_bridge node to bridge two Ethernet segments and the system seems to stop passing traffic at randomly-triggered points (somewhat annoying for a system half a world away behind a very restrictive firewall :-) I've installed a cron job to dump the Netgraph bridge status messages to a log file every few minutes. However, I've found that the ng_bridge status message looks like this: > ngctl msg bnet0: getstats 0 STATS=Rec'd response "getstats" (4) from "[10]:": Args: { recvOctets=474229151 recvPackets=3322699 recvMulticast=128640 recvBroadcast=105813 recvUnknown=2372 xmitOctets=516954216 xmitPackets=2968420 xmitMulticasts=8 xmitBroadcasts=339 } but to aid diagnosis I would really like to see several values that, according to ng_bridge.h, are in the stats structure, including recvRunts, recvInvalid, loopDrops, loopDetects, and memoryFailures. It looks like all the code is there to report the values of these variables, but I can't seem to find anything that is dropping these variables from ngctl's output. Any help is greatly appreciated, Guy -- Guy Helmer, Ph.D. Chief System Architect Palisade Systems, Inc.