All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pascal Italiaander <pc-secure@home.nl>
To: Alistair@nerdnet.ca, Netfilter <netfilter@lists.netfilter.org>
Subject: Re: Two IP add
Date: Fri, 6 Jun 2003 01:56:08 +0200	[thread overview]
Message-ID: <200306060156.08079.pc-secure@home.nl> (raw)
In-Reply-To: <200306051856.48803.Alistair@nerdnet.ca>

Op vrijdag 6 juni 2003 00:56, schreef u:
> On June 5, 2003 01:54 pm, Pascal Italiaander wrote:
> > Op donderdag 5 juni 2003 19:51, schreef u:
> > > Op donderdag 5 juni 2003 15:29, schreef Ray Leach:
> > > > 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:
> > > > >
> > > > >         Stop MASQUESRADING to two servers say. 10.10.10.5 and
> > > > > 10.10.10.8, how would i do this with a rule.
> > > > >
> > > > >         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 ?
> > >
> > > Ok , you could do something like this:
> >
> > sorry in the first reply was an error !!
> > this is fixed now.
> >
> >  NO_MASK="10.10.10.5 10.10.10.8"
> >
> >  if [ ${NO_MASK} != "" ] ; then
> >    for nomask in ${NO_MASK}; do
> >   	iptables -t nat -A POSTROUTING -s x.x.x.x -d ! ${nomask} -j MASQUERADE
> >  done;
> >  fi
> >
> > > this is a bit more flexible, cause , you can ad more ip's the NO_MASK
> > > easily without changing the rule itself, or have to write a new line.
> >
> >  Pascal
>
> 	I somehow don't think this will do what we want here.
> 	rule 1 from this loop will MASQUERADE any ip that is
> 	NOT 10.10.10.5, which unfortunately includes 10.10.10.8
> 	and rule #2 will never be hit by the 10.10.10.8 packet.
>
> 	I would suggest that we want to take the entire segment
> 	and manage it separately, but I have no experience with
> 	creating user chains in the nat table, although this *might*
> 	work -- ymmv
>
>
> iptables -t nat -N masq_filter
> iptables -t nat -A POSTROUTING -s x.x.x.x -d 10.10.10.0/24 -j masq_filter
> # the above line includes an assumption that MIGHT BE WRONG!!!! I dont know
> # what your netmask is!!!!!!!!!
> iptables -t nat -A masq_filter -d 10.10.10.5 -j RETURN
> iptables -t nat -A masq_filter -d 10.10.10.8 -j RETURN
> iptables -t nat -A masq_filter -j MASQUERADE
>
> 	filling in out the ips to NOT masquerade one at a time, perhaps with a
> loop as pascal suggests above, with appropriate modifications...

Yes correct , now you mention it , I see it also.
2 lines where added to the filter-list and would not traverse the firewall if 
IP was 10.10.10.8 

however the syntax could be reused, with this modification.
So combined the information together we get this example;

MASQ="yes' #Do you need masquerading ?
NO_MASK="10.10.10.5 10.10.10.8" #IP's who don't need masquerading(watch the 
single-space)
INET="10.10.10.0/24" #Local network + subnet
EX_IF="eth0" #External interface

if [ ${MASQ} == "yes" ]; then
   if [ ${NO_MASK} != "" ] ; then
        for nomask in ${NO_MASK}; do
 		iptables -t nat -A POSTROUTING -s x.x.x.x -d ! ${nomask} -j RETURN
		iptables -A POSTROUTING -t nat -s ${INET} -o ${EX_IF} -j MASQUERADE
 	done;
		else
			iptables -A POSTROUTING -t nat -s ${INET} -o ${EX_IF} -j MASQUERADE
 fi

greetings Pascal
have fun


  reply	other threads:[~2003-06-05 23:56 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
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 [this message]
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=200306060156.08079.pc-secure@home.nl \
    --to=pc-secure@home.nl \
    --cc=Alistair@nerdnet.ca \
    --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.