All of lore.kernel.org
 help / color / mirror / Atom feed
From: carlopmart <carlopmart@gmail.com>
To: netfilter@vger.kernel.org
Subject: Re: Using source nat to discriminate traffic
Date: Tue, 26 Apr 2011 14:42:43 +0200	[thread overview]
Message-ID: <4DB6BDC3.1070306@gmail.com> (raw)
In-Reply-To: <4DB6B471.7000805@atc.tcs.com>

On 04/26/2011 02:02 PM, Vigneswaran R wrote:
> On 04/26/2011 02:37 PM, carlopmart wrote:
>> - BBDD_1 can only be accessed by ip address 172.21.2.2.
>> - BBDD_2 can only be accessed by ip address 172.21.2.3
>>
>> Both ip address, 172.21.2.2 and 172.21.2.3, are assigned to the first
>> host that acts as a mysql client. Latest release of mysql client
>
> IMHO, if both the IPs are bound to the same host in a permanent basis,
> it would be better (request the admin) to change the ACLs so that both
> the databases (BBDD_1 and BBDD_2) are allowed from the same IP (either
> 172.21.2.2 or 172.21.2.3). Then as you know, your iptables rule will
> work for both databases.
>
>
> Regards,
> Vignesh
> --

Thanks Vignesh. Yes, your solution is perfectly and correct. But exists 
a problem: this hosts is included on a cluster (RHCS) with three nodes 
(in three weeks, will be six nodes). Service can run on a hostA, hostB 
or hostC ...


-- 
CL Martinez
carlopmart {at} gmail {d0t} com

  reply	other threads:[~2011-04-26 12:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-26  9:07 Using source nat to discriminate traffic carlopmart
2011-04-26  9:15 ` Jan Engelhardt
2011-04-26  9:45   ` carlopmart
2011-04-26 12:02 ` Vigneswaran R
2011-04-26 12:42   ` carlopmart [this message]
2011-04-27  5:37     ` Vigneswaran R

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=4DB6BDC3.1070306@gmail.com \
    --to=carlopmart@gmail.com \
    --cc=netfilter@vger.kernel.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.