Subject: RE: SUMMARY:- IPNAT problems
To: Manuel Bouyer <bouyer@antioche.lip6.fr>
From: Brett HALES <bhales@cmpmail.com>
List: tech-net
Date: 02/25/2001 09:35:34
Thanks Manuel,

I am now nat'ing away. Why can't ipnat change the state of
net.inet.ip.forwarding when it starts?

Cheers,

Brett


> On Sat, Feb 24, 2001 at 08:17:06PM +1030, Brett HALES wrote:
> > Hello,
> >
> > I am currently trying to get a machine to do what Linux did with IP
> > Masquerade.
> >
> > Initially I would like Machine A and Machine B to be able to talk to the
> > Internet via NAT on Machine C.
> >
> > I am running NetBSD 1.5 and have the below ipf.conf (IPFILTER) and
> > ipnat.conf (IPNAT) files configured. (That do not work)
> >
> > I do not want to at this stage specify a specific port for machine A or
> > machine B. Eg. If Machine A wanted to talk to 145.23.12.41 on
> port 6667 then
> > I want that to happen. I shall tinker with ipfilter latter to stop this.
> >
> > Can anybody help?
>
> Did you check that
> sysctl net.inet.ip.forwarding
> returns 1 ?
> If it returns 0, use:
> sysctl -w net.inet.ip.forwarding=1
> and things should work.
>
> --
> Manuel Bouyer <bouyer@antioche.eu.org>
> --
>