From: simon <simon.guinot@laposte.net>
To: linux-newbie@vger.kernel.org, wstanard@palmertrinity.org
Subject: Re: filtering .mp3 packets
Date: Wed, 27 Apr 2005 17:22:34 +0200 [thread overview]
Message-ID: <426FAE3A.8070709@laposte.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0504271523260.951-100000@hestia>
hello Bill
>>We've been having some difficulty finding the vocabulary to describe
>>filtering content (for example .mp3 files) over TCP-IP. We would like to
>>set up our Linux server to do some "trapping" of packets containing .mp3
>>files with an eye toward using Linux enabled routing to clean our campus
>>of an overwhelming dose of music downloads and trading. To do this
>>exploration, I need to know what I should call the process I'm trying to
>>perform. Any vocabulary that you can suggest?
>>
>>Bill Stanard
may be you can write a kernel module using the netfilter to perform that...
netfilter is a very powerful way to build every kind of filter.
you can find some informations here :
http://www.ouah.org/p61-0x0d_Hacking_the_Linux_Kernel_Network_Stack.txt
regards
simon
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2005-04-27 15:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 11:27 filtering .mp3 packets William Stanard
2005-04-25 16:56 ` Ray Olszewski
2005-04-26 11:36 ` John T. Williams
2005-04-27 14:15 ` J.
2005-04-27 15:22 ` simon [this message]
2005-04-27 19:51 ` J.
2005-04-27 22:57 ` John T. Williams
2005-04-28 0:39 ` Ray Olszewski
2005-04-29 3:05 ` joy merwin monteiro
2005-04-29 11:43 ` Stephen Ray
2005-04-29 15:24 ` joy merwin monteiro
2005-04-29 15:51 ` Ray Olszewski
2005-04-29 23:39 ` joy merwin monteiro
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=426FAE3A.8070709@laposte.net \
--to=simon.guinot@laposte.net \
--cc=linux-newbie@vger.kernel.org \
--cc=wstanard@palmertrinity.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.