Peer-to-Peer

SmartDefense can block peer-to-peer file-sharing traffic, by identifying the proprietary protocols and preventing the initial connection to the peer-to-peer networks. This prevents not only downloads, but also search operations.

This category includes the following nodes:

BitTorrent
eMule
Gnutella
KaZaA
Winny

Note: SmartDefense can detect peer-to-peer traffic regardless of the TCP port being used to initiate the session.

In each node, you can configure how peer-to-peer connections of the selected type should be handled, using the following table.

Peer to Peer Fields

In this field…	Do this…
Action	Specify what action to take when a connection is attempted, by selecting one of the following: Block. Block the connection. None. No action. This is the default.
Track	Specify whether to log peer-to-peer connections, by selecting one of the following: Log. Log the connection. None. Do not log the connection. This is the default.
Block proprietary protocols on all ports	Specify whether proprietary protocols should be blocked on all ports, by selecting one of the following: Block. Block the proprietary protocol on all ports. This in effect prevents all communication using this peer-to-peer application. This is the default. None. Do not block the proprietary protocol on all ports.
Block masquerading over HTTP protocol	Specify whether to block using the peer-to-peer application over HTTP, by selecting one of the following: Block. Block using the application over HTTP. This is the default. None. Do not block using the application over HTTP. This field is not relevant for eMule and Winny.