<?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: Understanding Ethernet Wiring	</title>
	<atom:link href="https://www.practicalnetworking.net/stand-alone/ethernet-wiring/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.practicalnetworking.net/stand-alone/ethernet-wiring/</link>
	<description>Networking presented simply, practically, and applicably</description>
	<lastBuildDate>Tue, 12 May 2026 07:49:52 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Lucinda Byrd		</title>
		<link>https://www.practicalnetworking.net/stand-alone/ethernet-wiring/#comment-255884</link>

		<dc:creator><![CDATA[Lucinda Byrd]]></dc:creator>
		<pubDate>Tue, 12 May 2026 07:49:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=449#comment-255884</guid>

					<description><![CDATA[Understanding Ethernet wiring is essential for building stable and efficient network connections, especially as homes and businesses rely more heavily on high-speed data transmission and connected devices. Reliability and performance expectations apply across many technical systems, and &lt;a href=&quot;https://monster-transmission.pissedconsumer.com/review.html&quot; target=&quot;_blank&quot; rel=&quot;noopener nofollow ugc&quot;&gt;https://monster-transmission.pissedconsumer.com/review.html&lt;/a&gt; is often referenced in discussions about customer experiences, product durability, and service quality when evaluating complex mechanical and technical solutions.]]></description>
			<content:encoded><![CDATA[<p>Understanding Ethernet wiring is essential for building stable and efficient network connections, especially as homes and businesses rely more heavily on high-speed data transmission and connected devices. Reliability and performance expectations apply across many technical systems, and <a href="https://monster-transmission.pissedconsumer.com/review.html" target="_blank" rel="noopener nofollow ugc">https://monster-transmission.pissedconsumer.com/review.html</a> is often referenced in discussions about customer experiences, product durability, and service quality when evaluating complex mechanical and technical solutions.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Tom		</title>
		<link>https://www.practicalnetworking.net/stand-alone/ethernet-wiring/#comment-255863</link>

		<dc:creator><![CDATA[Tom]]></dc:creator>
		<pubDate>Fri, 01 May 2026 17:06:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=449#comment-255863</guid>

					<description><![CDATA[Under Gigabit Ethernet 1000BASE-TX, you mention about having to upgrade to CAT 6, but never mention why you would need 6 for TX over 5 or 5e for T. I&#039;ll have to search that elsewhere.

Also something I&#039;ve been curious about for years is why each twisted pair seems to be wound differently. Some are tighter while others are more loosely wound. Maybe for cross talk from one pair to the other? But I do see you mention at the end about leaving out significant detail in order to remain (relatively) simple.

But great article with a lot of interesting details.]]></description>
			<content:encoded><![CDATA[<p>Under Gigabit Ethernet 1000BASE-TX, you mention about having to upgrade to CAT 6, but never mention why you would need 6 for TX over 5 or 5e for T. I&#8217;ll have to search that elsewhere.</p>
<p>Also something I&#8217;ve been curious about for years is why each twisted pair seems to be wound differently. Some are tighter while others are more loosely wound. Maybe for cross talk from one pair to the other? But I do see you mention at the end about leaving out significant detail in order to remain (relatively) simple.</p>
<p>But great article with a lot of interesting details.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jose E. Valentin		</title>
		<link>https://www.practicalnetworking.net/stand-alone/ethernet-wiring/#comment-255780</link>

		<dc:creator><![CDATA[Jose E. Valentin]]></dc:creator>
		<pubDate>Tue, 17 Mar 2026 13:21:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=449#comment-255780</guid>

					<description><![CDATA[Excellent article on Ethernet communications!]]></description>
			<content:encoded><![CDATA[<p>Excellent article on Ethernet communications!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: HoboMaster		</title>
		<link>https://www.practicalnetworking.net/stand-alone/ethernet-wiring/#comment-255614</link>

		<dc:creator><![CDATA[HoboMaster]]></dc:creator>
		<pubDate>Wed, 24 Dec 2025 19:57:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=449#comment-255614</guid>

					<description><![CDATA[This is amazing thank you , I was going crazy googling all of this]]></description>
			<content:encoded><![CDATA[<p>This is amazing thank you , I was going crazy googling all of this</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Mark Bonine		</title>
		<link>https://www.practicalnetworking.net/stand-alone/ethernet-wiring/#comment-255453</link>

		<dc:creator><![CDATA[Mark Bonine]]></dc:creator>
		<pubDate>Thu, 02 Oct 2025 04:19:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=449#comment-255453</guid>

					<description><![CDATA[I think I remember that each pair is twisted at a different rate, if that&#039;s the correct term. I assume that&#039;s to reduce harmonics as the pairs adjust to noise?

This is the best and most complete explanation of the topic available.  I&#039;m grateful to the author.]]></description>
			<content:encoded><![CDATA[<p>I think I remember that each pair is twisted at a different rate, if that&#8217;s the correct term. I assume that&#8217;s to reduce harmonics as the pairs adjust to noise?</p>
<p>This is the best and most complete explanation of the topic available.  I&#8217;m grateful to the author.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: majd		</title>
		<link>https://www.practicalnetworking.net/stand-alone/ethernet-wiring/#comment-255315</link>

		<dc:creator><![CDATA[majd]]></dc:creator>
		<pubDate>Mon, 25 Aug 2025 14:58:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=449#comment-255315</guid>

					<description><![CDATA[went to the comment section to say thank you and found out that the writer is none other than amazing Ed Harmoush.
Thank you very much]]></description>
			<content:encoded><![CDATA[<p>went to the comment section to say thank you and found out that the writer is none other than amazing Ed Harmoush.<br />
Thank you very much</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jan		</title>
		<link>https://www.practicalnetworking.net/stand-alone/ethernet-wiring/#comment-254973</link>

		<dc:creator><![CDATA[Jan]]></dc:creator>
		<pubDate>Wed, 09 Apr 2025 10:28:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=449#comment-254973</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.practicalnetworking.net/stand-alone/ethernet-wiring/#comment-60080&quot;&gt;Ed Harmoush&lt;/a&gt;.

&lt;p&gt;I think you might have confused 1000BASE-T and 1000BASE-TX.&lt;/p&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;&lt;p&gt;All four pairs in 1000BASE-T are full-duplex, eliminating the need for auto MDI/MDI-X functionality. See&#160;IEEE 802.3-2012 40.8.2 Crossover Function. And the PMA will provide identification of each pair. See IEEE 802.3-2012 40.1.4 Signaling.&lt;/p&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;&lt;p&gt;1000BASE-TX still uses 2 pairs for TX and 2 pairs for RX, so we still need auto MDI/MDI-X to match TX/RX.&lt;/p&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.practicalnetworking.net/stand-alone/ethernet-wiring/#comment-60080">Ed Harmoush</a>.</p>
<p>I think you might have confused 1000BASE-T and 1000BASE-TX.</p>
<p></p>
<p>All four pairs in 1000BASE-T are full-duplex, eliminating the need for auto MDI/MDI-X functionality. See&nbsp;IEEE 802.3-2012 40.8.2 Crossover Function. And the PMA will provide identification of each pair. See IEEE 802.3-2012 40.1.4 Signaling.</p>
<p></p>
<p>1000BASE-TX still uses 2 pairs for TX and 2 pairs for RX, so we still need auto MDI/MDI-X to match TX/RX.</p>
<p></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jan		</title>
		<link>https://www.practicalnetworking.net/stand-alone/ethernet-wiring/#comment-254972</link>

		<dc:creator><![CDATA[Jan]]></dc:creator>
		<pubDate>Wed, 09 Apr 2025 09:52:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=449#comment-254972</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.practicalnetworking.net/stand-alone/ethernet-wiring/#comment-254099&quot;&gt;Ninel&lt;/a&gt;.

&lt;p&gt;&lt;span&gt;Because Ethernet uses differential signals to transmit data, this means that the data is identified by the voltage difference between Pin1 and Pin2, Pin3 and Pin6. &lt;/span&gt;&lt;/p&gt;&lt;p&gt;We will map the voltage difference to the symbol of Ethernet transmission, such as using +1V to represent 0 and -1V to represent 1. &lt;/p&gt;&lt;p&gt;So when PoE is not used, we may load +0.5V on Pin1 and -0.5V on Pin2, and calculate the voltage difference Pin1 - Pin2 = 1V to get data 0, one bit.&lt;/p&gt;&lt;p&gt;When PoE is used, we load +24.5V on Pin1 and +23.5V on Pin2, and calculate the voltage difference Pin1 - Pin2 is still 1V, and data can still be transmitted normally. But at the same time, we will change the voltage of Pin3 and Pin6 from +0.5V and -0.5V, which originally represent data 0, to -23.5V and -24.5V, so that in the circuit formed by Pin 1 and Pin3 [+24.5 - (-23.5) = 48 V], we can get a voltage of 48V, and the same is true for Pin2 and Pin6.&lt;/p&gt;]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.practicalnetworking.net/stand-alone/ethernet-wiring/#comment-254099">Ninel</a>.</p>
<p><span>Because Ethernet uses differential signals to transmit data, this means that the data is identified by the voltage difference between Pin1 and Pin2, Pin3 and Pin6. </span></p>
<p>We will map the voltage difference to the symbol of Ethernet transmission, such as using +1V to represent 0 and -1V to represent 1. </p>
<p>So when PoE is not used, we may load +0.5V on Pin1 and -0.5V on Pin2, and calculate the voltage difference Pin1 &#8211; Pin2 = 1V to get data 0, one bit.</p>
<p>When PoE is used, we load +24.5V on Pin1 and +23.5V on Pin2, and calculate the voltage difference Pin1 &#8211; Pin2 is still 1V, and data can still be transmitted normally. But at the same time, we will change the voltage of Pin3 and Pin6 from +0.5V and -0.5V, which originally represent data 0, to -23.5V and -24.5V, so that in the circuit formed by Pin 1 and Pin3 [+24.5 &#8211; (-23.5) = 48 V], we can get a voltage of 48V, and the same is true for Pin2 and Pin6.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Michael Wilcock		</title>
		<link>https://www.practicalnetworking.net/stand-alone/ethernet-wiring/#comment-254762</link>

		<dc:creator><![CDATA[Michael Wilcock]]></dc:creator>
		<pubDate>Sat, 04 Jan 2025 15:54:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=449#comment-254762</guid>

					<description><![CDATA[This was beautifully constructed and unlocked a lot of understanding for me. Thanks for your thorough work to write and publish this.]]></description>
			<content:encoded><![CDATA[<p>This was beautifully constructed and unlocked a lot of understanding for me. Thanks for your thorough work to write and publish this.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Pablo		</title>
		<link>https://www.practicalnetworking.net/stand-alone/ethernet-wiring/#comment-254682</link>

		<dc:creator><![CDATA[Pablo]]></dc:creator>
		<pubDate>Tue, 15 Oct 2024 20:52:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.practicalnetworking.net/?p=449#comment-254682</guid>

					<description><![CDATA[Awesome. Many thanks for the time you have spent here]]></description>
			<content:encoded><![CDATA[<p>Awesome. Many thanks for the time you have spent here</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
