From owner-freebsd-questions Tue Oct 10 10:11:33 2000 Delivered-To: freebsd-questions@freebsd.org Received: from eeyore.local.dohd.org (d0030.dtk.chello.nl [213.46.0.30]) by hub.freebsd.org (Postfix) with ESMTP id 98A9237B66C for ; Tue, 10 Oct 2000 10:11:28 -0700 (PDT) Received: by eeyore.local.dohd.org (Postfix, from userid 1008) id D3639BB09; Tue, 10 Oct 2000 19:11:23 +0200 (MET DST) Date: Tue, 10 Oct 2000 19:11:23 +0200 From: Mark Huizer To: Doug Poland , ListServer FreeBSD Questions Subject: Re: Routing without ipfw? Message-ID: <20001010191123.A15021@dohd.cx> References: <39E24CC9.3BF9F219@i-clue.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from doug@polands.org on Tue, Oct 10, 2000 at 08:58:57AM -0500 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thanks for the response. I was attempting to get a > routing box working and I hadn't compiled firewall > options in the kernel yet. Since my box wasn't > routing I wasn't sure of the relationship between > natd and ipfw. Unfortunately, I'm still not routing > correctly. That's a different question. Yes, you need ipfw for natd. But ipfw is a loadable kernel module Mark > > > > > Doug Poland wrote: > > > > > > Greetings all, > > > > > > Can I route ip between interfaces ( ed0 --> ed1 ) without > > > ipfw? > > > > Yes. The simplest solution is to enable routing with /stand/sysinstall > > during installation. > > > > HTH > > -Christoph Sold > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message