<?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>Network Educator &#187; Addresses</title>
	<atom:link href="http://www.networkeducator.com/tag/addresses/feed" rel="self" type="application/rss+xml" />
	<link>http://www.networkeducator.com</link>
	<description>Lets network our blog</description>
	<lastBuildDate>Fri, 27 Jan 2012 11:30:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Troubleshooting TCP/IP</title>
		<link>http://www.networkeducator.com/troubleshooting-tcpip.htm</link>
		<comments>http://www.networkeducator.com/troubleshooting-tcpip.htm#comments</comments>
		<pubDate>Fri, 25 Nov 2011 07:30:23 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[access]]></category>
		<category><![CDATA[Addresses]]></category>
		<category><![CDATA[Analyzing traffic]]></category>
		<category><![CDATA[packet]]></category>
		<category><![CDATA[parsing]]></category>
		<category><![CDATA[REMOTE]]></category>
		<category><![CDATA[TCP/IP]]></category>
		<category><![CDATA[troubleshooting]]></category>

		<guid isPermaLink="false">http://www.networkeducator.com/?p=254</guid>
		<description><![CDATA[1)   Analyzing traffic using network monitor Frame is an encapsulation of network interface layer (layer 2) data. Each frame contains source and destination computer addresses, header of the protocol used to send data and data itself. Packet is an encapsulation of internet layer (layer 3) data There are two versions of Network Monitor, the basic version [...]]]></description>
		<wfw:commentRss>http://www.networkeducator.com/troubleshooting-tcpip.htm/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How Switches Learn Addresses</title>
		<link>http://www.networkeducator.com/how-switches-learn-addresses.htm</link>
		<comments>http://www.networkeducator.com/how-switches-learn-addresses.htm#comments</comments>
		<pubDate>Tue, 24 Nov 2009 11:59:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Networking Basics]]></category>
		<category><![CDATA[Addresses]]></category>
		<category><![CDATA[Catalyst]]></category>
		<category><![CDATA[forwarding]]></category>
		<category><![CDATA[MAC]]></category>
		<category><![CDATA[Switches]]></category>

		<guid isPermaLink="false">http://www.networkeducator.com/?p=575</guid>
		<description><![CDATA[How Switches Learn Addresses &#8211; A switch uses its bridge forwarding table (called a MAC table in Catalyst) address table when forwarding frames to devices. With an enpty bridge forwarding table, the switch must flood frames to all ports other than the one it arrivied on. This is the least-efficient way to transmit data.   [...]]]></description>
		<wfw:commentRss>http://www.networkeducator.com/how-switches-learn-addresses.htm/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

