From: Jack Bates <uo4zau@nottheoilrig.com>
To: netfilter@vger.kernel.org
Subject: Discriminate client requests from transparent proxy requests?
Date: Mon, 17 Dec 2012 23:45:23 -0800 [thread overview]
Message-ID: <50D01F13.7030707@nottheoilrig.com> (raw)
Do you have any advice how to discriminate traffic from clients from
traffic from our transparent proxy?
Our proxy sends requests to origin servers with the same source address
as the request from the client, so we can do per-host traffic shaping on
our router. But consequently I wonder how to discriminate client
requests from proxy requests, and route the former to the proxy, but not
route the latter. What options are there?
next reply other threads:[~2012-12-18 7:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 7:45 Jack Bates [this message]
2012-12-18 8:27 ` Discriminate client requests from transparent proxy requests? Jan Engelhardt
2012-12-19 16:41 ` Jack Bates
2012-12-19 21:51 ` Jan Engelhardt
2012-12-20 7:42 ` Jack Bates
2012-12-20 8:18 ` Jan Engelhardt
2012-12-20 12:58 ` Leonardo Rodrigues
2012-12-20 15:54 ` Neal Murphy
2012-12-20 19:35 ` Jan Engelhardt
2012-12-20 21:03 ` Neal Murphy
2012-12-18 13:35 ` Leonardo Rodrigues
2012-12-19 18:33 ` Jack Bates
2012-12-19 19:05 ` Leonardo Rodrigues
2012-12-20 7:10 ` Jack Bates
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=50D01F13.7030707@nottheoilrig.com \
--to=uo4zau@nottheoilrig.com \
--cc=netfilter@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 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.