Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!pmafire!mica.inel.gov!sixmile!jfp
From: jfp@INEL.GOV (Jeff Pack)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: Subnet 0
Message-ID: <1990Nov26.194015.8938@inel.gov>
Date: 26 Nov 90 19:40:15 GMT
References: <1120@soleil.UUCP>
Sender: news@inel.gov
Reply-To: jfp@INEL.GOV (Jeff Pack)
Organization: Idaho National Engineering Laboratory, Idaho Falls, Idaho
Lines: 40


In article <1120@soleil.UUCP>, gopstein@sisun1.squibb.com (Rich
Gopstein) writes:
|> zero is not legal in the subnetted portion of the address (ie the third
|> octet)...
|> 
|> This doesn't make sense to me.  Is there a reason that a zero in the
|> subnetted portion of the address will cause cisco routers a problem? 
|> 
|> 
You should be able to make the cisco recognize the zero subnet by adding
the following to the configuration:

    service subnet zero

As far as the legalities are concerned, the RFC's are a permissive
standard.  For example, most other vendors agree that broadcast is
all ones in the octet (i.e.; 255) but Sun configures their default
broadcast to be all zeros.  They say it depends how you interpret the RFC.
I think something similar is happening with subnet zero....

Jeff

---------------------------------------------------------------
Jeff Pack                         UUCP:  ...!uunet!inel.gov!jfp
Idaho National Engineering Lab    Internet:  jfp@inel.gov
P. O. Box 1625 M.S. 2603          Phone:  (208) 526-0007
Idaho Falls, ID 83415             FAX:  (208) 526-9936
========== long legal disclaimer follows, press n to skip ===========
^L
Neither the United States Government or the Idaho National Engineering
Laboratory or any of their employees, makes any warranty, whatsoever,
implied, or assumes any legal liability or responsibility regarding any
information, disclosed, or represents that its use would not infringe
privately owned rights.  No specific reference constitutes or implies
endorsement, recommendation, or favoring by the United States
Government or the Idaho National Engineering Laboratory.  The views and
opinions expressed herein do not necessarily reflect those of the
United States Government or the Idaho National Engineering Laboratory,
and shall not be used for advertising or product endorsement purposes.