From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Felipe W Damasio <felipewd@gmail.com>, netfilter-devel@vger.kernel.org
Subject: Re: ebtables extension 'http'
Date: Mon, 25 Jan 2010 17:57:48 +0100 [thread overview]
Message-ID: <4B5DCD8C.4010201@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1001251753560.20906@obet.zrqbmnf.qr>
Jan Engelhardt wrote:
> On Monday 2010-01-25 17:50, Patrick McHardy wrote:
>>>>> http://l7-filter.sourceforge.net/FAQ#usage
>>>> Right, thanks!
>>>>
>>>> But I just don't see the point of letting all the http traffic flows
>>>> through squid since it'll only care about a handful of domains...
>>>>
>>>> I don't suppose there is a way of "putting" the connection back on
>>>> the forwarding-state on the bridge after ebtables already dropped it
>>>> on the broute table, is there?
>>> Once you decided which machine handles the packet stream, it's decided.
>>> The twist is, you have to decide when you see the very first packet.
>> CT actually doesn't really care, it should be possible with TPROXY
>> if the local socket could be persuaded to close silently.
>
> 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 :-)
You're right, that wouldn't work without even mory ugly.
next prev parent reply other threads:[~2010-01-25 16:57 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 [this message]
2010-01-25 17:45 ` Felipe W Damasio
2010-01-25 19:02 ` Pascal Hambourg
2010-01-26 6:29 ` 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=4B5DCD8C.4010201@trash.net \
--to=kaber@trash.net \
--cc=felipewd@gmail.com \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.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).