From owner-freebsd-questions@freebsd.org Tue Mar 15 17:52:59 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 8E8BAAD166B for ; Tue, 15 Mar 2016 17:52:59 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from bede.qeng-ho.org (bede.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fileserver.home.qeng-ho.org", Issuer "fileserver.home.qeng-ho.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1D5551319 for ; Tue, 15 Mar 2016 17:52:58 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2]) by bede.home.qeng-ho.org (8.15.2/8.15.2) with ESMTP id u2FHqZtq044868; Tue, 15 Mar 2016 17:52:35 GMT (envelope-from freebsd@qeng-ho.org) Subject: Re: dhcpd, iscsi and a raspberry pi To: Guy Harrison , freebsd-questions@freebsd.org References: <201603151632.14124.gfh@swampdog.co.uk> From: Arthur Chance Message-ID: <56E84BE3.7010009@qeng-ho.org> Date: Tue, 15 Mar 2016 17:52:35 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <201603151632.14124.gfh@swampdog.co.uk> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit 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:52:59 -0000 On 15/03/2016 16:32, Guy Harrison wrote: > > 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) You're asking about Debian, a Linux distro, on a FreeBSD mailing list. Not quite as bad as asking about Windows on a Mac OS list, but you'd be much better off find a Debian mailing list to ask on. Try looking here https://www.debian.org/MailingLists/ > 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 > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > -- Moore's Law of Mad Science: Every eighteen months, the minimum IQ necessary to destroy the world drops by one point.