General discussion


Restricting P2P. How?

By catsforus ·
Is there a way to restrict the use of P2P? I know that shaping would place some restrictions on this. However programs such as Bitcomet and Limwire do they uses a specific port or protocol that could be shutdown or restricted by bandwidth?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by adembo In reply to Restricting P2P. How?

Here is my simple answer. They all access the interent, which is obviously on port 80. So what I have done, is (assuming you are not using a proxy server) add to the hosts file for those websites. Direct limewire traffic to or to a site on your network. You may need to find out what the IP is, but that could take care of most of it, besides not giving your users admin access to allow them to install the apps, would be my advice.

Collapse -

by catsforus In reply to
Collapse -

by Toivo Talikka In reply to Restricting P2P. How?

Firewall appliances and firewall applications have usually sets of rules available to block applications that tunnel P2P traffic over HTTP.

For example, have a look at the signatures are already in the ISA 2004 firewall:

Then there are also P2P and IM sniffer applications designed to work with the ISA 2004 firewall.

On the other hand, if you enforce a policy where users can access only websites they need for work, the problem with P2P would disappear.

Collapse -

by catsforus In reply to
Collapse -

by catsforus In reply to Restricting P2P. How?

This question was closed by the author

Related Discussions

Related Forums