From owner-freebsd-net@FreeBSD.ORG Wed Apr 8 22:38:51 2015 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D249468C; Wed, 8 Apr 2015 22:38:51 +0000 (UTC) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id BA94B394; Wed, 8 Apr 2015 22:38:51 +0000 (UTC) Received: from yuri.doctorlan.com (c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128]) (authenticated bits=0) by shell1.rawbw.com (8.14.9/8.14.9) with ESMTP id t38Mcn1Y087814 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 8 Apr 2015 15:38:50 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128] claimed to be yuri.doctorlan.com Message-ID: <5525ADF8.8020808@rawbw.com> Date: Wed, 08 Apr 2015 15:38:48 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: "J.R. Oldroyd" , Brooks Davis Subject: Re: [BUG?] dhclient sends packets with source IP address that has been deleted References: <55234B74.5020506@rawbw.com> <20150407145354.GA9746@spindle.one-eyed-alien.net> <20150408100349.31a74103@shibato> In-Reply-To: <20150408100349.31a74103@shibato> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-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: Wed, 08 Apr 2015 22:38:51 -0000 On 04/08/2015 01:03, J.R. Oldroyd wrote: > From RFC2131, section 4.1: > > DHCP messages broadcast by a client prior to that client obtaining > its IP address must have the source address field in the IP header > set to 0. > > Note the "must" there. > > So the current behavior looks like an error, to me. I suspected that this is the violation of DHCP specs. Many times I saw how FreeBSD to FreeBSD DHCP handshake is delayed without an apparent reason. I think this bug combined with another one when broadcast UDP packet isn't received when source IP is set is the cause of such DHCP delays. Yuri