From: Changli Gao <xiaosuo@gmail.com>
To: sclark46@earthlink.net
Cc: Jan Engelhardt <jengelh@medozas.de>, netfilter-devel@vger.kernel.org
Subject: Re: clone packet with new destination address
Date: Mon, 1 Nov 2010 23:02:21 +0800 [thread overview]
Message-ID: <AANLkTimfa_MguD9s1g1e2VkGwnPJFygFSFQirODuR-Zw@mail.gmail.com> (raw)
In-Reply-To: <AANLkTiny3XRc7-OPrUzvzp_=0wd4KJ+GAhPQEkQrSwjR@mail.gmail.com>
On Mon, Nov 1, 2010 at 11:00 PM, Changli Gao <xiaosuo@gmail.com> wrote:
> On Mon, Nov 1, 2010 at 10:29 PM, Stephen Clark <sclark46@earthlink.net> wrote:
>>
>> I am not sure on how to go about doing that, looking at the code for TEE it
>> looks
>> like the cloned packet bypasses any of the remaining iptables chains.
>
> It isn't true. The cloned packet only bypasses the iptables rule where
> it is generated.
>
>> So
>> where
>> would I change the destination address? Also if I am mistaken and it does
>> hit
>> one of the remaining iptables chains how do I tell it is not the original
>> but the
>> cloned packet I want to change to the new destination address?
>>
>
> I think you can use the RAWSNAT xtables-addon to change the
> destination address. Since the new skb is attached to untracked ct,
> you can use match conntrack --ctstate UNTRACKED to filter it out.
>
s/SNAT/DNAT/g .
--
Regards,
Changli Gao(xiaosuo@gmail.com)
next prev parent reply other threads:[~2010-11-01 15:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 12:31 clone packet with new destination address Stephen Clark
2010-10-22 13:24 ` Changli Gao
2010-10-22 13:36 ` Changli Gao
2010-10-22 14:16 ` Stephen Clark
2010-11-01 12:46 ` Stephen Clark
2010-11-01 13:09 ` Jan Engelhardt
2010-11-01 14:29 ` Stephen Clark
2010-11-01 15:00 ` Changli Gao
2010-11-01 15:02 ` Changli Gao [this message]
2010-11-01 15:16 ` Stephen Clark
2010-11-01 19:37 ` Jan Engelhardt
2010-11-01 19:29 ` Jan Engelhardt
2010-11-02 13:44 ` Stephen Clark
2010-11-02 13:46 ` Jan Engelhardt
2010-11-02 13:53 ` Stephen Clark
2010-11-02 22:35 ` Changli Gao
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=AANLkTimfa_MguD9s1g1e2VkGwnPJFygFSFQirODuR-Zw@mail.gmail.com \
--to=xiaosuo@gmail.com \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=sclark46@earthlink.net \
/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).