<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>The OSI Model, Layer by Layer on Aperture Zone</title>
    <link>https://aperturezone.com/osi/</link>
    <description>Recent content in The OSI Model, Layer by Layer on Aperture Zone</description>
    <image>
      <url>https://aperturezone.com/logo.webp</url>
      <link>https://aperturezone.com/logo.webp</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>fr-fr</language>
    <lastBuildDate>Sat, 18 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/osi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>RJ45: The Complete Guide — Standards, Cable Categories, Connectors, and Tools</title>
      <link>https://aperturezone.com/osi/rj45/</link>
      <pubDate>Sun, 12 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/osi/rj45/</guid>
      <description>&lt;p&gt;This article is in response to a request from &lt;strong&gt;@Menvé&lt;/strong&gt;, a site member and cybersecurity instructor: his students were looking for a clear and comprehensive guide on
the RJ45. Because we often forget—especially when we’re just starting out in cybersecurity—but it all starts here: the &lt;strong&gt;physical layer&lt;/strong&gt; is the
foundation on which everything else rests. It’s hard to make sense of segmentation, VLANs, or 802.1X without knowing what’s actually traveling through the cables.
For segmentation and VLANs, you can also check out the excellent article by @SilenShttps://aperturezone.fr/posts/cisco-firewall-final/&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>MAC Addresses: The Complete Guide — Layer 2, CAM Table, ARP, and Security</title>
      <link>https://aperturezone.com/osi/adresses-mac/</link>
      <pubDate>Thu, 16 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/osi/adresses-mac/</guid>
      <description>&lt;p&gt;This article builds on the &lt;a href=&#34;https://aperturezone.com/osi/rj45/&#34;&gt;RJ45 guide&lt;/a&gt;. That guide covered copper, twisted-pair cables, and crimping—the &lt;strong&gt;physical layer&lt;/strong&gt;. Here, we’re moving up a level—just one, but the one everyone skips. Between the cable and the IP address, there’s an entire layer that most people pass through without even noticing it: &lt;strong&gt;Layer 2&lt;/strong&gt;, the layer of MAC addresses.&lt;/p&gt;
&lt;p&gt;And that’s a shame, because that’s where a good half of everyday network incidents are resolved, and where attacks that haven’t aged a bit in thirty years play out.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Layer 3: IP, Addressing, and Routing — The Complete Guide</title>
      <link>https://aperturezone.com/osi/ip/</link>
      <pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/osi/ip/</guid>
      <description>&lt;p&gt;Third layer. We covered the &lt;a href=&#34;https://aperturezone.com/osi/rj45/&#34;&gt;cable&lt;/a&gt; — Layer 1. We covered &lt;a href=&#34;https://aperturezone.com/osi/mac-addresses/&#34;&gt;MAC addresses and Layer 2&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Layer 2 has a structural limitation, and it’s brutal: &lt;strong&gt;it doesn’t scale&lt;/strong&gt;. To find someone, it shouts down the hallway (broadcast). It works with thirty. With three billion, it’s a joke. And MAC addresses are &lt;strong&gt;flat&lt;/strong&gt;: &lt;code&gt;00:1A:2B:3C:4D:5E&lt;/code&gt; says nothing about where the machine is located. No structure, no hierarchy, nothing to aggregate. A global router would have to know every network card on the planet, one by one.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Layer 4: TCP, UDP, and Ports — The Complete Guide</title>
      <link>https://aperturezone.com/osi/tcp/</link>
      <pubDate>Fri, 31 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/osi/tcp/</guid>
      <description>&lt;p&gt;Fourth floor, and a change of pace. So far, everything we&#39;ve built—the &lt;a href=&#34;https://aperturezone.fr/posts/rj45/&#34;&gt;cable&lt;/a&gt;, &lt;a href=&#34;https://aperturezone.fr/posts/adresses-mac/&#34;&gt;MAC addresses&lt;/a&gt;, &lt;a href=&#34;https://aperturezone.fr/posts/couche3-ip-routage/&#34;&gt;IP and routing&lt;/a&gt;—share a common premise, the one on which the previous article ended: &lt;strong&gt;the network makes no promises&lt;/strong&gt;. An IP packet can be lost, duplicated, or arrive out of order. IP does its best and washes its hands of the rest.&lt;/p&gt;
&lt;p&gt;Yet your 4 GB file arrives intact. Your web page displays in the correct order. Your &lt;code&gt;apt upgrade&lt;/code&gt; never downloads a half-corrupted package without noticing it.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Layers 5 and 6: The Phantom Layers</title>
      <link>https://aperturezone.com/osi/5-6/</link>
      <pubDate>Sun, 02 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/osi/5-6/</guid>
      <description>&lt;p&gt;Fifth and sixth layers. After the &lt;a href=&#34;https://aperturezone.com/osi/rj45/&#34;&gt;cable&lt;/a&gt;, the &lt;a href=&#34;https://aperturezone.com/osi/mac-addresses/&#34;&gt;MAC addresses&lt;/a&gt;, the &lt;a href=&#34;https://aperturezone.com/osi/IP/&#34;&gt;IP&lt;/a&gt;, and &lt;a href=&#34;https://aperturezone.com/osi/TCP/&#34;&gt;TCP&lt;/a&gt;, logically, we should be talking about the session layer, followed by the presentation layer.&lt;/p&gt;
&lt;p&gt;Except that we have to be honest: &lt;strong&gt;these two layers are practically nonexistent.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Not in the sense that they’re useless—but in the sense that, in the network you manage every day, &lt;strong&gt;no one implements them as such&lt;/strong&gt;. There is no “Layer 6 protocol” the way there is a Layer 3 (IP) or Layer 4 (TCP). These are two layers that the OSI model envisaged, that theory describes in detail, and that reality has simply absorbed elsewhere.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Layer 7: The Application — HTTP, DNS, DHCP, and the Top of the Stack</title>
      <link>https://aperturezone.com/osi/application/</link>
      <pubDate>Tue, 04 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/osi/application/</guid>
      <description>&lt;p&gt;Seventh and final layer. We started with the &lt;a href=&#34;https://aperturezone.com/osi/rj45/&#34;&gt;cable&lt;/a&gt;, we went through &lt;a href=&#34;https://aperturezone.com/osi/mac-addresses/&#34;&gt;MAC addresses&lt;/a&gt;, &lt;a href=&#34;https://aperturezone.com/osi/IP/&#34;&gt;IP and routing&lt;/a&gt;, &lt;a href=&#34;https://aperturezone.com/osi/TCP/&#34;&gt;TCP and ports&lt;/a&gt;, and we found that &lt;a href=&#34;https://aperturezone.com/osi/layers-5-6-ghosts/&#34;&gt;layers 5 and 6 were phantom layers&lt;/a&gt;. Here we are at the top.&lt;/p&gt;
&lt;p&gt;And the top is where everyone lives. Layer 7 is what you see: the browser loading a page, an email being sent, a domain name being resolved, the machine receiving its IP address at startup. This is the &lt;strong&gt;application&lt;/strong&gt; layer—the only one the user interacts with directly, and by far the richest in protocols.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
