From owner-freebsd-questions Wed Sep 16 18:29:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05994 for freebsd-questions-outgoing; Wed, 16 Sep 1998 18:29:07 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from ms1.dgsys.com (ms1.dgsys.com [204.97.64.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05721 for ; Wed, 16 Sep 1998 18:27:52 -0700 (PDT) (envelope-from jchill@dgsys.com) Received: from [192.168.0.3] (gueuze.dgsys.com [204.97.64.155]) by ms1.dgsys.com (8.8.7/8.7.3) with ESMTP id VAA26971; Wed, 16 Sep 1998 21:27:20 -0400 (EDT) X-Sender: jchill@pop.dgsys.com Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 16 Sep 1998 21:31:10 -0400 To: Val From: Chris Hill Subject: Re: bridging? Cc: FreeBSD Questions list Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Val wrote, >i know that freebsd can do ip routing, can it do bridging though so that i >would not have to subnet the network? > >If not, will freebsd do some NAT since the machines i need to connect to >the internet don't really nothing but access to the mail/www/telnet >servers? NAT works like a champ, and in fact I'm using it right now to mail this message. This is way cool - I'm paying for one real IP, yet I have a class C at home thanks to NAT. As far as I can tell, NAT is exactly what you need for your stated purposes. -- Chris Hill jchill@dgsys.com [place witty saying here] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message