From owner-freebsd-doc@FreeBSD.ORG Fri Feb 3 21:37:10 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DAE016A420 for ; Fri, 3 Feb 2006 21:37:10 +0000 (GMT) (envelope-from tom@ctors.net) Received: from hoboe2bl1.telenet-ops.be (hoboe2bl1.telenet-ops.be [195.130.137.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 080F943D58 for ; Fri, 3 Feb 2006 21:37:08 +0000 (GMT) (envelope-from tom@ctors.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by hoboe2bl1.telenet-ops.be (Postfix) with SMTP id A777C38094 for ; Fri, 3 Feb 2006 22:37:07 +0100 (CET) Received: from [192.168.1.102] (d51A46967.access.telenet.be [81.164.105.103]) by hoboe2bl1.telenet-ops.be (Postfix) with ESMTP id 8BE3038100 for ; Fri, 3 Feb 2006 22:37:07 +0100 (CET) Message-ID: <43E3E923.4030806@ctors.net> Date: Sat, 04 Feb 2006 00:37:07 +0100 From: Tom Van Looy User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: freebsd-doc@freebsd.org References: <43E3721F.70005@ctors.net> In-Reply-To: <43E3721F.70005@ctors.net> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Network Device Configuration --> wrong information X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2006 21:37:10 -0000 I forgot to mention that this is about the freebsd handbook point 2.9.1. Tom Van Looy wrote: > 2.9.1 Network Device Configuration > ... > Netmask > The address block being used for this local area network is a Class C > block (192.168.0.0 - 192.168.255.255). The default netmask is for a > Class C network (255.255.255.0). > > --> this is wrong and should be (192.168.0.0 - 192.168.0.255) for /24. > It's mixed up with the RFC1918 range I guess, maybe someone can fix it. > > regards > > Tom Van Looy >