From: Leonardo Rodrigues <leolistas@solutti.com.br>
To: Jack Bates <uo4zau@nottheoilrig.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Discriminate client requests from transparent proxy requests?
Date: Wed, 19 Dec 2012 17:05:45 -0200 [thread overview]
Message-ID: <50D21009.50702@solutti.com.br> (raw)
In-Reply-To: <50D2088C.5060903@nottheoilrig.com>
how about adjusting TOS values on the packets using those created
ACLs ?? That would probably make identification easier/possible on
routing layers, your routers included.
you can specify a specific TOS value for your 'normal proxy' port
and another one for your 'transparent proxy'.
but you're right, i didnt catch your idea and, maybe, my answer was
for a different scenario than yours. But i think that using the
transparent port ACL and adjusting TOS on those packets, you could catch
that on your routers.
from http://www.squid-cache.org/Doc/config/tcp_outgoing_tos/
Allows you to select a TOS/Diffserv value for packets outgoing
on the server side, based on an ACL.
tcp_outgoing_tos ds-field [!]aclname ...
Example where normal_service_net uses the TOS value 0x00
and good_service_net uses 0x20
acl normal_service_net src 10.0.0.0/24
acl good_service_net src 10.0.1.0/24
tcp_outgoing_tos 0x00 normal_service_net
tcp_outgoing_tos 0x20 good_service_net
TOS/DSCP values really only have local significance - so you should
know what you're specifying. For more information, see RFC2474,
RFC2475, and RFC3260.
The TOS/DSCP byte must be exactly that - a octet value 0 - 255, or
"default" to use whatever default your host has. Note that in
practice often only multiples of 4 is usable as the two rightmost bits
have been redefined for use by ECN (RFC 3168 section 23.1).
Processing proceeds in the order specified, and stops at first fully
matching line.
Em 19/12/12 16:33, Jack Bates escreveu:
> Thank you, but what I want is for our *router* to be able to tell the
> difference between requests from clients to origin servers (and
> intercept these) and requests from our transparent proxy to origin
> servers (and not intercept these). I'm wondering what options there
> are to do this because our proxy makes "transparent" requests to
> origin servers, with the same source address as the request from the
> client.
>
> I think what you're describing instead is how the *proxy* can tell the
> difference between requests that were intercepted and requests that
> were explicitly sent to the proxy.
>
--
Atenciosamente / Sincerily,
Leonardo Rodrigues
Solutti Tecnologia
http://www.solutti.com.br
Minha armadilha de SPAM, NÃO mandem email
gertrudes@solutti.com.br
My SPAMTRAP, do not email it
next prev parent reply other threads:[~2012-12-19 19:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 7:45 Discriminate client requests from transparent proxy requests? Jack Bates
2012-12-18 8:27 ` 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 [this message]
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=50D21009.50702@solutti.com.br \
--to=leolistas@solutti.com.br \
--cc=netfilter@vger.kernel.org \
--cc=uo4zau@nottheoilrig.com \
/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.