<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: QOS when receive traffic is more than transmit</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/qos-when-receive-traffic-is-more-than-transmit/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/qos-when-receive-traffic-is-more-than-transmit/</link>
	<description></description>
	<lastBuildDate>Tue, 18 Jun 2013 20:45:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: elhammster</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/qos-when-receive-traffic-is-more-than-transmit/#comment-67645</link>
		<dc:creator>elhammster</dc:creator>
		<pubDate>Tue, 01 Sep 2009 15:03:36 +0000</pubDate>
		<guid isPermaLink="false">#comment-67645</guid>
		<description><![CDATA[While you can&#039;t prioritize incoming traffic without cooperation from your ISP, you can do some crude QOS&#039;ing by restricting how much bandwidth you will allow the other incoming protocols to have. 

If you think your normal Webex traffic is 2Mb, then you would allow Webex to occupy 2Mb of the pipe which leaves 6Mb for other protocols. Drop the packets at your router which exceed 6Mb for the other protocols. TCP/IP will automatically slow down the requests for more packets to try and ensure that the requester receives all packets.

I have used this method when I had a pipe that was only 512kbps to try and guarantee my video conference data. As I said, this is a crude method and not very accurate, but it can help if you need to ensure that at least some b/w is available for other protocols.]]></description>
		<content:encoded><![CDATA[<p>While you can&#8217;t prioritize incoming traffic without cooperation from your ISP, you can do some crude QOS&#8217;ing by restricting how much bandwidth you will allow the other incoming protocols to have. </p>
<p>If you think your normal Webex traffic is 2Mb, then you would allow Webex to occupy 2Mb of the pipe which leaves 6Mb for other protocols. Drop the packets at your router which exceed 6Mb for the other protocols. TCP/IP will automatically slow down the requests for more packets to try and ensure that the requester receives all packets.</p>
<p>I have used this method when I had a pipe that was only 512kbps to try and guarantee my video conference data. As I said, this is a crude method and not very accurate, but it can help if you need to ensure that at least some b/w is available for other protocols.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.012 seconds using memcached
Object Caching 268/271 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-06-18 21:09:17 -->