From owner-freebsd-net@FreeBSD.ORG Thu Aug 12 13:10:41 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 7DF6116A4CE; Thu, 12 Aug 2004 13:10:41 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B573343D45; Thu, 12 Aug 2004 13:10:40 +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 i7CDAZQA017517 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Aug 2004 16:10:36 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.12.11/8.12.11) id i7CDAcm3024911; Thu, 12 Aug 2004 16:10:38 +0300 (EEST) (envelope-from ru) Date: Thu, 12 Aug 2004 16:09:17 +0300 From: Ruslan Ermilov To: Chris Stenton Message-ID: <20040812130917.GC24142@ip.net.ua> Mail-Followup-To: net@FreeBSD.org References: <1092311458.13121.6.camel@hawk.gnome.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5G06lTa6Jq83wMTw" Content-Disposition: inline In-Reply-To: <1092311458.13121.6.camel@hawk.gnome.co.uk> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new cc: FreeBSD Current cc: net@freebsd.org 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 13:10:41 -0000 --5G06lTa6Jq83wMTw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [Cc: freebsd-net] 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, len > 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). Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --5G06lTa6Jq83wMTw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBG2v9qRfpzJluFF4RArWxAKCYaNQSzY4GbX34pTfuYrx/sRIJ1wCfRRHJ 81zCPUKuIGlwNtRYrAdIJGI= =4GvF -----END PGP SIGNATURE----- --5G06lTa6Jq83wMTw--