From owner-freebsd-questions@FreeBSD.ORG Tue Jul 23 08:26:32 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 57D459DE for ; Tue, 23 Jul 2013 08:26:32 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0CB8C202B for ; Tue, 23 Jul 2013 08:26:31 +0000 (UTC) Received: from [192.168.1.35] (mux.fjl.org.uk [62.3.120.246]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id r6N8QN3k000144 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 23 Jul 2013 09:26:24 +0100 (BST) (envelope-from frank2@fjl.co.uk) Message-ID: <51EE3E2C.2090203@fjl.co.uk> Date: Tue, 23 Jul 2013 09:26:20 +0100 From: Frank Leonhardt User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: dhcp server returns core dump when i define network with mask 8 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jul 2013 08:26:32 -0000 On 23/07/2013 09:03, jb wrote: > s m gmail.com> writes: > >> ... >> subnet 192.0.0.0 netmask 255.0.0.0 { >> range 192.0.0.1 192.255.255.255; > The 'range' denotes IP addresses that can be allocated to clients. > The IP 192.255.255.255 is a reserved broadcast address for the network. > jb > > It's definitely "bad idea" to try to use it, but it doesn't explain the core dump. Also, using DHCP to dish out addresses that don't belong to you AND aren't on a private network (as defined by IANA) will probably lead to trouble. Valid private address ranges are: 10.0.0.0 - 10.255.255.255 (private class A) 172.16.0.0 - 172.31.255.255 (private class B x 16) 192.168.0.0 - 192.168.255.255 (private class C x 256) Which block you use is really a matter of taste - classes haven't been used in routing for quite a while so you can consider them all as straight blocks but I (for one) still treat them as classed just to help me visualise what's what. For example, I'll use one class C per site to prevent conflicts over VPN. 192.0.0.0/24 addresses are allocated to real hosts on the wider internet, although IIRC some of the lower ones are reserved for use in documentation (like example.com) - is that where the idea came from?!? :-) Regards, Frank.