From owner-freebsd-isp Fri Sep 25 11:53:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19844 for freebsd-isp-outgoing; Fri, 25 Sep 1998 11:53:58 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19839 for ; Fri, 25 Sep 1998 11:53:56 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id NAA06304; Fri, 25 Sep 1998 13:52:39 -0500 (CDT) Received: from harkol-12.isdn.mke.execpc.com(169.207.64.140) by peak.mountin.net via smap (V1.3) id sma006300; Fri Sep 25 13:52:38 1998 Message-Id: <3.0.3.32.19980925135130.00774a48@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 25 Sep 1998 13:51:30 -0500 To: ulf@Alameda.net, Bill Vermillion , freebsd-isp@FreeBSD.ORG From: "Jeffrey J. Mountin" Subject: Re: Routing problem In-Reply-To: <19980925111651.D22112@Alameda.net> References: <3.0.3.32.19980925121618.00714074@207.227.119.2> <199809240148.VAA29188@bilver.magicnet.net> <360938BE.3569E424@eaznet.com> <199809240148.VAA29188@bilver.magicnet.net> <19980924150846.C24890@Alameda.net> <3.0.3.32.19980925121618.00714074@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:16 AM 9/25/98 -0700, Ulf Zimmermann wrote: >It is a valid netmask, but it wouldn't include 10.1.0.0/16 and 10.2.0.0/16 as >he wrote. Duh! Missread and for the odd numbered network. Guess this would be an example of network planning and boundaries. Planning ahead to simplify masking is something that seems to have been missed recently, if you follow all the talk about IPFW and long rulesets. Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message