From: Luca Ferrari <fluca1978@infinito.it>
To: linux-admin@vger.kernel.org
Subject: how to protect against peer-to-peer?
Date: Mon, 22 Nov 2004 11:27:53 +0100 [thread overview]
Message-ID: <200411221127.53218.fluca1978@infinito.it> (raw)
Hi,
in my network users are increasing the amount of peer-to-peer traffic (e-mule,
winmx), how can I deny the above traffic? I'm using iptables and squid on my
linux firewall, but I don't know if there's a specific port to lock or
something else I can use to recognize the "bad" packet in the network
traffic.
Thanks,
Luca
--
Luca Ferrari,
fluca1978@infinito.it
next reply other threads:[~2004-11-22 10:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 10:27 Luca Ferrari [this message]
2004-11-22 13:02 ` how to protect against peer-to-peer? urgrue
2004-11-22 13:39 ` Adam Lang
2004-11-22 13:53 ` Adrian C.
2004-11-22 13:57 ` Adrian C.
2005-02-12 1:01 ` RH Ent. 3.0 = no support for firewire HD? Eve Atley
2005-03-22 19:49 ` Best way to enable 'guest' access onto Linux fileserver? Eve Atley
2005-03-22 20:09 ` Grant Coady
2005-03-23 16:15 ` Jens Knoell
2005-03-23 21:10 ` Eve Atley
2005-03-23 23:01 ` Jens Knoell
2005-03-28 16:53 ` Resolved: " Eve Atley
2004-11-22 15:53 ` how to protect against peer-to-peer? Jens Knoell
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=200411221127.53218.fluca1978@infinito.it \
--to=fluca1978@infinito.it \
--cc=linux-admin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).