From owner-freebsd-net Thu Aug 2 11:50: 6 2001 Delivered-To: freebsd-net@freebsd.org Received: from ringworld.nanolink.com (unknown [217.75.135.248]) by hub.freebsd.org (Postfix) with SMTP id B565137B406 for ; Thu, 2 Aug 2001 11:49:54 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 31979 invoked by uid 1000); 2 Aug 2001 18:48:41 -0000 Date: Thu, 2 Aug 2001 21:48:41 +0300 From: Peter Pentchev To: bstephens@regionsmortgage.com Cc: net@FreeBSD.org Subject: Re: Using FreeBSD server as a router?? Message-ID: <20010802214841.E11105@ringworld.oblivion.bg> References: <86256A9C.00636E33.00@smtp.regionsmortgage.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <86256A9C.00636E33.00@smtp.regionsmortgage.com>; from bstephens@regionsmortgage.com on Thu, Aug 02, 2001 at 12:57:09PM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Aug 02, 2001 at 12:57:09PM -0500, bstephens@regionsmortgage.com wrote: > > > I have been combing the freebsd.org site for the last two days > attempting to find some documentation on how to configure and use a > FreeBSD server as a router. I have found some information on > configuring the server as a bridge as well as a filtering bridge, but > no router info. Does anyone have any leads on some info? There seems > to be a number of such articles/books for doing a similar feet under > Linux, but I can't seem to find any such documentation for FreeBSD. I > have been wondering about using the filtering bridge scheme. It would > provide the segmentation of traffic that I need but does it provide > routing tables, shortest data path info, etc. as a router would? Any > assistance is appreciated. I believe this message belongs in -net. G'luck, Peter -- This sentence contains exactly threee erors. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message