From owner-freebsd-questions@FreeBSD.ORG Mon Jan 26 09:15:47 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42EE016A4CE for ; Mon, 26 Jan 2004 09:15:47 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31E4243D31 for ; Mon, 26 Jan 2004 09:15:46 -0800 (PST) (envelope-from jan.muenther@nruns.com) Received: from [212.227.126.160] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1AlAKv-0006QP-00; Mon, 26 Jan 2004 18:15:45 +0100 Received: from [212.202.43.212] (helo=ergo.nruns.com) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1AlAKv-00032d-00; Mon, 26 Jan 2004 18:15:45 +0100 Received: by ergo.nruns.com (Postfix, from userid 1001) id 6E26A6D4; Mon, 26 Jan 2004 17:42:58 +0100 (CET) Date: Mon, 26 Jan 2004 17:42:58 +0100 From: jan.muenther@nruns.com To: Mike Message-ID: <20040126164258.GA36365@ergo.nruns.com> References: <401542F2.8000309@pacbell.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <401542F2.8000309@pacbell.net> User-Agent: Mutt/1.4i X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:9a8a46f2b40f7808f7699def63624ac2 cc: freebsd-questions Subject: Re: Configuring IP address aliasing X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2004 17:15:47 -0000 Hello, > I found the reference to using the 255.255.255.255 netmask via Google, > however, I have Michael Lucas's book "Absolute BSD" and reference on > pages 103 & 104 (on IP aliasing) clearly show using the same netmask as > the real interface when creating IP aliases. This book is blatantly wrong then. Basically, the point is that the network route already exists and the network extension is already clear. So, you must use a non-conflicting netmask. The ifconfig manpage describes this as well, by the way. Cheers, J.