From: Rusty Russell <rusty@rustcorp.com.au>
To: Jesse Peng <tzuhsi.peng@msa.hinet.net>
Cc: Harald Welte <laforge@netfilter.org>,
netfilter-devel@lists.netfilter.org
Subject: Re: P2P implementation for netfilter NAT
Date: Sun, 04 Dec 2005 21:26:49 +1100 [thread overview]
Message-ID: <1133692009.30188.27.camel@localhost.localdomain> (raw)
In-Reply-To: <001801c5f6b3$539b1b20$3478fea9@acer21ce70712f>
On Fri, 2005-12-02 at 04:10 +0800, Jesse Peng wrote:
> Dear All
> Here is the patch for p2p implementation.Please reference the links
> below:
> 1.Logic to implement.
> https://lists.netfilter.org/pipermail/netfilter-devel/2004-November/017479.html
> 2.The Last draft by Dan Kegel.
> http://www.brynosaurus.com/pub/net/p2pnat.pdf
>
> Hello Rusty
> Like what we discussed as following 2 points
> 1.hash_by_modified_source need be checked and added by conntracks
> being SNATP2Ped.As the checking code is hacked in
> ip_nat_used_tuple,and adding code in ip_nat_setup_info.All incoming
> hairpin or holepunch try be checked and added in the ip_nat_rule_find
> hacking.
> 2.delay tcp timeout for immediate reset by counterparts in case they
> are old version and fail to take hairpin or holepunch reaction.(Maybe
> We don't need do this any more,because that will only terminate our
> initiation,but while they initiate,we are happy to handle the
> holepunch and the hairpin! :) ) .
Hi Jesse,
Your patch seems incomplete, and anyway it's been mangled by your
mailer. Sorry I've been slow to respond, but a on a quick read I think
you're going in the right direction. Perhaps try an attachment?
Thanks!
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
next parent reply other threads:[~2005-12-04 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001801c5f6b3$539b1b20$3478fea9@acer21ce70712f>
2005-12-04 10:26 ` Rusty Russell [this message]
2005-12-05 8:03 ` P2P implementation for netfilter NAT Jesse Peng
2005-12-05 9:48 ` Waiting for user space response in Kernel Mode Guru Prasad
2005-12-05 9:52 ` Pablo Neira Ayuso
2006-01-05 15:52 ` P2P implementation for netfilter NAT Jesse Peng
2006-01-08 1:20 ` Rusty Russell
2006-01-16 16:26 ` Jesse Peng
2006-01-18 10:53 ` Jesse Peng
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=1133692009.30188.27.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=tzuhsi.peng@msa.hinet.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 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.