Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Leonardo Rodrigues <leolistas@solutti.com.br>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Jack Bates <uo4zau@nottheoilrig.com>, netfilter@vger.kernel.org
Subject: Re: Discriminate client requests from transparent proxy requests?
Date: Thu, 20 Dec 2012 10:58:02 -0200	[thread overview]
Message-ID: <50D30B5A.1030605@solutti.com.br> (raw)
In-Reply-To: <alpine.LNX.2.01.1212200858460.2026@nerf07.vanv.qr>

Em 20/12/12 06:18, Jan Engelhardt escreveu:
>
>>   * TOS/DSCP field
> I would not put too much reliance on this one, as hosts take more
> freedom in setting this field to whatever they like.
>

     as this is, in fact, a useless information for general purposes, 
you can always force all packets with some specific TOS/DSCP field and 
later alter that to meet your criterias. That way, even if hosts set 
those to something that would mess with your internal matching/routing, 
ensuring that it will be changed to your default ones would do it.



-- 


	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




  reply	other threads:[~2012-12-20 12:58 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 [this message]
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=50D30B5A.1030605@solutti.com.br \
    --to=leolistas@solutti.com.br \
    --cc=jengelh@inai.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox