From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: Netfilter Mailing List <netfilter@lists.samba.org>
Subject: Re: Purely NAT
Date: Mon, 28 Oct 2002 18:43:32 +0000 [thread overview]
Message-ID: <20021028184335.IOQ1554.mta07-svc.ntlworld.com@there> (raw)
In-Reply-To: <20021028183756.34671877D8@defiant.starfleet.net>
On Monday 28 October 2002 6:37 pm, Anthony Liu wrote:
> On Mon, 28 Oct 2002 14:44:43 +0000 Antony Stone
<Antony@Soft-Solutions.co.uk> wrote:
> > On Monday 28 October 2002 5:32 am, yenjet.chan@eglobal.com.my wrote:
> > > Hi all,
> > >
> > > This is my first post to the list, so please bare with me.
> > > I have a requirement here. Is there possible to create a purely NAT
> > > iptables rules for certain IP addresses?
> >
> > No. You can turn off stateful inspection by not loading or compiling
> > the connection tracking support, but you cannot use it for some addresses
> > but not others.
>
> Are you sure? By not using "-m state" it might actually work, how about:
> iptables -A FORWARD -o ppp0 -s aaa.bbb.ccc.eee -j ACCEPT
> iptables -A FORWARD -o ppp0 -s aaa.bbb.ccc.ddd -m state --state ! INVALID
> -j ACCEPT
This will allow you to create rules which do not refer to stateful
inspection, agreed, but it doesn't stop netfilter from maintaining the
connection tracking table for those connections.
Since the original poster wanted to increase the efficiency of netfilter by
avoiding the overhead of maintaining the connection tracking table, simply
writing rules which do not use -m state doesn't help.
Antony.
--
The difference between theory and practice is that
in theory there is no difference, whereas in practice there is.
next prev parent reply other threads:[~2002-10-28 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 5:32 Purely NAT Jet (jchan@trusecure.com)
2002-10-28 14:44 ` Antony Stone
2002-10-28 18:37 ` Anthony Liu
2002-10-28 18:43 ` Antony Stone [this message]
2002-10-29 2:18 ` Jet (jchan@trusecure.com)
2002-10-29 4:43 ` Alexey Talikov
2002-10-29 5:26 ` Jet
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=20021028184335.IOQ1554.mta07-svc.ntlworld.com@there \
--to=antony@soft-solutions.co.uk \
--cc=netfilter@lists.samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox