That was the link, as for you question, no idea =P <br><br><div><span class="gmail_quote">On 10/20/07, <b class="gmail_sendername">John Lowry</b> &lt;<a href="mailto:johnlowry@gmail.com">johnlowry@gmail.com</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><a href="http://redhatcat.blogspot.com/2007/09/beating-sandvine-with-linux-iptables.html">http://redhatcat.blogspot.com/2007/09/beating-sandvine-with-linux-iptables.html
</a><br><br>I am definitely NOT a iptables expert, but I think what you are doing is<br>telling the machine to reject TCP packets with the RST flag on the port<br>you tell your bit torrent client to use. Can any people with more
<br>experience/knowledge let us know if this is a good idea? I am seeing<br>maybe legitimate RST messages getting discarded?<br><br>Munjal Thakkar wrote:<br>&gt; there was an article floating around on how to setup a linux based
<br>&gt; router to somehow manipulate outgoing traffic to work with sandvine, it<br>&gt; seemed pretty legit, I&#39;ll have to find the bookmark in a bit.<br>&gt;<br>&gt; On 10/19/07, *John Jefferson Lowry IV* &lt;<a href="mailto:johnlowry@gmail.com">
johnlowry@gmail.com</a><br>&gt; &lt;mailto:<a href="mailto:johnlowry@gmail.com">johnlowry@gmail.com</a>&gt;&gt; wrote:<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Apparently Comcast uses Sandvine equipment to look at the behavior of<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; the traffic versus what it contains. So even if you encrypt it, it
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; will say, &quot;Hey, I am totally bit-torrent.&quot;<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; On 10/19/07, Emerson, Tom (*IC) &lt; <a href="mailto:Tom.Emerson@wbconsultant.com">Tom.Emerson@wbconsultant.com</a><br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;mailto:
<a href="mailto:Tom.Emerson@wbconsultant.com">Tom.Emerson@wbconsultant.com</a>&gt;&gt; wrote:<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; So?&nbsp;&nbsp;Throw an SSL wrapper around the connections...<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; Not only will that prevent comcast from &quot;falsifying traffic&quot;, but it
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; INCREASES the bandwidth consumed ;)<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; &gt; -----Original Message----- Of matti<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; &gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; &gt; well folks... comcast isn&#39;t playing very nicely...
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; &gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; &gt; Comcast blocks some Internet traffic<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; &quot;Comcast&#39;s technology kicks in, though not consistently, when one<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; BitTorrent user attempts to share a complete file with another user.
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; Each PC gets a message invisible to the user that looks like it comes<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; from the other computer, telling it to stop communicating. But neither<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; message originated from the other computer - it comes from Comcast. If
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; it were a telephone conversation, it would be like the operator<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; breaking<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; into the conversation, telling each talker in the voice of the<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; other: &quot;Sorry, I have to hang up. Good bye.&quot; &quot;
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>&gt;<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; --<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; John Lowry<br>&gt;<br>&gt;<br><br><br>--<br>John Lowry<br><a href="mailto:johnlowry@gmail.com">johnlowry@gmail.com</a><br></blockquote></div><br>