<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Ali Abbas &#187; TCP/IP</title>
	<atom:link href="http://alouche.net/blog/category/networking/tcpip/feed/" rel="self" type="application/rss+xml" />
	<link>http://alouche.net/blog</link>
	<description>Unix - Networking - News</description>
	<lastBuildDate>Sun, 11 Jul 2010 17:05:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>QinQ Vlan tagging and S-Vlans</title>
		<link>http://alouche.net/blog/2010/01/20/qinq-vlan-tagging-and-s-vlans/</link>
		<comments>http://alouche.net/blog/2010/01/20/qinq-vlan-tagging-and-s-vlans/#comments</comments>
		<pubDate>Wed, 20 Jan 2010 18:30:51 +0000</pubDate>
		<dc:creator>Ali Abbas</dc:creator>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[Switching & Routing]]></category>
		<category><![CDATA[TCP/IP]]></category>
		<category><![CDATA[WAN]]></category>
		<category><![CDATA[qinq]]></category>
		<category><![CDATA[s-vlan]]></category>
		<category><![CDATA[vlan]]></category>

		<guid isPermaLink="false">http://alouche.net/blog/?p=773</guid>
		<description><![CDATA[Pre-requiste: Understanding of the 802.1Q Protocol The purpose of this post is to shed a light on how QinQ Vlan takes place in a bridged network environment. Before continuing, it is important to keep in mind that 802.1QinQ or 802.1ad isn&#8217;t a defined protocol in itself but a mere amendment of the already existing 802.1Q [...]]]></description>
		<wfw:commentRss>http://alouche.net/blog/2010/01/20/qinq-vlan-tagging-and-s-vlans/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Nagle&#8217;s algorithm and TCP throughput</title>
		<link>http://alouche.net/blog/2009/10/29/the-nagles-algorithm-and-tcp-throughput/</link>
		<comments>http://alouche.net/blog/2009/10/29/the-nagles-algorithm-and-tcp-throughput/#comments</comments>
		<pubDate>Thu, 29 Oct 2009 20:57:11 +0000</pubDate>
		<dc:creator>Ali Abbas</dc:creator>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[TCP/IP]]></category>

		<guid isPermaLink="false">http://alouche.net/blog/?p=743</guid>
		<description><![CDATA[Who talks about about TCP throughput unfortunately can&#8217;t step away from the congestion problem that often occurs in TCP session connections. There are many TCP Congestion Algorithms, from Window Sliding to Fast Recovery; In this post I will only focus on the Nagle&#8217;s algorithm and how applications can be tweaked to either make use of [...]]]></description>
		<wfw:commentRss>http://alouche.net/blog/2009/10/29/the-nagles-algorithm-and-tcp-throughput/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ethernet flow control and IGMP snooping</title>
		<link>http://alouche.net/blog/2009/09/23/ethernet-flow-control-and-igmp-snooping/</link>
		<comments>http://alouche.net/blog/2009/09/23/ethernet-flow-control-and-igmp-snooping/#comments</comments>
		<pubDate>Wed, 23 Sep 2009 17:54:40 +0000</pubDate>
		<dc:creator>Ali Abbas</dc:creator>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[TCP/IP]]></category>
		<category><![CDATA[checkpoint]]></category>
		<category><![CDATA[ethernet]]></category>
		<category><![CDATA[flow control]]></category>
		<category><![CDATA[igmp]]></category>
		<category><![CDATA[igmp snooping]]></category>
		<category><![CDATA[tcp]]></category>

		<guid isPermaLink="false">http://alouche.net/blog/?p=497</guid>
		<description><![CDATA[It is important to note that TCP flow control mechanism as well as Ethernet flow control mechanism are completely 2 different mechanism, which strive to achieve the same unique goal but when in used, are completely unaware of each other. As a matter of fact, Ethernet flow control can fully alienate your network if not [...]]]></description>
		<wfw:commentRss>http://alouche.net/blog/2009/09/23/ethernet-flow-control-and-igmp-snooping/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Mathis Equation and TCP performance</title>
		<link>http://alouche.net/blog/2009/09/16/mathis-equation-and-tcp-performance/</link>
		<comments>http://alouche.net/blog/2009/09/16/mathis-equation-and-tcp-performance/#comments</comments>
		<pubDate>Wed, 16 Sep 2009 16:39:23 +0000</pubDate>
		<dc:creator>Ali Abbas</dc:creator>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[TCP/IP]]></category>
		<category><![CDATA[bandwidth]]></category>
		<category><![CDATA[mss]]></category>
		<category><![CDATA[mtu]]></category>
		<category><![CDATA[tcp]]></category>

		<guid isPermaLink="false">http://alouche.net/blog/?p=483</guid>
		<description><![CDATA[As simple as possible laid off, the Mathis equation goes as follow Rate &#60;= (MSS/RTT)*(1 / p) MSS This is the Maximum Segment Size, which is the MTU excluding the TCP/IP headers. MSS = MTU &#8211; TCP/IP headers &#8211; for example 1460 with an MTU of 1500 (20b IP and 20b TCP headers) RTT RTT [...]]]></description>
		<wfw:commentRss>http://alouche.net/blog/2009/09/16/mathis-equation-and-tcp-performance/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>How to reverse engineer a subnet</title>
		<link>http://alouche.net/blog/2008/10/30/how-to-reverse-engineer-a-subnet/</link>
		<comments>http://alouche.net/blog/2008/10/30/how-to-reverse-engineer-a-subnet/#comments</comments>
		<pubDate>Thu, 30 Oct 2008 22:10:04 +0000</pubDate>
		<dc:creator>Ali Abbas</dc:creator>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[TCP/IP]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[subnet]]></category>

		<guid isPermaLink="false">http://alouche.net/?p=86</guid>
		<description><![CDATA[Alright.. Alright! everbody have their own method to reverse engineer a subnet&#8230; Here is a technic and way that works for me and might work for you. Let&#8217;s take a random private ip. IP: 192.168.1.95/27 And let&#8217;s try to figure out its network range. In such case, we will take the lowest subnet octect, which [...]]]></description>
		<wfw:commentRss>http://alouche.net/blog/2008/10/30/how-to-reverse-engineer-a-subnet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->