From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: define what to nat
Date: Tue, 26 Apr 2005 14:32:02 -0400 [thread overview]
Message-ID: <20050426183202.GA18758@bender.817west.com> (raw)
In-Reply-To: <200504261317.29179.gnicolax@gmail.com>
On Tue, Apr 26, 2005 at 01:17:28PM -0500, Nicolás Velásquez O. wrote:
<--snip-->
> So I was wondering if there is a way to do something like:
> iptables -t nat -A POSTROUTING -o eth0 -d 192.168.0.0/24 -j "DO NOT NAT"
yes:
iptables -t nat -A POSTROUTING -o eth0 -d 192.168.0.0/24 -j ACCEPT
> iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
-j
--
"Brian: Peter, did you read the fine print on this loan contract?
Peter: If by "read", you mean "imagine the naked lady", then yes."
--Family Guy
prev parent reply other threads:[~2005-04-26 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 18:17 define what to nat Nicolás Velásquez O.
2005-04-26 18:32 ` Jason Opperisano [this message]
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=20050426183202.GA18758@bender.817west.com \
--to=opie@817west.com \
--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.