From: capsx <capsx@divx.team.lv>
Cc: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: POSTROUTING
Date: Wed, 18 Feb 2004 20:26:54 +0200 [thread overview]
Message-ID: <4033AE6E.4010008@divx.team.lv> (raw)
In-Reply-To: <BFEIJHPOPCCMOPEKHHMOAEEHCOAA.giovanni.costagliola@nexusat.it>
!
I want as source to specify a chain
not -s 10.0.0.0/27 but something like -s LOCAL_NET_CHAIN
-[capsx]-
giovanni costagliola wrote:
> ??
>
> try to explain what you mean.
>
> *g
>
> *g> -----Messaggio originale-----
> *g> Da: netfilter-admin@lists.netfilter.org
> *g> [mailto:netfilter-admin@lists.netfilter.org]Per conto di capsx
> *g> Inviato: mercoledi 18 febbraio 2004 19.07
> *g> A: Netfilter
> *g> Oggetto: Re: POSTROUTING
> *g> *g> *g> *g> iptables -N LOCAL_NET <- new chain
> *g> iptables -A INPUT -i eth1 -s 10.0.0.9 -j LOCAL_NET <- add adress
to *g> chain LOCAL_NET
> *g> *g> is there something wrong ?
> *g> *g> *g> -[capsx]-
> *g> *g> *g> Alexis wrote:
> *g> > But, this is not right, LOCAL_NET is not a target, you need at
least to
> *g> > create a new chain called LOCAL_NET to use it as a target.
> *g> > *g> > Im not shure if you can use a chain as a match.
> *g> > *g> > *g> > *g> > On Wed, 2004-02-18 at 12:08, capsx wrote:
> *g> > *g> >>Hello!
> *g> >>
> *g> >>Is it possible in POSTROUTING as source to specify a chain:
> *g> >>
> *g> >>f.e.
> *g> >>
> *g> >>iptables -N LOCAL_NET
> *g> >>iptables -A INPUT -i eth1 -s 10.0.0.9 -j LOCAL_NET
> *g> >>
> *g> >>iptables -t nat -A POSTROUTING -o eth0 -s LOCAL_NET -j SNAT
--to ip.ad.re.ss
> *g> *g>
>
next prev parent reply other threads:[~2004-02-18 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 15:08 POSTROUTING capsx
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 ` capsx [this message]
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=4033AE6E.4010008@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