From owner-freebsd-questions Tue Dec 23 14:13:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA14262 for questions-outgoing; Tue, 23 Dec 1997 14:13:40 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from milehigh.denver.net (milehigh.denver.net [204.144.180.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA14253 for ; Tue, 23 Dec 1997 14:13:32 -0800 (PST) (envelope-from jdc@milehigh.denver.net) Received: (from jdc@localhost) by milehigh.denver.net (8.8.8/8.8.8) id PAA23963; Tue, 23 Dec 1997 15:14:02 -0700 (MST) Message-ID: <19971223151401.62678@denver.net> Date: Tue, 23 Dec 1997 15:14:01 -0700 From: John-David Childs To: freebsd-questions@freebsd.org Subject: Re: Multiple class C's on the same wire References: <97Dec15.120334est.6182@netgate.iectech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79 In-Reply-To: ; from Doug White on Mon, Dec 22, 1997 at 10:17:13PM -0800 Organization: Enterprise Internet Solutions Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Monday December 22, 1997, Doug White had this to say about "Re: Multiple class C's on the same wire": > On Mon, 15 Dec 1997, Chris Peltier wrote: > > > > > Hi there, [Explanation of setting up multiple class /32's on an Ethernet interface deleted] > > Some other FreeBsd > > machines on the original Class C started complaining about > > hosts not on the network (I guess they didn't understand some > > of the arp messages about the new class C on the same wire). > > They complained but operated without any problems. Yup...probbly because of the gateway on the first machine they were able to route to the new class C even if it wasn't "by the book". > > Livingston Portmasters on the other hand were a mess. All the > > arp table entries (on the freebsd boxes) for the Livingstons were ARP is classful...thus, as Doug White (in one of his dizzying spells of helpfulness :-) wrote > > Everyone's netmasks *MUST* match. Period. > The solution: either turn off routed completely and use STATIC routes everywhere (including to/from the networks used by the PM's) or use OSPF. I chose the first method for a long time until I finally understood enough and had a spare late-night moment or two (so few customers would be inconvenienced) to implement OSPF. -- John-David Childs (JC612) Enterprise Internet Solutions System Administrator @denver.net/Internet-Coach/@ronan.net & Network Engineer 1031 S. Parker Rd. #I-8 Denver, CO 80231 As of this^H^H^H^H next week, passwords will be entered in Morse code.