All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rio Martin <rio@martin.mu>
To: netfilter@lists.netfilter.org
Subject: Blocking Streaming Media (Was: Re: (no subject)..)
Date: Tue, 1 Jun 2004 09:43:02 +0700	[thread overview]
Message-ID: <200406010943.02317.rio@martin.mu> (raw)
In-Reply-To: <6.0.3.0.2.20040531211546.02412c80@mx1.girotto.com.au>

On Monday 31 May 2004 18:18, Ivan wrote:
> Hi,
> I am looking for a solution to block streaming media using iptables.
> I have found that some of my users are listening to radio stations using
> internet, which has pumped up the
> internet bill significantly, and of course put a choke on my internet
> links. Does anyone know of a solution for blocking just the streaming media
> traffic from any web site, while still allowing
> the access to the website it self?
> Thanks,
> Ivan


Hiye Ivan,
The problem you faced was users connecting to Internet Radio Stations using 
web port (port 80) isnt it ? I give u an example like LaunchCast from Yahoo 
or other stations using port 80 as their service port.

This is become a serious problem when bandwidth allocated not so wide. The 
only thing in my mind, try to apply the magic of patch-o-matic STRING. 
Examine correctly what packets arrived or what kind of streaming packets sent 
by server. Block using those STRING.

Regards,
Rio Martin.


  parent reply	other threads:[~2004-06-01  2:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-31 11:18 (no subject) Ivan
2004-05-31 11:39 ` Markus Zeilinger
2004-05-31 11:53   ` Krishna Prasanth
2004-06-01  1:34 ` Mark E. Donaldson
2004-06-01  2:43 ` Rio Martin [this message]
2004-06-01  5:37   ` Blocking Streaming Media (Was: Re: (no subject)..) SBlaze
2004-06-01 14:50     ` Michael Gale
2004-06-01 15:59       ` Rio Martin
2004-06-02  7:32     ` Rio Martin
  -- strict thread matches above, loose matches on Subject: below --
2004-06-01 15:59 Rio Martin
2004-06-10 21:37 SBlaze
2004-06-10 23:33 ` Michael Gale
2004-06-10 23:54   ` SBlaze

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=200406010943.02317.rio@martin.mu \
    --to=rio@martin.mu \
    --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 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.