Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Darrell Dieringer" <netfilter@darrelldieringer.com>
To: Taniform Asongwe <tasongwe@yahoo.co.uk>, netfilter@lists.netfilter.org
Subject: RE: streaming audio ports
Date: Wed, 18 Jun 2003 12:22:38 -0500	[thread overview]
Message-ID: <IMEDICLPAGAOCBLCCKLPOEEFFKAA.netfilter@darrelldieringer.com> (raw)
In-Reply-To: <20030618165614.94092.qmail@web9604.mail.yahoo.com>

As with many things, it depends on the server.  "Shoutcast" streaming
audio servers, for instance, default to port 8000, but can be
configured to operate on any port.  I don't know about 'RealAudio' or
others, but I imagine it's a similar story.

You could block everything by default, and only permit the ports
corresponding to services you want to allow people to use.

Darrell Dieringer - Madison, WI

> -----Original Message-----
> From: netfilter-admin@lists.netfilter.org
> [mailto:netfilter-admin@lists.netfilter.org]On Behalf Of Taniform
> Asongwe
> Sent: Wednesday, June 18, 2003 11:56 AM
> To: netfilter@lists.netfilter.org
> Subject: streaming audio ports
>
>
> Hi there,
>
> could someone tell me how I can block streaming audio
> from running into my network? My users are listening
> onto internet radio stations and consuming a lot of
> bandwidth, a practice I wish to stop. I have blocked
> port 554 with iptables but it is not enough.
>
> Thanks in advance
>
> Taniform
>
> ____________________________________________________________
> ____________
> Want to chat instantly with your online friends?  Get the
> FREE Yahoo!
> Messenger http://uk.messenger.yahoo.com/
>
>
>



      reply	other threads:[~2003-06-18 17:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 16:56 streaming audio ports Taniform Asongwe
2003-06-18 17:22 ` Darrell Dieringer [this message]

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=IMEDICLPAGAOCBLCCKLPOEEFFKAA.netfilter@darrelldieringer.com \
    --to=netfilter@darrelldieringer.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=tasongwe@yahoo.co.uk \
    /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