From owner-freebsd-net@FreeBSD.ORG  Mon Aug 16 17:25:12 2010
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E3AB81065673;
	Mon, 16 Aug 2010 17:25:12 +0000 (UTC)
	(envelope-from yongari@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id D3B308FC08;
	Mon, 16 Aug 2010 17:25:12 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o7GHPCMj035132;
	Mon, 16 Aug 2010 17:25:12 GMT
	(envelope-from yongari@freefall.freebsd.org)
Received: (from yongari@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o7GHPCxs035128;
	Mon, 16 Aug 2010 17:25:12 GMT (envelope-from yongari)
Date: Mon, 16 Aug 2010 17:25:12 GMT
Message-Id: <201008161725.o7GHPCxs035128@freefall.freebsd.org>
To: eugenijusu@inbox.lv, yongari@FreeBSD.org, freebsd-net@FreeBSD.org,
	yongari@FreeBSD.org
From: yongari@FreeBSD.org
Cc: 
Subject: Re: kern/149497: [fxp] 8.1-release,
	problem with fxp driver [regression]
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Aug 2010 17:25:13 -0000

Synopsis: [fxp] 8.1-release, problem with fxp driver [regression]

State-Changed-From-To: open->closed
State-Changed-By: yongari
State-Changed-When: Mon Aug 16 17:24:31 UTC 2010
State-Changed-Why: 
Not a fxp(4) bug.
This issue was caused by a bug in ipfilter's checksum offloading
handling. Consumer grade fxp(4) controllers support simple RX
checksum offloading capability and fxp(4) started to use that
feature. However ipfilter's checksum offloading logic has a bug
such that it incorrectly computes checksum of received frame and
dropped the frame.
See the kern/106438 for more details and possible fix.
You can disable RX checksum offloading of fxp(4) as temporary
workaround.
#ifconfig fxp0 -rxcsum


Responsible-Changed-From-To: freebsd-net->yongari
Responsible-Changed-By: yongari
Responsible-Changed-When: Mon Aug 16 17:24:31 UTC 2010
Responsible-Changed-Why: 
Track.

http://www.freebsd.org/cgi/query-pr.cgi?pr=149497