Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Javier Prieto Martínez" <javier.prieto.ext@juntadeandalucia.es>
To: Grant Taylor <gtaylor@riverviewtech.net>,
	Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Redirecting ports in a bridge
Date: Tue, 22 Apr 2008 17:10:55 +0200	[thread overview]
Message-ID: <480DFFFF.7090807@juntadeandalucia.es> (raw)
In-Reply-To: <480DF644.8010302@riverviewtech.net>


>> Thanks for the advice. I'll try with EBTables, then.
>
> *nod*
>
> Except for possibly some syntactical change your rules should be very 
> similar and operate in the same fashion.
>
> Based on your previous statement "I don't want to mess with the real 
> IPs" it sounds like you don't even want to change source / destination 
> IPs of the traffic going to the back end system.  Am I understanding 
> you correctly that you indeed want to not alter the source and / or 
> destination IP?  If this is the case, be aware that you do not want to 
> NAT the IP and that you will be down to NATing the MAC address (which 
> can be done but is another discussion) as the frame is passing through 
> the bridge.
>
> I guess I should ask:
>
> +---+         +---+   +---+   +---+
> | C +-- - - --+ R +---+ A +---+ S |
> +---+         +---+   +---+   +---+
>
> Presuming that C is the client, R is the router, A is the appliance, 
> and S is one or more of the servers, do you want S to see the source 
> and destination IP that the client connected to?  Or is it ok for the 
> appliance to munge the source and / or destination IP (as seen by the 
> server) in the process of redirecting to the server?

Well.. I don't speak English very well, so it's easy to misunderstand my 
posts :-)

In your graph, "S" is my LAN with my all my servers and local 
workstations. When I say that "I don't want to mess with the real IPs", 
I mean I don't want to make any change within my LAN.

The point of the redirection is that, when I need to make a change in 
one of my servers, I'd like my appliance to redirect all the traffic 
coming from the extranet ("C") to another server. For example, if I have 
to stop the web server while upgrading, I'd like all the traffic coming 
from outside to reach another web server with a catched version of my 
web page.

The proccess should be something like that:

* C starts a connection to S1, port 80
* R routes that packet to my LAN
* A captures that packet, and changes the destintation to S2, port 80
* S2 generates a response to C
* A captures that packet, and changes its source to S1, port 80
* R routes that packet to the outside network
* C gets a packet from S1, port 80

I'm making some tests with EBTables in my lab enviroment.
I'll tell you the results.

Thanks a lot.

  reply	other threads:[~2008-04-22 15:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18  9:27 Redirecting ports in a bridge Javier Prieto Martínez
2008-04-18 10:35 ` Jan Engelhardt
2008-04-18 10:55   ` Javier Prieto Martínez
2008-04-18 11:29     ` Jan Engelhardt
2008-04-18 11:41       ` Javier Prieto Martínez
2008-04-18 12:26         ` Marc Cozzi
2008-04-18 12:34           ` Javier Prieto Martínez
2008-04-23 15:25           ` Jan Engelhardt
2008-04-18 14:38         ` Grant Taylor
2008-04-21  6:55           ` Javier Prieto Martínez
2008-04-22  1:30             ` Grant Taylor
2008-04-22  6:15               ` Javier Prieto Martínez
2008-04-22 14:29                 ` Grant Taylor
2008-04-22 15:10                   ` Javier Prieto Martínez [this message]
2008-04-22 19:24                     ` Grant Taylor
2008-04-23 15:24         ` Jan Engelhardt
2008-04-23 17:16           ` Grant Taylor
2008-04-23 18:48             ` Jan Engelhardt
2008-04-23 18:57               ` Grant Taylor
2008-04-24  6:15                 ` Javier Prieto Martínez
2008-04-18 14:34   ` Grant Taylor
2008-04-18 14:44 ` Grant Taylor

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=480DFFFF.7090807@juntadeandalucia.es \
    --to=javier.prieto.ext@juntadeandalucia.es \
    --cc=gtaylor@riverviewtech.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox