From owner-freebsd-stable@FreeBSD.ORG Tue Mar 4 09:59:00 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 799D11065676 for ; Tue, 4 Mar 2008 09:59:00 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 740718FC24 for ; Tue, 4 Mar 2008 09:59:00 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 511FB1CC038; Tue, 4 Mar 2008 01:59:00 -0800 (PST) Date: Tue, 4 Mar 2008 01:59:00 -0800 From: Jeremy Chadwick To: "Chris H." Message-ID: <20080304095900.GC77655@eos.sc1.parodius.com> References: <200803040619.m246Jbja018523@drugs.dv.isc.org> <20080304000320.msp5bfrytc0wsowg@webmail.1command.com> <20080304095246.GA77655@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080304095246.GA77655@eos.sc1.parodius.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Edwin Groothuis , Mark Andrews , freebsd-stable@freebsd.org, Andy Dills Subject: Re: What's new on the 127.0.0/24 block in 7? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Mar 2008 09:59:00 -0000 On Tue, Mar 04, 2008 at 01:52:46AM -0800, Jeremy Chadwick wrote: > If you then put another box on the network as 192.168.1.7, and give it a > netmask of 255.255.255.128 (/25), it should not be able to see > 192.168.1.200. Broadcast packets from 192.168.1.7 would be going to > 192.168.1.128 (its "view" of the network would be 192.168.1.0 to > 192.168.1.128). And this is also wrong (off-by-one on the broadcast address). It should have read: > If you then put another box on the network as 192.168.1.7, and give it a > netmask of 255.255.255.128 (/25), it should not be able to see > 192.168.1.200. Broadcast packets from 192.168.1.7 would be going to > 192.168.1.127 (its "view" of the network would be 192.168.1.0 to > 192.168.1.127). This is what I get for handling two MPLS network outages at the same time while trying to write this mail. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |