From: Changli Gao <xiaosuo@gmail.com>
To: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: ebtables extension 'http'
Date: Tue, 26 Jan 2010 14:29:37 +0800 [thread overview]
Message-ID: <412e6f7f1001252229q6e8afde1r474939fadeea57ae@mail.gmail.com> (raw)
In-Reply-To: <4B5DEAB0.6080401@plouf.fr.eu.org>
On Tue, Jan 26, 2010 at 3:02 AM, Pascal Hambourg
<pascal.mail@plouf.fr.eu.org> wrote:
> Hello,
>
> Felipe W Damasio a écrit :
>>
>> 2010/1/25 Jan Engelhardt <jengelh@medozas.de>:
>>> The issue is that you would need to replay the tcp handshake.
>>>
>>> Case 1:
>>> - do TCP handshake
>>> - read out Host: header
>>> - if proxied
>>> - good
>>> - if not,
>>> - have to replay TCP handshake to next host (eww :-)
>>
>> Would this be so bad? :-)
>
> Yes, quite, because it must be transparent to the client. However the
> new server may have a lower MSS and not support some TCP options such as
> windows scaling, ECN, selective ACK, window scaling, timestamps... that
> the previous one supported and which are transmitted only during the
> handshake, so the client would not know about.
how about learning this info from the next hop by sending a SYN packet
with all options set and the largest MSS. It sounds like TCP splicing
and SYN proxy. And I heard some one had implemented SYN proxy in
Linux, and xBSD also support SYN proxy. Is there any chance to
integrate SYN proxy and TCP splicing into Linux?
> Not to mention that of
> course it will use a different initial sequence number and it would have
> to be translated by the bridge in each packet.
NAT also need to take care of this, so we can reuse the code already
in the kernel maybe.
--
Regards,
Changli Gao(xiaosuo@gmail.com)
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-01-26 6:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 13:46 ebtables extension 'http' Felipe W Damasio
2010-01-25 13:54 ` Jan Engelhardt
2010-01-25 14:32 ` Felipe W Damasio
2010-01-25 16:35 ` Jan Engelhardt
2010-01-25 16:50 ` Patrick McHardy
2010-01-25 16:55 ` Jan Engelhardt
2010-01-25 16:57 ` Patrick McHardy
2010-01-25 17:45 ` Felipe W Damasio
2010-01-25 19:02 ` Pascal Hambourg
2010-01-26 6:29 ` Changli Gao [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=412e6f7f1001252229q6e8afde1r474939fadeea57ae@mail.gmail.com \
--to=xiaosuo@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pascal.mail@plouf.fr.eu.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).