From owner-freebsd-net@FreeBSD.ORG Tue Apr 7 03:13:58 2015 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B2E4EF26 for ; Tue, 7 Apr 2015 03:13:58 +0000 (UTC) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 9DB4113A for ; Tue, 7 Apr 2015 03:13:58 +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 t373Dvej053477 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Mon, 6 Apr 2015 20:13:57 -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: <55234B74.5020506@rawbw.com> Date: Mon, 06 Apr 2015 20:13:56 -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: net@freebsd.org Subject: [BUG?] dhclient sends packets with source IP address that has been deleted Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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: Tue, 07 Apr 2015 03:13:58 -0000 I am observing what dhclient sends to the server. Source IP of the packet it sends is the previous DHCP lease. This address doesn't exist any more, because I manually deleted it with 'ifconfig em0 remove ' command. Yet, when I rerun dhclient, it takes this address from /var/db/dhclient.leases.em0 and sends the UDP packet with this non-existent IP as source address in IP header. This looks very weird to me, though I am not sure what the practical implications of this might be. My guess is that it is able to do this because it injects packets with bpf. Should this thing be fixed, or this is harmless? Some other host might have this IP address by the time dhclient runs, and this might cause confusion somewhere. 10.1 STABLE Yuri