From owner-freebsd-net@FreeBSD.ORG Thu Aug 12 14:48:34 2004 Return-Path: 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 E057216A4CE; Thu, 12 Aug 2004 14:48:34 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EB1743D2F; Thu, 12 Aug 2004 14:48:34 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i7CEmSG3027758 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Aug 2004 17:48:29 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.12.11/8.12.11) id i7CEmVKa072747; Thu, 12 Aug 2004 17:48:31 +0300 (EEST) (envelope-from ru) Date: Thu, 12 Aug 2004 17:47:10 +0300 From: Ruslan Ermilov To: Robert Watson Message-ID: <20040812144710.GA72404@ip.net.ua> References: <20040812130917.GC24142@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J2SCkAp4GZ/dPZZf" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new cc: net@freebsd.org cc: Chris Stenton cc: FreeBSD Current Subject: Re: bad tcp cksum on outgoing packets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2004 14:48:35 -0000 --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 12, 2004 at 10:44:12AM -0400, Robert Watson wrote: >=20 > On Thu, 12 Aug 2004, Ruslan Ermilov wrote: >=20 > > On Thu, Aug 12, 2004 at 12:50:58PM +0100, Chris Stenton wrote: > > > I have just been doing some debugging on my 5.2.1 box and noticed that > > > outgoing tcp packets on the box are coming up with bad checksums on > > > tcpdump. I am using the nge interface. > > >=20 > > > Here is a sample output. > > >=20 > > > 12:44:29.458021 0:4:e2:10:60:83 0:c:6e:4e:a0:cc ip 82: > > > hawk.gnome.co.uk.ssh > kite.gnome.co.uk.2167: P [bad tcp cksum 9420!] > > > 2071:2099(28) ack 753 win 65535 (DF) [tos 0x10] (ttl 64, id 35623, l= en > > > 68, bad cksum 0!) > > >=20 > > > 12:44:29.642088 0:c:6e:4e:a0:cc 0:4:e2:10:60:83 ip 60: > > > kite.gnome.co.uk.2167 > hawk.gnome.co.uk.ssh: . [tcp sum ok] 753:753(= 0) > > > ack 2099 win 64956 (DF) (ttl 128, id 44852, len 40) > > >=20 > > >=20 > > > Any ideas whats going on as the packet does not seem to be resent? > > >=20 > > You don't have hardware checksums enabled, do you? I barely > > recall they are incompatible with bpf(4). >=20 > They're not incompatible per se, but if you're sniffing outgoing packets > and the network interface is calculating the checksum on send, BPF will > see a version of the packet before the checksum is calculated. If tcpdump > later attempts to verify the checksum, it still won't be calculated in the > copy it sees, and will whine. It was unclear to me in the above e-mail if > this was a tcpdump of packets on the wire (say, the receiver), or on the > sender before they hit the wire. >=20 That's what I meant exactly. Thanks for clarifying my thoughts. ;) Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --J2SCkAp4GZ/dPZZf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBG4LuqRfpzJluFF4RAn3aAJ9oicqVISg6gPjUf/3SIYDAcJ+MVQCfcczt ugfTVw+VylL/3OYDKTbjHIQ= =Ehy7 -----END PGP SIGNATURE----- --J2SCkAp4GZ/dPZZf--