netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gáspár Lajos" <swifty@freemail.hu>
To: "Michal Kubeček" <mkubecek@suse.cz>,
	"netfilter list" <netfilter@vger.kernel.org>
Subject: Re: What happens after PREROUTING/nat ?
Date: Thu, 08 Dec 2011 14:58:15 +0100	[thread overview]
Message-ID: <4EE0C277.8030909@freemail.hu> (raw)
In-Reply-To: <3132035.exjJScDA16@alaris>

Hi,

Thank you for your response, but... :D


2011-12-08 09:55 keltezéssel, Michal Kubeèek írta:
> On Wednesday 07 of December 2011 18:57EN, Gáspár Lajos wrote:
>> But if "C" is in the LAN then the packets are simply disappearing...
> They are not. If you monitor the LAN traffic, you should notice that the
> problem is not the redirected packet but the reply from B to C. Because
I know about this problem and I have the required SNAT rules too...
And as I wrote the packets did not hit the line... (After C->A there was 
no A->B.... because of a missing PROMISC flag on the bridge...)

> 3. When translating the destination address from A to B for packets
> coming from LAN, translate source address as well ("masquerade"). Then
> the reply will go back to A and it will translate both source and
> destination address. Awful? Definitely, but this is where all those
> masquerades got us...
This is what I got... And it is working now... See my other post...

Thank you ! :D

Swifty

      reply	other threads:[~2011-12-08 13:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 17:57 What happens after PREROUTING/nat ? Gáspár Lajos
2011-12-07 18:23 ` SOLVED: " Gáspár Lajos
2011-12-08  8:55 ` Michal Kubeček
2011-12-08 13:58   ` Gáspár Lajos [this message]

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=4EE0C277.8030909@freemail.hu \
    --to=swifty@freemail.hu \
    --cc=mkubecek@suse.cz \
    --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;
as well as URLs for NNTP newsgroup(s).