Re: 2.2.x and IPMasq/ipportfw

Aaron Lehmann (aaronl@vitelus.com)
Sun, 24 Jan 1999 21:09:04 +0000 ( )


yep, my mistake. port forwarding is included but experimental, so
CONFIG_EXPERIMENTAL (?) has to be enabled.

KeyID 1024D/73348CA0
Fingerprint 8EFC 7F10 F26C 55A8 458A 38B0 890F 384F 7334 8CA0
Public key available at http://www.vitelus.com/aaronl/pubkey.asc

On Sun, 24 Jan 1999, Matthew Kirkwood wrote:

> On Sun, 24 Jan 1999, Aaron Lehmann wrote:
>
> > I am considering upgrading to 2.2.0 in a few days. The CHANGES file has
> > done a great job at scaring me.
> >
> > I use this machine as an IPMasqurading router. According to the ChangeLog,
> > ipfwadm will break. :(. That stinks. I'll have to upgrade to IPChains, but
> > the site appars to be down.
>
> Or has firewalled you out :)
>
> If you're prepared to miss out on the extra flexibility (and speed) of
> ipchains, you can just drop the ipfwadm-wrapper over your ipfwadm binary
> and leave it at that..
>
> > I don't see an IP: Masqurading option in the kernel anymore. What happened
> > to that? Is it unnecesary with IPChains?
>
> Nope. You have to enable "IP: Always defragment" as well as the usual
> options (firewalling, IP firewalling).
>
> > I also have not been able to find port forwarding patches to 2.1.xxx or
> > 2.2.x. Will these ever be brought back up to sync with 2.2?
>
> ipportfw is included in 2.2, I believe.
>
> Matthew.
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/