I didn&#39;t cap it. Might have been the ISP.<span></span><br><br>On Friday, February 15, 2013, Marc Juul  wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Feb 15, 2013 at 9:46 AM, Matthew Meier &lt;<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;wolfy@wlfy.it&#39;)">wolfy@wlfy.it</a>&gt; wrote:<br>

&gt; Looks like space (192.168.0.3) is consuming 100% of our bandwidth. anyone<br>
&gt; know what&#39;s up with that? if it&#39;s bit  torrent can we cap it around 3 Mbit<br>
&gt; to allow some wiggle room for user&#39;s connections?<br>
<br>
Yeah that was me. I limited the bandwidth thinking the unit was<br>
kilobits and it was actually kilobytes. Sorry for the trouble. I have<br>
now limited the bandwidth to 2 mbit down, and a tiny bit up, so you<br>
can uncap the connection at the router/firewall (it seems to be capped<br>
at 400 kbit/sec right now).<br>
<br>
--<br>
Marc Juul<br>
</blockquote>