All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Vasantha Kumar Puttappa <vasanthakumar@iitb.ac.in>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ip_local_deliver related query
Date: Tue, 07 Feb 2006 15:47:02 +0100	[thread overview]
Message-ID: <43E8B2E6.9020004@trash.net> (raw)
In-Reply-To: <37547.10.107.26.27.1139293685.squirrel@gpo.iitb.ac.in>

Vasantha Kumar Puttappa wrote:
> Hi Patrick,
>   Thanks for your response. I have one more thing to clarify.
>   ( Sorry in the previous I made a great mistake, I wanted to change
>   destination IP address of the packet and not the source IP address).
> 
>   ( I am referring to first figure in the following link
>  http://www.linuxsecurity.com/resource_files/firewalls/IPTables-Tutorial/iptables-tutorial.html)
> 
>   If I am not wrong, NAT is being in done in PREROUTING AND POST-ROUTING
>  stage. But what I want to do is to take packets in FILTER INPUT stage and
>  change the destination IP address ( I don't want to create any SNAT
>  corresponding to that) and give it to local process.
>  (Assume that a socket waiting with that new destination address)

NAT is also done in LOCAL_OUT (DNAT) and LOCAL_IN (SNAT).

>   So, will there be any problem ?

No, it will work fine. Again: the socket lookups are done after the
netfilter hooks were called, so they will use the changed IP address.

      reply	other threads:[~2006-02-07 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03  6:13 ip_local_deliver related query Vasantha Kumar Puttappa
2006-02-03 13:56 ` Patrick McHardy
2006-02-04  6:21   ` Vasantha Kumar Puttappa
2006-02-07  6:28     ` Vasantha Kumar Puttappa
2006-02-07 14:47       ` Patrick McHardy [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=43E8B2E6.9020004@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=vasanthakumar@iitb.ac.in \
    /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.