From owner-freebsd-current Wed Jun 28 21:30:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA07907 for current-outgoing; Wed, 28 Jun 1995 21:30:58 -0700 Received: from virgo.ai.net (root@virgo.ai.net [198.69.44.2]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA07901 for ; Wed, 28 Jun 1995 21:30:56 -0700 Received: from aries.ai.net (aries.ai.net [198.69.44.1]) by virgo.ai.net (8.6.11/8.6.12) with ESMTP id AAA00481; Thu, 29 Jun 1995 00:33:28 -0400 Received: (from nc@localhost) by aries.ai.net (8.6.11/8.6.12) id AAA05403; Thu, 29 Jun 1995 00:30:48 -0400 Date: Thu, 29 Jun 1995 00:30:48 -0400 (EDT) From: Network Coordinator To: FreeBSD-current users , Joerg Wunsch cc: FreeBSD-current users Subject: Re: Paul Richards: sysconfig routed setting In-Reply-To: <199506290344.FAA04362@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk > Right now i've been solving this running gated's on the gateways that > are going to forward RIP announcements to the ethernet, and have > routed -q's (listening-only routed's) on all non-gateway hosts, so > they can adjust their kernel routing tables as soon as some of the > external routes are being announced. Everything is working as > desired. > > I'm curious how to solve this withouth routed's. I would think you would solve this the way everyone else does. For packets that are local on the ethernet, send directly to that machine, if they are not, forward to one of the routers. Afterall, that's what a router is for. -Jerry.