From owner-freebsd-net@FreeBSD.ORG Tue Dec 2 19:09:04 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 CEAC91065677; Tue, 2 Dec 2008 19:09:04 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from mail.consult-scs.com (MAIL.CONSULT-SCS.COM [208.81.60.67]) by mx1.freebsd.org (Postfix) with ESMTP id B3D9F8FC1A; Tue, 2 Dec 2008 19:09:04 +0000 (UTC) (envelope-from vulture@netvulture.com) Received: from [127.0.0.1] (host77.netvulture.com [208.201.244.77]) (Authenticated sender: vulture@netvulture.com) by mail.consult-scs.com (Postfix) with ESMTPA id 5BE5D164248E; Tue, 2 Dec 2008 11:09:37 -0800 (PST) Message-ID: <493587D4.5000400@netvulture.com> Date: Tue, 02 Dec 2008 11:09:08 -0800 From: Jonathan Feally User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-net@freebsd.org, freebsd-stable@freebsd.org References: <4933A00E.7080201@netvulture.com> <4934C733.4020506@netvulture.com> <49357329.9000107@netvulture.com> In-Reply-To: <49357329.9000107@netvulture.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SCS-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: 5BE5D164248E.4F48C X-SCS-MailScanner: Found to be clean X-SCS-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-204.399, required 4, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60, INIT_RECVD_OUR_AUTH -200.00) X-SCS-MailScanner-From: vulture@netvulture.com Cc: 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 19:09:04 -0000 Jonathan Feally wrote: > I will try another em card in that server to confirm/rule out the nic > driver. I am seeing the same checksum number on both the source > machine, the dhcp server machine, and a 3rd windows xp machine > sniffing the traffic with etherreal/wireshark. The windows xp box is > running an intel nic as well, and those 0.0.0.0.67 -> > 255.255.255.255.68 packets as seen by the server do have the correct > checksum. After the nic test, if no change from one driver to the > other, then I'll try to un-patch the bpf.c change. > > At this point it is acting like the checksum offloading (which I did > disable on both the client and server) just isn't working. > > Will let you know. > > -Jon > > Danny Braniss wrote: Tried a add-in em0 card - intel pro/1000 XT server card - 82544E chip - no change. also tried with ifconfig em0 -rxcsum ifconfig em0 -txcsum dhclient em0 No change. Packets still received with bad IP checksum. Went back to bge0 now and reversed rev 178675 back to 172506 care of patch via http://svn.freebsd.org/viewvc/base/stable/7/sbin/dhclient/bpf.c?r1=172506&r2=178675&view=patch Also no change. So this change to dhclient doesn't seem to be the issue. >From looking at http://svn.freebsd.org/viewvc/base/stable/7/sbin/dhclient/ this patch I took out is 7 months old, and I had this system running on 7-STABLE just fine about as of about 2-3 weeks ago. So it must have been something else in the sys/net or sys/netinet. I do seem some changes that are 3 weeks old, 4 weeks, and 6 days for these directories on files that would effect the packet assembly. Authors are julian, rwatson, and bz. I'm going to look through these recent changes to try to find some that has to do with the checksum process. -Jon -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.