From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@lists.netfilter.org
Subject: Re: Where has NAT gone?
Date: Tue, 17 Apr 2007 22:21:08 +0200 [thread overview]
Message-ID: <46252C34.40309@plouf.fr.eu.org> (raw)
In-Reply-To: <1176839902.3870.9.camel@murdegern.cbxnet.de>
Hello,
Torsten Luettgert a écrit :
>
> What you're probably missing is conntrack, which moved to
>
> Networking ->
> Networking options ->
> Network packet filtering framework (Netfilter) ->
> Core Netfilter Configuration
>
> There, enable "Netfilter connection tracking support"
> (CONFIG_NF_CONNTRACK_ENABLED) and "Netfilter Xtables support"
> (CONFIG_NETFILTER_XTABLES).
>
> Then, one menu up and into "IP: Netfilter Configuration",
> enable
>
> IPv4 connection tracking support (CONFIG_NF_CONNTRACK_IPV4)
> IP tables support (CONFIG_IP_NF_IPTABLES)
> Full NAT (CONFIG_NF_NAT)
Note that although it is now the default since 2.6.20, you can still
disable the new layer 3-independent connection tracking in the "Core
Netfilter Configuration" menu and enable the old IPv4-only connection
tracking (CONFIG_IP_NF_CONNTRACK) and NAT (CONFIG_IP_NF_NAT) in the "IP:
Netfilter Configuration" menu. But you lose the IPv6 connection tracking.
> I understand those config options were moved because they are
> actually not IPv4 specific ("iptables") but more general,
> IPv4 / IPv6 / ARP ("xtables").
Yes, but AFAIK xtables has little to do (if anything) with the layer
3-independant connection tracking.
> The binary for setting the rules is still called "iptables", though.
Because that's the dedicated userspace tool to manage the IPv4 rules.
There are similar dedicated tools to manage IPv6 and ARP rules,
respectively ip6tables and arptables.
next prev parent reply other threads:[~2007-04-17 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 8:12 Where has NAT gone? richard
2007-04-17 9:02 ` Jan Engelhardt
2007-04-17 19:58 ` Torsten Luettgert
2007-04-17 20:21 ` Pascal Hambourg [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-19 9:37 richard
2007-04-17 8:07 netsol3
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=46252C34.40309@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--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.