From owner-freebsd-net@FreeBSD.ORG Tue Dec 2 06:53:41 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7DC321065679; Tue, 2 Dec 2008 06:53:41 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 0EF568FC08; Tue, 2 Dec 2008 06:53:40 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (Inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id mB26XjIm060326 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Dec 2008 17:03:45 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Tue, 2 Dec 2008 17:03:37 +1030 User-Agent: KMail/1.9.10 References: <4933A00E.7080201@netvulture.com> <4934C733.4020506@netvulture.com> In-Reply-To: <4934C733.4020506@netvulture.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4748134.Xn4Dr6lWPW"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200812021703.44935.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: freebsd-net@freebsd.org Subject: Re: dhclient doing DISCOVER with bad IP checksum - bge (7.1 show stopper??) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2008 06:53:41 -0000 --nextPart4748134.Xn4Dr6lWPW Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 02 December 2008 15:57:15 Jonathan Feally wrote: > Can someone please confirm or rule out my issue with dhclient sending > bad IP checksum packets. It would really suck if 7.1 was released with a > broken DHCP client. I had 7.1-PRE (early Octover) send out DHCP requests without issue, althoug= h I=20 don't have that system available now. It was using em card. I have a 7.0-STABLE system with an sk card from July that does DHCP request= s=20 just fine too.. I don't have any bge systems running 7 to test with though sorry.. Does it= =20 always give dud packets or just DHCP? Can you try another card in the clien= t? =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart4748134.Xn4Dr6lWPW Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBJNNbI5ZPcIHs/zowRAktgAJ407dx5bAwTyUNnfIGV0P6jEPPFkwCfQZWh CBeBrwgKBwnVY4FGljkCP2w= =87ln -----END PGP SIGNATURE----- --nextPart4748134.Xn4Dr6lWPW--