netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amin Azez <azez@ufomechanic.net>
To: liran tal <liransgarage@gmail.com>
Cc: Netfilter Developer Mailing List <netfilter-devel@lists.netfilter.org>
Subject: Re: The cause of NAT/Masquerading not perfomed
Date: Thu, 20 Sep 2007 11:51:41 +0100	[thread overview]
Message-ID: <46F250BD.7010405@ufomechanic.net> (raw)
In-Reply-To: <3ed55890709190705t229ccb08i59f27daa0308bb2a@mail.gmail.com>

* liran tal wrote, On 19/09/07 15:05:
> Hey everyone,
> 
> What can be attributed as the cause for the problem of not performing an
> NAT/Masquerade?
> This is a basic scenario where a computer on the LAN attempts to reach a
> computer beyond
> the WAN port and what happens is that no Masquerading is being performed -
> i.e: with a sniffer
> I can see that the IP that was received is of the LAN computer (wasn't
> replaced by the WAN IP address).
> 
> I can answer the question above with several possibilities:
> 1. wrong iptables rules
> 2. no NAT support compiled in kernel (or as module)
> 3. (bad network driver?)
> 
> I've had this problem with a kernel 2.4 and now I migrated completely to
> kernel 2.6 (2.6.10)
> and still encounter this problem.
> 
> Any comment on this issue would mean alot to me.


For what reasons do you suppose that NAT should be being performed (as
opposed to NEEDS to be performed).

Maybe you cane post the output from iptables-save so we can see where
you have put the NAT rules.

Sam

      reply	other threads:[~2007-09-20 10:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 14:05 The cause of NAT/Masquerading not perfomed liran tal
2007-09-20 10:51 ` Amin Azez [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=46F250BD.7010405@ufomechanic.net \
    --to=azez@ufomechanic.net \
    --cc=liransgarage@gmail.com \
    --cc=netfilter-devel@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 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).