From: Thilo Schulz <arny@ats.s.bawue.de>
To: netfilter@lists.netfilter.org
Subject: Re: Blocking Google Earth
Date: Sat, 13 Aug 2005 17:11:15 +0200 [thread overview]
Message-ID: <200508131711.17351.arny@ats.s.bawue.de> (raw)
In-Reply-To: <42FE0054.5020204@solutti.com.br>
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
On Saturday 13 August 2005 16:14, Leonardo Rodrigues Magalhães wrote:
> I really dont think it's easy to limit bandwidth usage ONLY for
> Earth Google without making bad experiencies on doing searchs on Google.
> No matter if searches are low-bandwidth. If you get some QoS and band
> limitation on google IPs, be sure that your google earth users will use
> ALL the available bandwidth, thus making google earth as well as google
> serching probably extremely slow.
He only had that problem with one single user. Likewise, he can restrict
bandwidth to google only for that one single user too. Like I already said,
your proxy method can be easily circumvented using something like an SSL
proxy after your proxy, whereas QoS can selectively keep a user from unfairly
exceeding certain bandwidth. This will not only solve problems with the http
protocol, but also problems with the user using too much bandwidth in
general.
--
Thilo Schulz
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-13 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 20:18 Blocking Google Earth fabricio bianco abreu
2005-08-12 20:29 ` Raphael Jacquot
2005-08-12 22:38 ` fabricio bianco abreu
2005-08-13 2:31 ` Thilo Schulz
2005-08-12 23:59 ` Eric Scopinho
2005-08-13 12:32 ` Jan Engelhardt
2005-08-14 1:15 ` Dwayne Hottinger
2005-08-13 14:14 ` Leonardo Rodrigues Magalhães
2005-08-13 15:11 ` Thilo Schulz [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-13 19:44 Joris Dobbelsteen
2005-08-15 6:22 ` Jan Engelhardt
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=200508131711.17351.arny@ats.s.bawue.de \
--to=arny@ats.s.bawue.de \
--cc=netfilter@lists.netfilter.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