From: Antoine Souques <corum@via.ecp.fr>
Cc: netfilter@vger.kernel.org
Subject: Re: Fair queuing with htb
Date: Sat, 25 Dec 2010 03:41:10 +0100 [thread overview]
Message-ID: <4D1559C6.2020807@via.ecp.fr> (raw)
In-Reply-To: <201012250208.36503.gregoire.leroy@hyperthese.net>
> I've attached a graph which explains what are the marked packets.
>
Your design is wrong. You mark the upload traffic, when the main http
traffic is the download traffic. That is why your QoS seems ineffective
> The general goal is to do a QoS based on user ip. If I had no proxy,
> it would
> be easy. However, since I've a proxy, my firewall sees the proxy ip,
> not the
> users IP.
>
Where is your firewall ? Between the proxy and the webserver, or the
otherside ?
In the first case, you can only mark the upload traffic (it's to late
for the download traffic). You should use the conntrack module to mark a
connection, and so, you will be able to mark the download traffic
Moreover, I don't understand why you don't have access to your user
addresses. You use mark, so your firewall and your proxy are running on
the same box. So, when the download traffic leaves your proxy/firewall,
the destination adsress is the user address. tc is called when a packet
is send to the network, or when a packet arrive. So you can do IP based
QoS.
Antoine
next prev parent reply other threads:[~2010-12-25 2:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 1:26 Fair queuing with htb Grégoire Leroy
2010-12-23 6:01 ` Julien Vehent
2010-12-23 12:30 ` Grégoire Leroy
2010-12-25 0:09 ` Andrew Beverley
2010-12-25 1:08 ` Grégoire Leroy
2010-12-25 2:41 ` Antoine Souques [this message]
[not found] ` <4D155860.6090507@via.ecp.fr>
2010-12-25 3:51 ` Grégoire Leroy
2010-12-25 12:29 ` Amos Jeffries
2010-12-25 20:40 ` Grégoire Leroy
2010-12-25 22:46 ` Andrew Beverley
2011-01-10 11:55 ` Grégoire Leroy
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=4D1559C6.2020807@via.ecp.fr \
--to=corum@via.ecp.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox