From: Harald Welte <laforge@netfilter.org>
To: Stelios Sidiroglou-Douskos <ss1759@cs.columbia.edu>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: IPIP and SNAT
Date: Sat, 2 Aug 2003 18:03:51 +0200 [thread overview]
Message-ID: <20030802160351.GA21637@naboo> (raw)
In-Reply-To: <Pine.GSO.4.31.0307301130240.13487-100000@disco.cs.columbia.edu>
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
On Wed, Jul 30, 2003 at 11:37:23AM -0400, Stelios Sidiroglou-Douskos wrote:
>
> I am having some trouble with SNAT and my IPIP implementation.
What is 'your IPIP implementation'?
> I have the ipip part working (I use code from ipip.c) but when I clear
> the nfct field of the sk_buff that packet that gets fwd to the other
> interface doesn't get NATed.
obviously. The NAT mappings are saved in the conntrack entry, so if you
remove the reference to conntrack, there will no NAT happen.
> I tried not clearing conntrack but obviously that results in
> the packets not matching up when they return.
>
> Do I have to rebuild the conntrack tuple and insert it back? If so, is
> there a code or a helper function to do just that?
well, as I am not aware of what exactly you are trying to implement,
It's hard to give any hints.
> thanks in advance,
> stelios.
>
> p.s Please reply to this address directly also.
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-02 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 15:37 IPIP and SNAT Stelios Sidiroglou-Douskos
2003-08-02 16:03 ` Harald Welte [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-31 19:30 Stelios Sidiroglou-Douskos
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=20030802160351.GA21637@naboo \
--to=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=ss1759@cs.columbia.edu \
/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.