All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn <core@enodev.com>
To: Ray Leach <raymondl@knowledgefactory.co.za>
Cc: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: Two IP add
Date: 05 Jun 2003 12:50:44 -0500	[thread overview]
Message-ID: <1054835444.8856.2.camel@localhost> (raw)
In-Reply-To: <1054819746.13885.39.camel@raylinux.internal>

On Thu, 2003-06-05 at 08:29, Ray Leach wrote:
> On Thu, 2003-06-05 at 13:38, Dharmendra.T wrote:
> > On Thu, 2003-06-05 at 15:26, Paulo Andre wrote: 
> >         I would like to do the following:
> >         iptables -t nat -A POSTROUTING -s x.x.x.x -d ! 'servers ip' -j MASQUERADE 
> >         now how would i put in two ip address's ?
> > iptables -t nat -A POSTROUTING -s 10.10.10.5 -d 'sever ip' -j DROP 
> > iptables -t nat -A POSTROUTING -s 10.10.10.8 -d 'sever ip' -j DROP 
> > Should work 
> No, that will drop the packets and they won't traverse any more
> tables/chains.
> 
> the -j return tells iptables to leave the POSTROUTING chain and
> continue, so no more POSTROUTING rules will be checked for that packet.
> 
> the nat table has these chains:
> 
> PREROUTING
> POSTROUTING
> OUTPUT
> 
> A target of -j return means leave this chain and continue to the next.

So what happens with
iptables -t nat -A POSTROUTING -s 10.x.x.5 -s 'server ip' -j POSTROUTING

;]


  reply	other threads:[~2003-06-05 17:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05  9:56 Two IP add Paulo Andre
2003-06-05 11:07 ` Ray Leach
2003-06-05 11:38 ` Dharmendra.T
2003-06-05 13:29   ` Ray Leach
2003-06-05 17:50     ` Shawn [this message]
2003-06-05 17:51     ` Pascal Italiaander
2003-06-05 17:54       ` Pascal Italiaander
2003-06-05 22:56         ` Alistair Tonner
2003-06-05 23:56           ` Pascal Italiaander
2003-06-06  1:10             ` Alistair Tonner

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=1054835444.8856.2.camel@localhost \
    --to=core@enodev.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=raymondl@knowledgefactory.co.za \
    /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.