Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 Mar 2012 18:19:44 -0700 (PDT)
From:      Jeremy Chadwick <freebsd@jdc.parodius.com>
To:        FreeBSD-gnats-submit@FreeBSD.org
Subject:   conf/165956: periodic/daily/420.status-network should show dropped packets
Message-ID:  <20120312011944.67A53102C1E@icarus.home.lan>
Resent-Message-ID: <201203120130.q2C1UBQP002477@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         165956
>Category:       conf
>Synopsis:       periodic/daily/420.status-network should show dropped packets
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Mon Mar 12 01:30:10 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator:     Jeremy Chadwick
>Release:        FreeBSD 8.2-STABLE amd64
>Organization:
>Environment:
System: FreeBSD icarus.home.lan 8.2-STABLE FreeBSD 8.2-STABLE #0: Fri Feb 10 17:43:50 PST 2012 root@icarus.home.lan:/usr/obj/usr/src/sys/X7SBA_RELENG_8_amd64 amd64
>Description:
	Sorry if I got the Category wrong -- I can never remember what
	to choose for periodic scripts!

	The nightly periodic script for network interface statistics,
	daily/420.status-network, uses "netstat -in".  This is not the
	same as dropped packets caused by use of ipfw or pf; these types
	of dropped packets would be caused by Ethernet problems (cabling
	or NIC driver issues) or similar anomalies on that level.

	I propose that -d be added to the netstat flag list, to give more
	visibility into problems.
>How-To-Repeat:
	n/a
>Fix:
	Change periodic/daily/420.status-network as documented in
	Description.

>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120312011944.67A53102C1E>