All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Lowth" <chris@lowth.com>
To: Jeffrey Laramie <JALaramie@Loudoun-Fairfax.com>, ksmith@perfht.com
Cc: netfilter@lists.netfilter.org
Subject: Re: Kazaa Ports
Date: Thu, 11 Sep 2003 10:08:23 +0100	[thread overview]
Message-ID: <002a01c37844$417cc0f0$0900a8c0@lowth.com> (raw)
In-Reply-To: 3F5F6EA2.3030303@Loudoun-Fairfax.com

[-- Attachment #1: Type: text/plain, Size: 751 bytes --]

http://www.lowth.com/p2pwall will block kazaa using iptables "QUEUE" target, if that's what you're after.
It's written up in the October 2003 issue of the Linux Journal (www.linuxjournal.com) 
  ----- Original Message ----- 
  From: Jeffrey Laramie 
  To: ksmith@perfht.com 
  Cc: netfilter@lists.netfilter.org 
  Sent: Wednesday, September 10, 2003 7:34 PM
  Subject: Re: Kazaa Ports




  Kevin Smith wrote:

I found this web site with a bit on info about Blocking p2p programs.:

http://testweb.oofle.com/messaging/index.htm

Hope it helps. 

Kev
  Thanks to everyone for their suggestions. I've got my resident Kazaa experts (aka children) doing some research on this also. This may take a few days, so stay tuned.

  Jeff

[-- Attachment #2: Type: text/html, Size: 2162 bytes --]

  reply	other threads:[~2003-09-11  9:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <NGBBLGFEALDADHNDAAFFIEPEDKAA.ksmith@perfht.com>
2003-09-10 18:34 ` Kazaa Ports Jeffrey Laramie
2003-09-11  9:08   ` Chris Lowth [this message]
2003-09-09  8:21 jimbo jones
2003-09-09 13:51 ` Jeffrey Laramie
2003-09-09 18:25   ` SBlaze
  -- strict thread matches above, loose matches on Subject: below --
2003-09-08 15:49 Jeffrey Laramie
2003-09-08 17:01 ` SBlaze
2003-09-08 17:48   ` Jeffrey Laramie
2003-09-08 21:02     ` SBlaze
2003-09-08 22:47       ` Jeffrey Laramie
2003-09-09  3:53         ` 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='002a01c37844$417cc0f0$0900a8c0@lowth.com' \
    --to=chris@lowth.com \
    --cc=JALaramie@Loudoun-Fairfax.com \
    --cc=ksmith@perfht.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.