netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Janis Dzerve <janisdz2@gmail.com>
To: netfilter-devel@vger.kernel.org
Subject: SNAT in NF_INET_PRE_ROUTING not working on kernel 2.6.35
Date: Thu, 14 Apr 2011 12:57:57 -0700	[thread overview]
Message-ID: <BANLkTimxX+sjsYpSCpyeKsejamAk_O0WYw@mail.gmail.com> (raw)

Hi,

I'm working on the project where incoming packets are source-natted in
NF_INET_PRE_ROUTING netfilter hook.
I know that iptables does not allow SNAT in PREROUTING but it works
fine in preroute netfilter hook in kernel 2.6.32 with rp_filter
disabled.
After upgrading to kernel 2.6.35 it does not work any more. I.e. the
natted packets are dropped somewhere after being natted and do not
appear in the forwarding hook any more.

So, I wanted to ask if this feature (snat in preroute) was explicitly
disabled? and is there any way to reenable it?

Thank you,
Janis Dzerve.

                 reply	other threads:[~2011-04-14 19:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=BANLkTimxX+sjsYpSCpyeKsejamAk_O0WYw@mail.gmail.com \
    --to=janisdz2@gmail.com \
    --cc=netfilter-devel@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).