From owner-freebsd-questions@freebsd.org Thu Mar 17 03:14:43 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C05FAAD3F33 for ; Thu, 17 Mar 2016 03:14:43 +0000 (UTC) (envelope-from gfh@swampdog.co.uk) Received: from mx1.solardns.com (mx1.solardns.com [109.73.127.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 836FC1068 for ; Thu, 17 Mar 2016 03:14:42 +0000 (UTC) (envelope-from gfh@swampdog.co.uk) Received: from titan.solardns.com ([213.129.84.167]) by mx1.solardns.com with esmtps (TLSv1.2:DHE-RSA-AES256-SHA:256) (Exim 4.85) (envelope-from ) id 1agONM-0007us-J5 for freebsd-questions@freebsd.org; Thu, 17 Mar 2016 03:13:30 +0000 Received: from [81.109.74.232] (port=37048 helo=sd.swampdog) by titan.solardns.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.86_1) (envelope-from ) id 1agONM-003rzK-53 for freebsd-questions@freebsd.org; Thu, 17 Mar 2016 03:13:28 +0000 From: Guy Harrison To: freebsd-questions@freebsd.org Subject: Re: dhcpd, iscsi and a raspberry pi Date: Thu, 17 Mar 2016 03:13:19 +0000 User-Agent: KMail/1.9.9 References: <201603151632.14124.gfh@swampdog.co.uk> <201603152316.33023.gfh@swampdog.co.uk> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201603170313.19785.gfh@swampdog.co.uk> X-AuthUser: swampdog X-Filter-ID: s0sct1PQhAABKnZB5plbIY0Wf8WMyPuXHU+XUfPiEwcD4Rd/h6nhaQ7ZruH71MWktHFHLxtsn9wx dKyKAPnphQR4+0K7G1KvSa5ZSxPOujd2vxpKI0nPnfcNMKzMVl0ZgZ/Tw6DoY/8c2+5B5/2kISDH pDYvAGz9SvCxHRSxuIZ7BYTbOVvf2gutSKwjkrz64tmbePOZicDE2cTpTraHqS3breeaRmS0N1SH eKK+UkYtlPa/1nUwnw/hoHgr71b/vCrJPmnnTHzVkpybMK7ZTSEhnb66958pLGInGdL26Gs7lfzu /tPONwh9XNOtDyHaCxAmFTLzJB9zUoZ7ZW57niXMjKy9q3SRj7Q2gxGEk++TEtSxjwHNYb/2LiS7 Aj0AWhTXYlwXE+/uHic0AZ4kmrFUBlt3lbnvUeKEYqy8QDYdQk7XGXTfKeB6w9EPnG9cwaEh4MHC ziS+7iGBWJgglPOW6bvL9DC431WlF1LxckxUtEzMQ8hG9MbEN0FihoziP1MA7ED7gs165rpid68f E6luiuQKW35wYye6nyYrkIlIr+mi9pmJxFJZniBtPSj46J1fhOzjF0b4LXcjJZ5lojV3tFdAoO2u Gco+Sc/igH4lkBSh9vJu6q0AAzXqBj9opKSnwxkGqROms5EUtztdTJjbPrNfgmP1oCYIL5fOtJM= X-Report-Abuse-To: spam@mx1.solardns.com X-Filter-Fingerprint: IFrWXGses7OKB5S5G8/dJdIz5bb8V0ykx8BnFBnunHBA3cTUQ1R++keuE7RDJ8Kg3RbMLUalw1oC mj99/u+Poh38tEMU4IgC4sNz49qn3HHnhRv/ZJ3kEy8bfiAr+Fb/UpndEJ0YoaLytXXo8BMTaVt0 ARHRi6XGuAluI1udprGClI6bm+u9ssQgM5AHe3Zacv4uJct5wtJvPpZ2dlBHCwDSxr3Vz+LJ/RhM 2JZ0ECN5dnq47RWft7iCyM9+PbHelB4qP9S6mTzNwoPraFy6ieiDqMHb2a0eZvGOvr7RaxKWGCKO us9nABr0Pk/4CplP X-Originating-IP: 213.129.84.167 X-SpamExperts-Domain: out.solardns.com X-SpamExperts-Username: 213.129.84.167 Authentication-Results: solardns.com; auth=pass smtp.auth=213.129.84.167@out.solardns.com X-SpamExperts-Outgoing-Class: ham X-SpamExperts-Outgoing-Evidence: Combined (0.00) X-Recommended-Action: accept X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Mar 2016 03:14:43 -0000 On Tuesday 15 March 2016 23:56:14 Matt Mullins wrote: > On Tue, Mar 15, 2016 at 4:16 PM, Guy Harrison wrote: > > On Tuesday 15 March 2016 22:41:10 Lowell Gilbert wrote: > > > Lowell Gilbert writes: > > > > I thought dhcpd would use MAC address if the client didn't provide > > > > anything else. I'll check if I get a chance. > > > > > > Confirmed. My dual-boot machine has no special settings in the > > > server's dhcp.conf, and gets the same address regardless of which OS > > > it's using. It even offers a different hostname on each OS. > > > > Cheers. It's beginning to look like it's the lack of client information > > from the first (initrd *.53) dhcp request that may be the cause. If > > that's the case then I can rule out.. > > > > ..and go figure out what how.. > > > > uid "\001\270'\353\0172d"; > > uid is the cause. DUID was added to dhcpv4 in RFC 4361, and a dhcpd > that understands the option will treat different DUIDs as separate > devices even if they have the same MAC address. > > You might want to remove "send dhcp-client-identifier = hardware;" > from your /etc/dhcp/dhclient.conf (or equivalent) on your Raspberry > Pi. The plot thickens. It would appear that option is commented out and even when I uncomment it, whatever I value I assign it, is ignored. Seems I'm now off looking for something which is overriding it elsewhere. Cheers for the help. Guy