Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Oct 2000 14:38:55 -0500
From:      "Doug Poland" <doug@polands.org>
To:        "Ronald Klop" <ronald@klop.yi.org>
Cc:        "Mark Huizer" <freebsd-questions@freebsd.org>, <owner-freebsd-questions@freebsd.org>
Subject:   RE: Routing without ipfw?
Message-ID:  <NDBBKMNOJKJGAEKJNLIAIEHLELAA.doug@polands.org>
In-Reply-To: <Pine.BSF.4.21.0010102101020.766-100000@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> On Tue, 10 Oct 2000, Doug Poland wrote:
> 
> > >
> > >
> > > > 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.
> > > >
> > > > Doug
> > >
> > >
> > > That's a different question. Yes, you need ipfw for natd.
> > > But ipfw is a loadable kernel module
> > >
> > > Mark
> > 
> > So, logically, if you need natd for routing between interfaces,
> > and natd needs ipfw, then ipfw is required for routing.  Either
> > compiled into the kernel or as a lkm?
> > 
> > Confused,
> > Doug
> 
> No, not exactly. You need natd for Network Address Translation. Not for
> routing. You can do routing without nat and than you don't need ipfw.
> But for using natd you must have ipfw.
> 
> Don't forget: if you use the kernel module you don't have diverting
> enabled which is needed for natd. So you should compile your kernel with
> the option IPDIVERT. For ipdivert there is not yet a kernel module or
> sysctl as far as I know.
> 
> Greetings,
> 
> Ronald.
> 
> - -- 
> Ronald Klop                                        http://klop.yi.org/
> http://www.FreeBSD.org/                    http://klop.yi.org/~ronald/
> PGP: http://klop.yi.org/~ronald/pgp.txt
>      mailto:ronald@klop.yi.org?Subject=publicpgpkey
> 
>
Okay,

So in my futile effort to get "routing" working
between ed0 and ed1, all I should have to do is set

/etc/rc.conf  ... gateway_enable="YES"

and reboot.  So if it's not working, how can I 
diagnose and fix my machine's inability to route?

Frustrated but hopeful,
Doug




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?NDBBKMNOJKJGAEKJNLIAIEHLELAA.doug>