From: Thilo Schulz <arny@ats.s.bawue.de>
To: netfilter@lists.netfilter.org
Subject: Re: Blocking Google Earth
Date: Sat, 13 Aug 2005 04:31:19 +0200 [thread overview]
Message-ID: <200508130431.24772.arny@ats.s.bawue.de> (raw)
In-Reply-To: <20050812223230.14D0920EB@juno.tc.df.gov.br>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
On Saturday 13 August 2005 00:38, fabricio bianco abreu wrote:
> I would like to block it because a user using Google Earth consumes about
> 256kbps bandwith. I have 600+ users and only a 2Mbps link to the Internet.
I don't see how you would do that without doing a packet inspection for all
packets directed at www.google.com, as maps.google.com is - as you
undoubtedly already know - is an alias for www.google.com
You would have to do packet inspection and filter for maps.google.com. This
could be easily circumvented by using an SSL capable proxy.
Maybe QoS could do the trick for you. While allowing access to google earth,
it might discourage that user from excessively using it by restricting his
bandwidth to something like 64kbit/s while google itself is still perfectly
usable. It is generally a sensible idea to make use of QoS on a setup like
yours.
--
Thilo Schulz
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-13 2:31 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 [this message]
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
-- 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=200508130431.24772.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