<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Ingress Policing with Linux and tc</title>
	<atom:link href="http://blog.stevedoria.net/20050906/ingress-policing-with-linux-and-tc/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.stevedoria.net/20050906/ingress-policing-with-linux-and-tc</link>
	<description>Real-World Computing Experience Distilled</description>
	<pubDate>Fri, 21 Nov 2008 11:10:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: shaheem</title>
		<link>http://blog.stevedoria.net/20050906/ingress-policing-with-linux-and-tc#comment-7299</link>
		<dc:creator>shaheem</dc:creator>
		<pubDate>Wed, 27 Aug 2008 06:09:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.stevedoria.net/?p=19#comment-7299</guid>
		<description>thanks i'm gonna try this. how can i give each user an equal amount of BW. ive got some docs but the ones i tried really slow down the server. dunno if this is the norm. it is a mid to low level spec machine tho.</description>
		<content:encoded><![CDATA[<p>thanks i&#8217;m gonna try this. how can i give each user an equal amount of BW. ive got some docs but the ones i tried really slow down the server. dunno if this is the norm. it is a mid to low level spec machine tho.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lucas</title>
		<link>http://blog.stevedoria.net/20050906/ingress-policing-with-linux-and-tc#comment-7295</link>
		<dc:creator>Lucas</dc:creator>
		<pubDate>Fri, 22 Aug 2008 15:02:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.stevedoria.net/?p=19#comment-7295</guid>
		<description>Hi,

This don't work for me.

I want to limit incoming traffic too, but in this case, the link goes slower and slower, but don't stay at specific speed.

at filter, there is a "flowid :1", but, where is this class There isn't any class called ":1", right?

I did read the lartc, but it's getting confused.

If someone can help me, please send me an email.

lucasmocellin@gmail.com

Lucas.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>This don&#8217;t work for me.</p>
<p>I want to limit incoming traffic too, but in this case, the link goes slower and slower, but don&#8217;t stay at specific speed.</p>
<p>at filter, there is a &#8220;flowid :1&#8243;, but, where is this class There isn&#8217;t any class called &#8220;:1&#8243;, right?</p>
<p>I did read the lartc, but it&#8217;s getting confused.</p>
<p>If someone can help me, please send me an email.</p>
<p><a href="mailto:lucasmocellin@gmail.com">lucasmocellin@gmail.com</a></p>
<p>Lucas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kenny</title>
		<link>http://blog.stevedoria.net/20050906/ingress-policing-with-linux-and-tc#comment-7255</link>
		<dc:creator>Kenny</dc:creator>
		<pubDate>Fri, 09 May 2008 20:10:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.stevedoria.net/?p=19#comment-7255</guid>
		<description>The idea is that you slow down the TCP ACKs to the local computer so that it can't eat up all the incoming bandwidth in the future (not for packets that have already arrived). So instead of a steady stream of packets coming at full speed, you get intervals of silence where the server is waiting for the previous packet to be acknowledged. In those intervals of silence things of higher priority can get a chance to come in.</description>
		<content:encoded><![CDATA[<p>The idea is that you slow down the TCP ACKs to the local computer so that it can&#8217;t eat up all the incoming bandwidth in the future (not for packets that have already arrived). So instead of a steady stream of packets coming at full speed, you get intervals of silence where the server is waiting for the previous packet to be acknowledged. In those intervals of silence things of higher priority can get a chance to come in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MockSoul</title>
		<link>http://blog.stevedoria.net/20050906/ingress-policing-with-linux-and-tc#comment-7191</link>
		<dc:creator>MockSoul</dc:creator>
		<pubDate>Wed, 16 Jan 2008 05:59:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.stevedoria.net/?p=19#comment-7191</guid>
		<description>Albert, how you can 'shape' packets which are already sent? There is no way to shape incoming packets.</description>
		<content:encoded><![CDATA[<p>Albert, how you can &#8217;shape&#8217; packets which are already sent? There is no way to shape incoming packets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Albert</title>
		<link>http://blog.stevedoria.net/20050906/ingress-policing-with-linux-and-tc#comment-7019</link>
		<dc:creator>Albert</dc:creator>
		<pubDate>Tue, 01 May 2007 14:48:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.stevedoria.net/?p=19#comment-7019</guid>
		<description>Hi There!! There is something that I still don't get it. Is there a posibility to enqueue incoming traffic and how?

I can see that the example limits the incoming traffic to a fixed rate. But how could I use a hierarchy of queues to do the job. I read the "Linux Advanced Routing &#38; Traffic Control HOWTO" but I couldn't figured out how can I enqueue the incoming traffic.

Thanks for the time.</description>
		<content:encoded><![CDATA[<p>Hi There!! There is something that I still don&#8217;t get it. Is there a posibility to enqueue incoming traffic and how?</p>
<p>I can see that the example limits the incoming traffic to a fixed rate. But how could I use a hierarchy of queues to do the job. I read the &#8220;Linux Advanced Routing &amp; Traffic Control HOWTO&#8221; but I couldn&#8217;t figured out how can I enqueue the incoming traffic.</p>
<p>Thanks for the time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Automatthias</title>
		<link>http://blog.stevedoria.net/20050906/ingress-policing-with-linux-and-tc#comment-111</link>
		<dc:creator>Automatthias</dc:creator>
		<pubDate>Mon, 19 Jun 2006 10:31:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.stevedoria.net/?p=19#comment-111</guid>
		<description>That's a good approach as it allows people to get some actual results quickly. If someone wants to get deeper into details and get more control, they can always read the papers.</description>
		<content:encoded><![CDATA[<p>That&#8217;s a good approach as it allows people to get some actual results quickly. If someone wants to get deeper into details and get more control, they can always read the papers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://blog.stevedoria.net/20050906/ingress-policing-with-linux-and-tc#comment-51</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Thu, 18 May 2006 02:41:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.stevedoria.net/?p=19#comment-51</guid>
		<description>It took me awhile to sit down and wade through documentation, which tended to go through too much theory and background information. The folks that support the Linux Documentation Project are great, and it is through their work that I learned the differences between packet policing and packet shaping. I simply intended this post to serve as a quick howto on setting it up. I'm glad it helped.</description>
		<content:encoded><![CDATA[<p>It took me awhile to sit down and wade through documentation, which tended to go through too much theory and background information. The folks that support the Linux Documentation Project are great, and it is through their work that I learned the differences between packet policing and packet shaping. I simply intended this post to serve as a quick howto on setting it up. I&#8217;m glad it helped.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Herington</title>
		<link>http://blog.stevedoria.net/20050906/ingress-policing-with-linux-and-tc#comment-50</link>
		<dc:creator>Alex Herington</dc:creator>
		<pubDate>Wed, 17 May 2006 22:00:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.stevedoria.net/?p=19#comment-50</guid>
		<description>Excellent! Works flawlessly. I'd also like to report that this works fine throttling NAT'ed traffic from an ethernet interface to a VLAN interface. *VERY* useful considering I've found using tc to limit outgoing traffic on a VLAN interface does *not* work (unless my tests were wrong!).</description>
		<content:encoded><![CDATA[<p>Excellent! Works flawlessly. I&#8217;d also like to report that this works fine throttling NAT&#8217;ed traffic from an ethernet interface to a VLAN interface. *VERY* useful considering I&#8217;ve found using tc to limit outgoing traffic on a VLAN interface does *not* work (unless my tests were wrong!).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
