From owner-freebsd-net@FreeBSD.ORG Wed Nov 14 10:14:02 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 83C46E27 for ; Wed, 14 Nov 2012 10:14:02 +0000 (UTC) (envelope-from dhartmei@insomnia.benzedrine.cx) Received: from insomnia.benzedrine.cx (106-30.3-213.fix.bluewin.ch [213.3.30.106]) by mx1.freebsd.org (Postfix) with ESMTP id B91EA8FC12 for ; Wed, 14 Nov 2012 10:13:59 +0000 (UTC) Received: from insomnia.benzedrine.cx (localhost.benzedrine.cx [127.0.0.1]) by insomnia.benzedrine.cx (8.14.1/8.13.4) with ESMTP id qAE9mu39010429 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Nov 2012 10:48:57 +0100 (MET) Received: (from dhartmei@localhost) by insomnia.benzedrine.cx (8.14.1/8.12.10/Submit) id qAE9muZl020126; Wed, 14 Nov 2012 10:48:56 +0100 (MET) Date: Wed, 14 Nov 2012 10:48:56 +0100 From: Daniel Hartmeier To: Sean Chittenden Subject: Re: 0.0.0.0/8 oddities... Message-ID: <20121114094856.GA19022@insomnia.benzedrine.cx> References: <50A20359.9080906@networx.ch> <7C614093-6408-49C6-8515-F6C09183453B@chittenden.org> <50A32FE7.2010206@rewt.org.uk> <7BE7E643-FB13-45DE-BA40-257B8ADFAA98@chittenden.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7BE7E643-FB13-45DE-BA40-257B8ADFAA98@chittenden.org> User-Agent: Mutt/1.5.12-2006-07-14 Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 10:14:02 -0000 On Tue, Nov 13, 2012 at 11:06:04PM -0800, Sean Chittenden wrote: > Where does it say that it shouldn't be used? Which RFC & ?? There are plenty of RFCs and I haven't exhaustively read things, so I reserve the right to be wrong & corrected, but I haven't seen anything that says, "do not use 0.0.0.0/8." 0.0.0.0/32, yes, that's a reserved and special IP address, but the remainder of the /8? It's a stretch to argue that it can't be used. RFC1122 Section 3.2.1.3 (which RFC5735 references directly) (a) { 0, 0 } This host on this network. MUST NOT be sent, except as a source address as part of an initialization procedure by which the host learns its own IP address. See also Section 3.3.6 for a non-standard use of {0,0}. (b) { 0, } Specified host on this network. It MUST NOT be sent, except as a source address as part of an initialization procedure by which the host learns its full IP address. So a sender MUST NOT use 0.0/16 or 0/8 as destination, ever... Daniel