I know that I was running into that issue when I was running a node, and that I ended up having to use an obscure version of Cisco’s NBAR functionality to do deep inspection and block the traffic.
Additionally, I know that several content filter manufacturers have the “Block P2P” capability built-in to their devices, there’s got to be some kind of GPL code of what to look for. I can tell you from experience that blocking ports doesn’t work, since the Torrent clients can switch to port 80… it has to be something in the firewall code that can look for Torrent headers. From: [email protected] [mailto:[email protected]] On Behalf Of Drew Sent: Sunday, January 23, 2011 9:55 AM To: [email protected] Subject: [SCFN] P2P blocking....... Just for discussion sake. We are getting a few notices here and there from ISPs about copyrighted material downloads. Not too many, but more than we used to. Some of the connection owners are asking about their liability issues. I really hate to even broach this subject since blocking ports on SoCalFreeNet.Org, minus email spam, has been something we have always fought. So the question is, can you effectively block P2P traffic anyways? Some torrent clients seem to be pretty effective at shifting ports. Thoughts? Drew
_______________________________________________ SoCalFreeNet.org General Discussion List To unsubscribe, please visit: http://socalfreenet.org/mailman/listinfo/discuss_socalfreenet.org
