<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>PHY on Prepakis Georgios | Kernelstub | Security Researcher</title><link>https://blog.kernelstub.dev/tags/phy/</link><description>Recent content in PHY on Prepakis Georgios | Kernelstub | Security Researcher</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 07 Nov 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.kernelstub.dev/tags/phy/index.xml" rel="self" type="application/rss+xml"/><item><title>Decoding Auto Negotiation and Duplex Mismatch at the PHY Layer</title><link>https://blog.kernelstub.dev/posts/decoding-auto-negotiation-and-duplex-mismatch-at-the-phy-layer/</link><pubDate>Fri, 07 Nov 2025 00:00:00 +0000</pubDate><guid>https://blog.kernelstub.dev/posts/decoding-auto-negotiation-and-duplex-mismatch-at-the-phy-layer/</guid><description>&lt;h2 id="understanding-the-physical-layer-phy"&gt;Understanding the Physical Layer (PHY)&lt;/h2&gt;
&lt;p&gt;If you&amp;rsquo;ve ever chased down a &amp;ldquo;the network is slow but only sometimes and only in one direction&amp;rdquo; ticket, there&amp;rsquo;s a good chance the real culprit was sitting quietly at Layer 1, way below anything a &lt;code&gt;ping&lt;/code&gt; or &lt;code&gt;traceroute&lt;/code&gt; will show you. That&amp;rsquo;s the world of the PHY chip, the piece of silicon on every Ethernet interface that actually puts bits onto the wire and pulls them back off again.&lt;/p&gt;</description></item></channel></rss>