From: Stephen Hemminger <shemminger@vyatta.com>
To: Ivan Chernyavsky <camposer@yandex.ru>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] ethernet bridging and http header enrichment
Date: Wed, 3 Dec 2008 11:30:42 -0800 [thread overview]
Message-ID: <20081203113042.392f078d@extreme> (raw)
In-Reply-To: <495641228242344@webmail54.yandex.ru>
On Tue, 02 Dec 2008 21:25:44 +0300
Ivan Chernyavsky <camposer@yandex.ru> wrote:
> Dear all,
>
> I have following problem to solve:
>
> 1. Traffic should go thru my box transparently --- no changes
> in IP or MAC addresses.
>
> 2. Part of that traffic, namely, some web traffic to particular
> hosts, should be "enriched" by adding some headers to HTTP
> requests. Size of original requests is guaranteed to be
> small enough so that header insertion will not make them to grow
> above max allowed ethernet frame size.
>
> I know how to handle (1), and that's why I'm here. But I don't
> have much ideas how to perform (2) in that context.
>
> I was looking to write an 'ebtables' extension, but it seems
> that it is impossible to alter the frame size using these (am
> I wrong?). Using them together with some userland application
> like Squid, from my opinion, would break my condition (1) (again,
> am I so wrong??).
>
> Could you please point me to some documentation or bring an idea
> how that could be accomplished?
>
> Thanks in advance,
>
Use iptables, and queue?
next prev parent reply other threads:[~2008-12-03 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 18:25 [Bridge] ethernet bridging and http header enrichment Ivan Chernyavsky
2008-12-03 19:30 ` Stephen Hemminger [this message]
2008-12-04 16:53 ` Ivan Chernyavsky
2008-12-04 16:39 ` Jaime Medrano
2008-12-04 17:23 ` Ivan Chernyavsky
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=20081203113042.392f078d@extreme \
--to=shemminger@vyatta.com \
--cc=bridge@lists.linux-foundation.org \
--cc=camposer@yandex.ru \
/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