<?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/"
	xmlns:series="https://publishpress.com/"
	
	>
<channel>
	<title>
	Comments on: Host to Host through a Switch	</title>
	<atom:link href="https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/</link>
	<description>Networking presented simply, practically, and applicably</description>
	<lastBuildDate>Fri, 04 Oct 2024 18:55:41 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Juan		</title>
		<link>https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-254669</link>

		<dc:creator><![CDATA[Juan]]></dc:creator>
		<pubDate>Fri, 04 Oct 2024 18:55:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=642#comment-254669</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-7823&quot;&gt;Ed Harmoush&lt;/a&gt;.

what i understand from all of this is that when Host1 send a message to Host2 once it hits the switch, the switch will flood an address resolution to everyone except the originator, that way when the host with the right Ip address receives this message it will send a message back (Ack) to the switch and this is when the switch takes the MAC Address and writes it down on the table &quot;learning&quot; a new MAC address for an IP address he already knew.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-7823">Ed Harmoush</a>.</p>
<p>what i understand from all of this is that when Host1 send a message to Host2 once it hits the switch, the switch will flood an address resolution to everyone except the originator, that way when the host with the right Ip address receives this message it will send a message back (Ack) to the switch and this is when the switch takes the MAC Address and writes it down on the table &#8220;learning&#8221; a new MAC address for an IP address he already knew.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: s. ponce		</title>
		<link>https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-254500</link>

		<dc:creator><![CDATA[s. ponce]]></dc:creator>
		<pubDate>Tue, 02 Jul 2024 18:50:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=642#comment-254500</guid>

					<description><![CDATA[I was curious to ask, say there are two devices with different subnets both connected to a regular switch (not managed). if the switch only cares about the mac addresses, why couldn&#039;t an application establish communication from one device to the other?. the switch knows the ports computer a and b are connected to, along with the mac address for each. does the application care about the ip addresses not being in the same subnet? or it depends on the the protocol use, maybe some protocols care, where others don&#039;t. this is a question that has been haunting me for a while, I apologize if the intent of the question is not inherently clear, I don&#039;t deal with networks much but I have run into this type of scenarios. thanks!]]></description>
			<content:encoded><![CDATA[<p>I was curious to ask, say there are two devices with different subnets both connected to a regular switch (not managed). if the switch only cares about the mac addresses, why couldn&#8217;t an application establish communication from one device to the other?. the switch knows the ports computer a and b are connected to, along with the mac address for each. does the application care about the ip addresses not being in the same subnet? or it depends on the the protocol use, maybe some protocols care, where others don&#8217;t. this is a question that has been haunting me for a while, I apologize if the intent of the question is not inherently clear, I don&#8217;t deal with networks much but I have run into this type of scenarios. thanks!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Karpurapu Rahul		</title>
		<link>https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-249257</link>

		<dc:creator><![CDATA[Karpurapu Rahul]]></dc:creator>
		<pubDate>Sat, 10 Jul 2021 07:09:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=642#comment-249257</guid>

					<description><![CDATA[flooding will never be done when A wants to send to B. As we can see in the animation, the destination MAC was filled with that of the MAC address of B. How did A know the MAC address of B? A learnt it during the ARP protocol. So when B was sending its MAC address as a response to the ARP done by A, it had to go through the switch and then the switch would have learnt that the port on which b sits is 2. So there was no need for flooding to be done when A wants to send a message to B.]]></description>
			<content:encoded><![CDATA[<p>flooding will never be done when A wants to send to B. As we can see in the animation, the destination MAC was filled with that of the MAC address of B. How did A know the MAC address of B? A learnt it during the ARP protocol. So when B was sending its MAC address as a response to the ARP done by A, it had to go through the switch and then the switch would have learnt that the port on which b sits is 2. So there was no need for flooding to be done when A wants to send a message to B.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Ed Harmoush		</title>
		<link>https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-247287</link>

		<dc:creator><![CDATA[Ed Harmoush]]></dc:creator>
		<pubDate>Mon, 07 Jun 2021 18:03:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=642#comment-247287</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-247181&quot;&gt;Jenny&lt;/a&gt;.

You&#039;re welcome =).

Yes, you are correct on both points.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-247181">Jenny</a>.</p>
<p>You&#8217;re welcome =).</p>
<p>Yes, you are correct on both points.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jenny		</title>
		<link>https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-247181</link>

		<dc:creator><![CDATA[Jenny]]></dc:creator>
		<pubDate>Sat, 05 Jun 2021 12:22:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=642#comment-247181</guid>

					<description><![CDATA[Thank you Ed for your brilliant  in-depth illumination of ARP process. 

Just one thing, I wish to clarify :    The switch has the job to do flooding for the broadcast frame, rather than to initiate the broadcast frame.     Whereas the Host has the job to initiate the broadcast frame. 

Now, after the ARP request got initiated, the host then placed the ARP request onto the connected wire(s), allowing its ethernet LINK to take care of the actual delivery of the broadcast frames. This means the cable wire(s) will deliver the ARP request to all DIRECTLY CONNECTED neighbours.   Hope my interpretation of your article was on the right track. Many thanks !]]></description>
			<content:encoded><![CDATA[<p>Thank you Ed for your brilliant  in-depth illumination of ARP process. </p>
<p>Just one thing, I wish to clarify :    The switch has the job to do flooding for the broadcast frame, rather than to initiate the broadcast frame.     Whereas the Host has the job to initiate the broadcast frame. </p>
<p>Now, after the ARP request got initiated, the host then placed the ARP request onto the connected wire(s), allowing its ethernet LINK to take care of the actual delivery of the broadcast frames. This means the cable wire(s) will deliver the ARP request to all DIRECTLY CONNECTED neighbours.   Hope my interpretation of your article was on the right track. Many thanks !</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Student		</title>
		<link>https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-245077</link>

		<dc:creator><![CDATA[Student]]></dc:creator>
		<pubDate>Tue, 11 May 2021 17:03:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=642#comment-245077</guid>

					<description><![CDATA[Assume that the ARP tables of both devices (laptop and Raspberry) and the MAC address table of the switch are initially empty. Your laptop will now send 3 ping requests to the IP address of the Raspberries. Describe step by step,
which messages are sent from which host and where and when the information in the various tables is updated]]></description>
			<content:encoded><![CDATA[<p>Assume that the ARP tables of both devices (laptop and Raspberry) and the MAC address table of the switch are initially empty. Your laptop will now send 3 ping requests to the IP address of the Raspberries. Describe step by step,<br />
which messages are sent from which host and where and when the information in the various tables is updated</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Ed Harmoush		</title>
		<link>https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-243260</link>

		<dc:creator><![CDATA[Ed Harmoush]]></dc:creator>
		<pubDate>Thu, 15 Apr 2021 17:37:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=642#comment-243260</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-243041&quot;&gt;nabilshazain&lt;/a&gt;.

You&#039;re welcome =)]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-243041">nabilshazain</a>.</p>
<p>You&#8217;re welcome =)</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Ed Harmoush		</title>
		<link>https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-243258</link>

		<dc:creator><![CDATA[Ed Harmoush]]></dc:creator>
		<pubDate>Thu, 15 Apr 2021 17:35:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=642#comment-243258</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-242453&quot;&gt;Anntria&lt;/a&gt;.

The hosts will still use IP addresses to speak to each other. The Switch, however, will never look into the L3 header to see the IP headers.  See this for more info:

https://www.youtube.com/watch?v=gYN2qN11-wE]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-242453">Anntria</a>.</p>
<p>The hosts will still use IP addresses to speak to each other. The Switch, however, will never look into the L3 header to see the IP headers.  See this for more info:</p>
<p><a href="https://www.youtube.com/watch?v=gYN2qN11-wE" rel="nofollow ugc">https://www.youtube.com/watch?v=gYN2qN11-wE</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: nabilshazain		</title>
		<link>https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-243041</link>

		<dc:creator><![CDATA[nabilshazain]]></dc:creator>
		<pubDate>Sun, 11 Apr 2021 14:20:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=642#comment-243041</guid>

					<description><![CDATA[this is wonderful post.. Thank you dear Sir]]></description>
			<content:encoded><![CDATA[<p>this is wonderful post.. Thank you dear Sir</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Anntria		</title>
		<link>https://www.practicalnetworking.net/series/packet-traveling/host-to-host-through-a-switch/#comment-242453</link>

		<dc:creator><![CDATA[Anntria]]></dc:creator>
		<pubDate>Thu, 01 Apr 2021 06:50:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=642#comment-242453</guid>

					<description><![CDATA[How does 2 hosts communicate with each other with only a single switch in between.MAC addresses of both the hosts are given but IP address is not mentioned]]></description>
			<content:encoded><![CDATA[<p>How does 2 hosts communicate with each other with only a single switch in between.MAC addresses of both the hosts are given but IP address is not mentioned</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
