From bfeldman@rex.vetinsite.net  Mon Oct 10 06:32:27 2005
Return-Path: <bfeldman@rex.vetinsite.net>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6236916A41F
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 10 Oct 2005 06:32:27 +0000 (GMT)
	(envelope-from bfeldman@rex.vetinsite.net)
Received: from rex.vetinsite.net (36.f8bed1.client.atlantech.net [209.190.248.54])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 06B2843D48
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 10 Oct 2005 06:32:26 +0000 (GMT)
	(envelope-from bfeldman@rex.vetinsite.net)
Received: from rex.vetinsite.net (bfeldman@localhost.vetinsite.net [127.0.0.1])
	by rex.vetinsite.net (8.13.4/8.13.4) with ESMTP id j9A6WQ6V003699
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 10 Oct 2005 02:32:26 -0400 (EDT)
	(envelope-from bfeldman@rex.vetinsite.net)
Received: (from bfeldman@localhost)
	by rex.vetinsite.net (8.13.4/8.13.4/Submit) id j9A6WQgI003698;
	Mon, 10 Oct 2005 02:32:26 -0400 (EDT)
	(envelope-from bfeldman)
Message-Id: <200510100632.j9A6WQgI003698@rex.vetinsite.net>
Date: Mon, 10 Oct 2005 02:32:26 -0400 (EDT)
From: Brian Fundakowski Feldman <green@freebsd.org>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: fxp(4) promiscuous mode seems to corrupt hw-csum
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         87194
>Category:       kern
>Synopsis:       [fxp] fxp(4) promiscuous mode seems to corrupt hw-csum
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    yongari
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 10 06:40:10 GMT 2005
>Closed-Date:    Wed Jun 24 00:38:44 UTC 2009
>Last-Modified:  Wed Jun 24 00:38:44 UTC 2009
>Originator:     Brian Fundakowski Feldman
>Release:        FreeBSD 6.0-RC1 i386
>Organization:
>Environment:
System: FreeBSD rex.vetinsite.net 6.0-RC1 FreeBSD 6.0-RC1 #2: Sun Oct 9 21:16:52 EDT 2005 root@:/usr/obj/usr/src/sys/REX i386

fxp0: <Intel 82551 Pro/100 Ethernet> port 0xcc00-0xcc3f mem 0xfe6fe000-0xfe6fefff,0xfe6a0000-0xfe6bffff irq 17 at device 1.0 on pci3
miibus0: <MII bus> on fxp0
fxp0: Ethernet address: 00:04:23:b3:37:55
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=b<RXCSUM,TXCSUM,VLAN_MTU>
	inet6 fe80::204:23ff:feb3:3755%fxp0 prefixlen 64 scopeid 0x2 
	inet ...
	ether 00:04:23:b3:37:55
	media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
>Description:
	When turning promiscuous mode on, e.g. with bridging, the
	tcpdump output for every packet shows an invalid checksum.
	Now, this is not that strange in the face of hardware
	checksumming, but the interface is also unusable in some
	unknown capacity -- some things seem to work, other things
	don't.  I don't know whether packets are not being sent
	or they're being sent with actual bad checksums.
>How-To-Repeat:
	1. Set up a local caching named.
	2. dig in a www.freebsd.org (succeeds)
	3. dig @localhost in a www.freebsd.org (succeeds)
	4. turn on promisc, e.g. "ifconfig bridge0 addm fxp0 up"
	5. attempt 2. and 3. with various domains.  2. seems to succeed
	   in general, but 3. always fails.  There isn't much of a difference
	   between what the libc resolver and BIND9 send out, but it's
	   enough of a difference that it demonstrates the problem with
	   no effort (here).
>Fix:
	It would be nice to be able to disable the hardware checksumming,
	but that is not implemented.
>Release-Note:
>Audit-Trail:

From: Kris Kennaway <kris@obsecurity.org>
To: Brian Fundakowski Feldman <green@FreeBSD.org>
Cc: FreeBSD-gnats-submit@FreeBSD.org
Subject: Re: kern/87194: fxp(4) promiscuous mode seems to corrupt hw-csum
Date: Tue, 11 Oct 2005 05:33:27 -0400

 tcpdump on another machine and see what the packets actually are.  If
 your NIC is doing hardware checksumming, it's expected that tcpdump
 will not see it, and so will conclude the checksums are bad.
 
 Kris
Responsible-Changed-From-To: freebsd-bugs->freebsd-net 
Responsible-Changed-By: vwe 
Responsible-Changed-When: Wed Jan 14 21:36:45 UTC 2009 
Responsible-Changed-Why:  

Over to maintainer(s). 

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

From: Tom Judge <tom@tomjudge.com>
To: bug-followup@FreeBSD.org, green@freebsd.org
Cc:  
Subject: Re: kern/87194: [fxp] fxp(4) promiscuous mode seems to corrupt hw-csum
Date: Wed, 14 Jan 2009 19:22:17 -0600

 Can you add the output of ifconfig bridge0 as if_bridge should downgrade 
 the active hardware features to match the other members in the bridge.
 
 Also have you tried "ifconfig fxp0 -txsum -rxsum" to disable the 
 hardware checksumming?
 
 I have a number of bridges with all fxp members working fine under 6.2 
 and 7.0 do you still have these problems on a newer release than 6.0?
 
 Tom
 
State-Changed-From-To: open->feedback 
State-Changed-By: yongari 
State-Changed-When: Tue Jun 23 07:55:36 UTC 2009 
State-Changed-Why:  
I guess you came across old bug of bridge(4) which it failed to 
disable Tx checksum offloading when one of member interface of a 
bridge can't handle Tx checksum offload. I believe that bug was 
fixed long time ago. Does this still problems on newer releases? 


Responsible-Changed-From-To: freebsd-net->yongari 
Responsible-Changed-By: yongari 
Responsible-Changed-When: Tue Jun 23 07:55:36 UTC 2009 
Responsible-Changed-Why:  
Grab. 

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

From: Brian Fundakowski Feldman <green@freebsd.org>
To: bug-followup@freebsd.org
Cc:  
Subject: Re: kern/87194: [fxp] fxp(4) promiscuous mode seems to corrupt
	hw-csum
Date: Tue, 23 Jun 2009 12:28:16 -0400

 I am no longer working at the company that had those systems so I cannot
 check to see if the problem was fixed; my apologies.
 
 -- 
 Brian Fundakowski Feldman                           \'[ FreeBSD ]''''''''''\
   <> green@FreeBSD.org                               \  The Power to Serve! \
  Opinions expressed are my own.                       \,,,,,,,,,,,,,,,,,,,,,,\
State-Changed-From-To: feedback->closed 
State-Changed-By: yongari 
State-Changed-When: Wed Jun 24 00:37:35 UTC 2009 
State-Changed-Why:  
green@ has no more access to the system. I believe the bug was 
fixed in r154336 and revised again in r180220. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=87194 
>Unformatted:
