From: Michael Gale <michael.gale@utilitran.com>
To: netfilter@lists.netfilter.org
Subject: Re: Blocking Streaming Media (Was: Re: (no subject)..)
Date: Thu, 10 Jun 2004 17:33:42 -0600 [thread overview]
Message-ID: <20040610173342.6e858194@mgalepc.utilitran.com> (raw)
In-Reply-To: <20040610213743.34810.qmail@web61007.mail.yahoo.com>
Hello,
Netfilter is a packet level firewall option, for security you should be using
multiple levels. Which means adding more layers, use iptables for packet
filtering and then:
Exampels:
Squid for http application level filtering
Frox for FTP application level filtering
For https allow connections to only required servers.
Michael.
On Thu, 10 Jun 2004 14:37:43 -0700 (PDT)
SBlaze <dagent.geo@yahoo.com> wrote:
> I guess, blocking ports or defining ports to be allowed to users is not
> enough. Users are clever and smart from day to day. Once the originial and
> standard ports blocked by administrator, they use port forwarding sometimes
> to some kind of hosting server or dedicated server, and they still able to do
> music streaming.
>
> If you checkout the greatest site, let say www.shoutcast.com, u can see lots
> of stations use port 80, it means connecting to radio stations would be the
> same as clients surfing to the web.
>
> I'm still thinking patch-o-matic STRING would be the best solustion for now ..
>
> Regards,
> Rio Martin.
>
> Perhaps you missed the rest of my post? I only pointed out the yahoo support
> page as a starting point. I wouldn't attack this from a port point of view
> becuase that method would be hit and miss. Find where the music comes from and
> block the ranges it comes from. I stated examples of this with the Yahoo
> LaunchCAST streaming protocol. I don't know the structure of your network so
> it is hard for me to say how to find the culprits. I also used a packet
> sniffer on my network to find where the service was originalting. Stopping
> shoutcast maybe a bit more difficult... I'll look into that as well...
>
> =====
> In the absence of order there will be chaos.
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Friends. Fun. Try the all-new Yahoo! Messenger.
> http://messenger.yahoo.com/
>
>
>
>
>
--
Michael Gale
Network Administrator
Utilitran Corporation
next prev parent reply other threads:[~2004-06-10 23:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 21:37 Blocking Streaming Media (Was: Re: (no subject)..) SBlaze
2004-06-10 23:33 ` Michael Gale [this message]
2004-06-10 23:54 ` SBlaze
-- strict thread matches above, loose matches on Subject: below --
2004-06-01 15:59 Rio Martin
2004-05-31 11:18 (no subject) Ivan
2004-06-01 2:43 ` Blocking Streaming Media (Was: Re: (no subject)..) Rio Martin
2004-06-01 5:37 ` SBlaze
2004-06-01 14:50 ` Michael Gale
2004-06-01 15:59 ` Rio Martin
2004-06-02 7:32 ` Rio Martin
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=20040610173342.6e858194@mgalepc.utilitran.com \
--to=michael.gale@utilitran.com \
--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.