All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Awie" <awie@eksadata.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Kazaa
Date: Tue, 02 Sep 2003 07:53:09 +0000	[thread overview]
Message-ID: <marc-lartc-106248929321442@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106240635718517@msgid-missing>

Thanks Rio, I will try.

Thx & Rgds,

Awie

----- Original Message -----
From: "Rio Martin" <rio@martin.mu>
To: <lartc@mailman.ds9a.nl>
Sent: Tuesday, September 02, 2003 8:43 AM
Subject: Re: [LARTC] Kazaa


> On Monday 01 September 2003 17:01, Tom Verbeek wrote:
> > Hi Awie,
> > I you simply want to block Kazaa, you need to set up a Firewall that
> > is restrictive of outgoing requests (Kazaa does not need to have
> > incoming ports forwarded or open).
> > Block this Port 1214/TCP (incoming and outgoing).
> > Cheers,
> > Tom.
>
> Kazaa use random ports if you blocked tcp port 1214.
> Have you checked this P2P software ? There is SOCKS support, so if you
blocked
> tcp port 1214, your users still able to comunicate with Kazaa gateway
through
> SOCKS proxy.
>
> Perhaps you should take this as solution to your problem, blocked all tcp
port
> from 1 - 65535, list any ports to be allowed by your firewall.
>
> Regards,
> Rio Martin.
> --
>
>
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-09-02  7:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-01  8:49 [LARTC] Kazaa Awie
2003-09-01 10:01 ` Tom Verbeek
2003-09-01 15:34 ` gypsy
2003-09-02  0:43 ` Rio Martin
2003-09-02  7:53 ` Awie [this message]
2003-09-02  8:07 ` Robert Penz
2003-09-02  9:28 ` miller69
2003-09-02  9:29 ` miller69

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=marc-lartc-106248929321442@msgid-missing \
    --to=awie@eksadata.com \
    --cc=lartc@vger.kernel.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.