From owner-freebsd-current@FreeBSD.ORG Tue Oct 16 11:31:56 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CDFC16A41A for ; Tue, 16 Oct 2007 11:31:56 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.225]) by mx1.freebsd.org (Postfix) with ESMTP id 0D13B13C46A for ; Tue, 16 Oct 2007 11:31:55 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so1125058nzf for ; Tue, 16 Oct 2007 04:31:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=u7KMOJcADYVYfWOKSbDAgnIEndXSYBuG513I+szfSoM=; b=plOJNnns0Mddv4gveephR5cWiyUUABVvvKVr7vdrjzBhjmWTadNrko/v82Z+TZDnweK2RXKb5MhFihtcUfAf+3T8YfP4hF7l9CHyahqDPQ7deA9xTdd580Tx2tYAD/HVMc7/hJ18FSKmsNPTzboPr/E0QDyfvtn9p5WPyPWrZPw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=LQPzk61iHJbx42YMeHpccHZ6Q1eqi3fXL438mg5k4h14OPfeuf6JpQQvgJDYQlJxyuKlIm31i1azRufojnJ9pD+DlSC4klneewtEp5fRAmIs2dTuqPhkOicxbT1Rrut/K7vNrMs9H6PFhvMsv6q+BnLlYDRwfpt/bdj9tZte9YY= Received: by 10.114.124.1 with SMTP id w1mr8291214wac.1192534314588; Tue, 16 Oct 2007 04:31:54 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id k23sm10519062waf.2007.10.16.04.31.52 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 16 Oct 2007 04:31:53 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l9GBSFOr081468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Oct 2007 20:28:15 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l9GBSEo7081467; Tue, 16 Oct 2007 20:28:14 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 16 Oct 2007 20:28:14 +0900 From: Pyun YongHyeon To: Jelte Jansen Message-ID: <20071016112814.GE79351@cdnetworks.co.kr> References: <471490DF.7010609@NLnetLabs.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <471490DF.7010609@NLnetLabs.nl> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: re(4) checksum offload problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2007 11:31:56 -0000 On Tue, Oct 16, 2007 at 12:22:23PM +0200, Jelte Jansen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Hi, > > i'm seeing bad IP/UDP checksums on packets on a realtek gigabit network > card. Turning offloading off (ifconfig -txcsum) seems to make the > problem disappear. > > Attached are pcap files showing the bad checksums; the IP header is set > to 0x0000 and then TCP/UDP headers are wrong too. The machine in > question is on .99. These were taken on the host itself but i also see > them on the other machine. > > pciconf: > re0@pci0:1:8:0: class=0x020000 card=0xee221113 chip=0x816910ec rev=0x10 > hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8110SB Single-Chip Gigabit LOM Ethernet Controller' > class = network > subclass = ethernet > > Version: > $FreeBSD: src/sys/dev/re/if_re.c,v 1.95 2007/08/14 02:00:04 yongari E\ > xp $ > > Jelte Would you give me more information for your network configuration? Which host use re(4) driver? Which host was used to capture the traffic? If you see bad checksum messages on hosts with Tx checksum enabled driver it's quite normal to see bad checksummed frames. Hardware will insert computed checksum into the frame after bpf listeners see the frame. -- Regards, Pyun YongHyeon