From: capsx <capsx@divx.team.lv>
To: netfilter@lists.netfilter.org
Subject: POSTROUTING
Date: Wed, 18 Feb 2004 17:08:05 +0200 [thread overview]
Message-ID: <40337FD5.5000905@divx.team.lv> (raw)
Hello!
Is it possible in POSTROUTING as source to specify a chain:
f.e.
iptables -N LOCAL_NET
iptables -A INPUT -i eth1 -s 10.0.0.9 -j LOCAL_NET
iptables -t nat -A POSTROUTING -o eth0 -s LOCAL_NET -j SNAT --to ip.ad.re.ss
--
-[capsx]-
next reply other threads:[~2004-02-18 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 15:08 capsx [this message]
2004-02-18 17:52 ` POSTROUTING Alexis
2004-02-18 18:07 ` POSTROUTING capsx
2004-02-18 18:14 ` R: POSTROUTING giovanni costagliola
2004-02-18 18:26 ` POSTROUTING capsx
2004-02-18 18:25 ` POSTROUTING Antony Stone
2004-02-18 23:45 ` POSTROUTING Arnt Karlsen
2004-02-18 23:31 ` POSTROUTING Antony Stone
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=40337FD5.5000905@divx.team.lv \
--to=capsx@divx.team.lv \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox