Has anybody come up with a rule set that will disable music sharing and file sharing bit torrent technologies?

BearShare LimeWire eDonkey ... etc?


Thanks,
Jim

The lazy way is to take advantage of the router's smart defense -

UNDER SECURITY/ SMARTDEFENSE TAB/ Near the bottom open the PEER to PEER Folder -

You can block Kazaa/ gnutella / emule / BitTorrent and Winny.

Thanks Stan

Lazy R US ;-)
(Well outta-control and over-worked fit in there somewhere as well ;-)

Jim

~~~~~~~~~~~~~~~~~~~~~

UNDER SECURITY/ SMARTDEFENSE TAB/ Near the bottom open the PEER to PEER Folder -

You can block Kazaa/ gnutella / emule / BitTorrent and Winny.

Speaking of Blocking sites / protocols at the gateway - I also use http://opendns.com/ - sign up for a FREE account and you can block porn that may be missed by the z100g.

In case you have some computer literate smart kids, you can write a rule to block DNS (53) except for the opendns servers 208.67.222.222 and 208.67.220.220. ( You have to set up the z100g to use them)

It also corrects typos - like when someone types in .cm instead of .com which is a big source of malware.

And another way I block sites like doubleclick etc is I use http://www.mvps.org/winhelp2002/hosts.htm via the host file. (ONE MAJOR ISSUE is that the site zonealarm uses for live chat iad. something is blocked. You have to comment that out.) Second issue is to make sure you diable windows xp DNS client via "Services Editor" - it's on the web page.

Thanks Stan!

I had tried OpenDNS on my home router a while back and it hosed up my VPN connection into work somehow, but that is not a problem at the church where this router is located, so I'm on it!

For the permanent PCs there I'll also make the host file & DNS updates!

Jim

The SmartDefense Peer-to-Peer blocking features will block most of the "low hanging fruit", but some of the more configurable torrent clients such Azureus can be set to preference encrypted connections only which will render SmartDefense (or most endpoint protection) useless.

Obviously without port-forwards internally the client will have a low id (download/upload ratio) which can minimize downloads. Unfortunately most of the updated torrent "how tos" are showing users to use encryption to get around ISP traffic shaping.

You can also set up a SYSLOG server and forward your logs to the server and perform some pattern matching on accept/deny traffic to determine if someone is using a BitTorrent client and then follow up directly with the end user.

Thanks cbischoff!

Hopefully I will not have to resort to such advanced tactics... to keep the teenagers at bay, but now I have ammo if I need it ;-)

Jim