<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[How do I curb torrenting?]]></title><description><![CDATA[<p dir="auto">I just started to provide VM boxes (remote desktop sessions) to traders and people within the finance community.</p>
<p dir="auto">I provide two types of boxes - one that they dedicate 100% to trading and another that we jokingly call a "porn box" because they use it for chat/IM/email (to watch porn), etc.</p>
<p dir="auto">I've got AV solutions handled but what I didn't take into account was the fact that these guys will have access to high bandwidth and can easily torrent. Are there any simple things I can do to deter them from this?</p>
<p dir="auto">I want to make it clear that I don't want to be a policeman and they are purchasing an "open" connection same as they would have at their home, etc. so I can't really say they can/can not do anything specific so I don't want to block or really even throttle but I want to make it such that they come to the conclusion on their own that its easier to not torrent on my VMs.</p>
<p dir="auto">I give each instance a fairly small HDD (100GB) and I'll start to dig into Traffic Shaping - but does anyone have any quick tricks that tend to work?</p>
<p dir="auto">Thx.</p>
]]></description><link>https://forum.netgate.com/topic/39637/how-do-i-curb-torrenting</link><generator>RSS for Node</generator><lastBuildDate>Thu, 08 Oct 2026 13:24:53 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/39637.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 01 Dec 2011 15:07:55 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to How do I curb torrenting? on Mon, 05 Dec 2011 05:36:12 GMT]]></title><description><![CDATA[<p dir="auto">If you want to attempt to block torrents completely then you can check in snort there are rules already for p2p traffic.</p>
<p dir="auto">If you are just concerned of the bandwidth usage you can create a limiter for say 2mbps under Traffic Shaper &gt; Limiter and then set that traffic shaper assigned to the firewall rules. If you use the "per ip" option you can use one set of rules for all clients.</p>
]]></description><link>https://forum.netgate.com/post/307305</link><guid isPermaLink="true">https://forum.netgate.com/post/307305</guid><dc:creator><![CDATA[joako]]></dc:creator><pubDate>Mon, 05 Dec 2011 05:36:12 GMT</pubDate></item><item><title><![CDATA[Reply to How do I curb torrenting? on Sat, 03 Dec 2011 17:10:16 GMT]]></title><description><![CDATA[<p dir="auto">Thanks for the reply.</p>
<p dir="auto">They are getting a VM (Windows or Ubuntu) and its essentially a clean install that they have 100% admin rights to. I don't police, monitor or configure anything on the VM so I can't impliment any local rights/restrictions.</p>
<p dir="auto">My concern isn't really about bandwidth or viruses, etc. because there is more than enough bandwidth and I take daily snapshots so if they destroy the VM with a virus the most they will lose is 1 day's worth of work.</p>
<p dir="auto">My concern is more with my ISP. If someone is seeding something they shouldn't be on a VM that I provide then I have some responsibility for that back to my ISP. I don't think it will be an issue (I personally know all of the people using the VMs at this point) but if the business grows and gets larger I assume there will come a point in time when I don't know every VM user personally and/or someone will abuse/misuse the services.</p>
]]></description><link>https://forum.netgate.com/post/307188</link><guid isPermaLink="true">https://forum.netgate.com/post/307188</guid><dc:creator><![CDATA[pf123user]]></dc:creator><pubDate>Sat, 03 Dec 2011 17:10:16 GMT</pubDate></item><item><title><![CDATA[Reply to How do I curb torrenting? on Thu, 01 Dec 2011 15:40:46 GMT]]></title><description><![CDATA[<p dir="auto">If you're renting out virtual machines then the security policy should be implemented at system level rather than at network level.<br />
It is seriously much easier to implement an endpoint protection system that allows you to block certain software and provide antivirus/antimalware capabilities than to try and throttle and limit traffic once it leaves the "box".</p>
<p dir="auto">The hard way is to actually use L7 to permit legitimate traffic and block everything else.  Once you hit a certain amount of bandwidth being passed, this can bog down your pfSense box though.</p>
<p dir="auto">Another alternative is to identify all the legitimate traffic being used via a mixture of ports/ IPs and L7 then applying a connection rate limit on all other traffic.  i.e. You prioritise legitimate traffic and penalise or block all other traffic using a connection rate limit.<br />
Since torrenting tends to rely on opening large amounts of connections (getting 1Kbps from 1000 seeders gives you 1Mbps so on and so forth), applying a connection limit would reduce the effective torrenting speed.<br />
This can be circumvented if there are few high speed seeders or if the torrenting software is configured to have a very slow connection opening rate and limit on maximum number of open connections though.</p>
]]></description><link>https://forum.netgate.com/post/306884</link><guid isPermaLink="true">https://forum.netgate.com/post/306884</guid><dc:creator><![CDATA[dreamslacker]]></dc:creator><pubDate>Thu, 01 Dec 2011 15:40:46 GMT</pubDate></item></channel></rss>