All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Cannings <lists@edeca.net>
To: netfilter@lists.netfilter.org
Subject: Re: Redirect ports on localhost
Date: Thu, 25 Mar 2004 20:03:09 +0000	[thread overview]
Message-ID: <200403252003.09492.lists@edeca.net> (raw)
In-Reply-To: <40633766.3050005@personalsoft.com.br>

On Thursday 25 March 2004 19:47, Fabiano Bonin wrote:
> >From: Ben Yerushalmi <beny@pd.verio.net>
> >Looks like changing the OUTPUT chain did actually work in redirecting
> >localhost traffic. On the Linux 2.4 kernel you will need to enable the
> >"NF_NAT_LOCAL" kernel option.
> Could you provide a complete example of how to do all this?
> I think it will solve some of my problems.

You'll need to enable the option CONFIG_IP_NF_NAT_LOCAL.  Using `make 
menuconfig`, the relevant options are found:

In 2.4:

Under "Networking options -> IP: Netfilter Configuration -> NAT of local 
connections"

In 2.6:

Under "Device Drivers  -> Networking Support -> Networking Options -> 
Network packet filtering (replaces ipchains) -> IP Netfilter 
Configuration"

In both you will also have to enable "Full NAT" and "iptables support".  
This will let you use NAT with connections that originate locally, ie 
from processes on your iptables machine.  The help for the option says 
there should be more on the netfilter site, http://www.netfilter.org.

David


  reply	other threads:[~2004-03-25 20:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040325193403.19216.70237.Mailman@vishnu.netfilter.org>
2004-03-25 19:47 ` Redirect ports on localhost Fabiano Bonin
2004-03-25 20:03   ` David Cannings [this message]
2004-03-23 20:10 Ben Yerushalmi
2004-03-24  2:01 ` forum
2004-03-24  2:52   ` Mark E. Donaldson
2004-03-24  2:57     ` forum
2004-03-24  3:14 ` Alexander Samad
2004-03-24 20:31   ` al clethero
2004-03-24  5:15 ` Ben Yerushalmi
2004-03-25  7:34 ` Ben Yerushalmi
2004-03-26  5:35 ` Ben Yerushalmi
2004-03-26  6:07   ` forum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200403252003.09492.lists@edeca.net \
    --to=lists@edeca.net \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.