From owner-freebsd-net@FreeBSD.ORG Tue Nov 7 20:20:02 2006 Return-Path: X-Original-To: freebsd-net@FreeBSD.ORG Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC80C16A40F for ; Tue, 7 Nov 2006 20:20:02 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02E4C43D70 for ; Tue, 7 Nov 2006 20:20:01 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (dapatm@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id kA7KJtOn073277; Tue, 7 Nov 2006 21:20:00 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id kA7KJsAm073276; Tue, 7 Nov 2006 21:19:54 +0100 (CET) (envelope-from olli) Date: Tue, 7 Nov 2006 21:19:54 +0100 (CET) Message-Id: <200611072019.kA7KJsAm073276@lurza.secnetix.de> From: Oliver Fromme To: freebsd-net@FreeBSD.ORG, amarat@ksu.ru In-Reply-To: <4550B6A1.9090207@ksu.ru> X-Newsgroups: list.freebsd-net User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 07 Nov 2006 21:20:00 +0100 (CET) Cc: Subject: Re: a very strange netstat output and problem when using transparent proxy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-net@FreeBSD.ORG, amarat@ksu.ru List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Nov 2006 20:20:02 -0000 Marat N.Afanasyev wrote: > bge0: flags=8843 mtu 1500 Ok, I also have a machine with bge(4) NIC within reach. I've had a look at it for similar symptoms (see below). > bge0 1500 00:50:45:5f:4f:78 2341018 799 3062828 > 0 0 799 is not good, but I wouldn't call it "huge amount of ierrs". Is that a typical number, or was that output taken before the problem (network freeze) appears? > % uptime > 7:34PM up 40 mins, 3 users, load averages: 0.14, 0.16, 0.08 Ok, 799 ierrs after 40 minuted uptime is definitely not good. :-) > Real IP address. I've already switched forward off and make squid listen > on 80 instead. Problem persists. OK, so it's a NIC problem, not IPFW-related. Here's output from my machine with bge(4) NIC: Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll bge0 1500 00:16:35:... 7808595 35 3451475 0 0 Uptime is 8 days, the machine is only moderately loaded, but gets quite some amount of NFS traffic (as a client). OS is FreeBSD 6.2-PRELELEASE as of October 19th. Whie 35 ierrs in 8 days isn't much, I think it still indicates a problem somewhere. It should really be 0. (I haven't experienced any freezes or other problems, though.) Maybe you should ask on the -stable mailing list for others with bge(4) NICs to check. It looks like a bug in the driver. Oh by the way, do you have polling enabled? Try to switch in on (if disabled) or off (if enabled) and check whether it improves the situation for you. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "File names are infinite in length, where infinity is set to 255 characters." -- Peter Collinson, "The Unix File System"