From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 17:40:53 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 881BE1065676; Tue, 2 Dec 2008 17:40:53 +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 669E28FC20; Tue, 2 Dec 2008 17:40:53 +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 F3B8F1642485; Tue, 2 Dec 2008 09:41:25 -0800 (PST) Message-ID: <49357329.9000107@netvulture.com> Date: Tue, 02 Dec 2008 09:40:57 -0800 From: Jonathan Feally User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 References: <4933A00E.7080201@netvulture.com> <4934C733.4020506@netvulture.com> In-Reply-To: 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: F3B8F1642485.6C299 X-SCS-MailScanner: Found to be clean X-SCS-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-203.107, required 4, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60, INIT_RECVD_OUR_AUTH -200.00, MISSING_HEADERS 1.29) X-SCS-MailScanner-From: vulture@netvulture.com Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: dhclient doing DISCOVER with bad IP checksum - bge (7.1 show stopper??) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2008 17:40:53 -0000 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: >> 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've had many problems lately, but none involved checksum nor the dhcpd > (btw, I assume that you are seeing bad checksum on the receiving server) > could you add a nic to your PE1750? > > danny > > > >> Jonathan Feally wrote: >> >>> Sorry for the cross-post, but this could be either lists problem. >>> >>> I have 2 boxes running 7-STABLE as of 20081130, both i386 SMP. One is >>> running ISC DHCPD 3.0.x from recent ports, and the other dhclient from >>> make world. >>> >>> The server is refusing to answer the DISCOVER request, as it thinks >>> the IP checksum is wrong, which tcpdump also confirms. Other DHCP >>> clients are working fine on this network, so I do not believe it to be >>> the network, server or dhcpd. >>> >>> Server is running a 2 Port Intel card - em driver. >>> >>> Client is a Dell PE1750 with 2 onboard NIC's - bge driver. >>> >>> I have tried turning off both RXCSUM and TXCSUM on both the client and >>> server machines with no luck. I also tried the second NIC on the >>> server with the same result. >>> >>> This setup was working just a couple of weeks ago, and the only thing >>> that has changed is updating the src for a make world. PXE booting >>> this server does result in an IP being issued, so it is pointing >>> towards something new/changed in 7-STABLE. >>> >>> I have attached a 3 packet dump of the DISCOVER requests. >>> >>> Can anybody shed some light on this for me? >>> >>> Thanks, -Jon >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> freebsd-net@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >>> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> >> > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.