From owner-freebsd-questions@freebsd.org Tue Mar 15 17:00:27 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 98A47AD2697 for ; Tue, 15 Mar 2016 17:00:27 +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 5DF131330 for ; Tue, 15 Mar 2016 17:00:26 +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 1afrth-0002MF-I0 for freebsd-questions@freebsd.org; Tue, 15 Mar 2016 16:32:44 +0000 Received: from [81.109.74.232] (port=37225 helo=sd.swampdog) by titan.solardns.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.86_1) (envelope-from ) id 1afrth-001Iar-7A for freebsd-questions@freebsd.org; Tue, 15 Mar 2016 16:32:41 +0000 From: Guy Harrison To: freebsd-questions@freebsd.org Subject: dhcpd, iscsi and a raspberry pi Date: Tue, 15 Mar 2016 16:32:13 +0000 User-Agent: KMail/1.9.9 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201603151632.14124.gfh@swampdog.co.uk> X-AuthUser: swampdog X-Filter-ID: s0sct1PQhAABKnZB5plbIY0Wf8WMyPuXHU+XUfPiEwcD4Rd/h6nhaQ7ZruH71MWktHFHLxtsn9wx dKyKAPnphQR4+0K7G1KvSa5ZSxPOujd2vxpKI0nPnfcNMKzMVl0ZgZ/Tw6DoY/8c2+5B5/2kISDH pDYvAGz9SvCxHRSxuIbb9htmGaMvX8zqHZbv/ZiK92Y/11kvH4JBsRjPkhf9EC3breeaRmS0N1SH 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: Tue, 15 Mar 2016 17:00:27 -0000 HI Folks, I just wanted to check I'm getting correct behaviour 'cos I'm no expert on these things! I've built an iscsi enabled kernel for the raspberry pi (aka debian jessie) and the initrd is obtaining a first IP address then when the kernel proper boots a second IP address is obtained. Both are bound to eth0. [admin@sdvmf64dns ~/etc]$ dhcpd --version isc-dhcpd-V3.1.2p1 [admin@sdvmf64dns ~]$ uname -a FreeBSD sdvmf64dns.swampdog 8.2-RELEASE-p4 FreeBSD 8.2-RELEASE-p4 #1: Thu Oct 27 14:26:36 BST 2011 root@sdvmf64dns.swampdog:/usr/obj/usr/src/sys/GENERIC amd64 The problem is the second IP address is "known" in that 'nslookup' knows the pi name and so forth.. lease 192.168.1.45 { starts 4 2016/03/10 14:55:05; ends 4 2016/03/10 15:05:05; cltt 4 2016/03/10 14:55:05; binding state active; next binding state free; hardware ethernet b8:27:eb:0f:32:64; uid "\001\270'\353\0172d"; set ddns-rev-name = "45.1.168.192.in-addr.arpa"; set ddns-txt = "318788caec8944734a9e0c2fe418c9db6f"; set ddns-fwd-name = "pi05.swampdog"; client-hostname "pi05"; } ..whereas the first IP.. lease 192.168.1.53 { starts 3 2016/03/09 14:09:27; ends 3 2016/03/09 14:19:27; tstp 3 2016/03/09 14:19:27; cltt 3 2016/03/09 14:09:27; binding state free; hardware ethernet b8:27:eb:0f:32:64; } ..only appears the once, on boot. This is the IP address by which the iscsi target knows the pi and it expires! I was expecting the first *.53 IP to be inherited by the kernel rather than it go obtain the second *.45 IP address. Is correct? If so, what do I need to be doing to get that to happen? I've googled this to death and not encountered this precise problem. TIA Guy