From owner-freebsd-questions Tue Apr 15 12:12:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA00634 for questions-outgoing; Tue, 15 Apr 1997 12:12:40 -0700 (PDT) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA00625 for ; Tue, 15 Apr 1997 12:12:37 -0700 (PDT) Received: from harlie.bfd.com (bastion.bfd.com [204.160.242.14]) by horst.bfd.com (8.8.5/8.7.3) with SMTP id MAA03808; Tue, 15 Apr 1997 12:12:16 -0700 (PDT) Date: Tue, 15 Apr 1997 12:12:15 -0700 (PDT) From: "Eric J. Schwertfeger" To: Alec Kloss cc: Guy Helmer , freebsd-questions@FreeBSD.ORG Subject: Re: Subnets of all 0's/all 1's In-Reply-To: <199704151739.MAA25341@d2si.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 15 Apr 1997, Alec Kloss wrote: > > Should FreeBSD be able to support a network with a subnet of all zeros or > > all ones? If not, could someone give a short technical explanation as to > > why? > I did not know that this isn't allowed. I checked things out and RFC > certainly does imply that this is a no-no. In RFC 950, RFC 943 this > referenced as justification for this. RFC does not seem to use > imperitive language (you shall or you must) but something much less > harsh, as in > "When called for, the address zero is to be interpreted as > meaning "this", as in this network." Hmmm.... had a URL for a page at 3-com that had a wonderful writeup on this, and many other IP addressing issues, sort of an "everything you ever wanted to know and were afraid to ask" document, and it points to this restriction being because of one of the more primitive dynamic routing protocols being unable to handle these two cases. It also says that this restriction was depreciated, but I can't remember where or when. I was actually more surprized to find out you're supposed to have all subnets equal size. Unfortunately, Cisco's try to enforce both of these rules (or at least the 2501 we have does). On the other hand, our Linux firewall and the FreeBSD machines here (give me time, I want to convert it all to FreeBSD, but haven't had time to evaluate the FreeBSD equivilents of masquerading yet) talk to subnets that violate both rules. Ah, found it: http://www.3com.com/nsc/501302.html