<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: TAKUMI SUGATA</title>
    <description>The latest articles on DEV Community by TAKUMI SUGATA (@taqq).</description>
    <link>https://dev.to/taqq</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3893113%2F337933c5-31af-4a18-bc73-b34ee78241dc.jpg</url>
      <title>DEV Community: TAKUMI SUGATA</title>
      <link>https://dev.to/taqq</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/taqq"/>
    <language>en</language>
    <item>
      <title>Measure? Select? - Understanding the difference between Network metrics and Routing metrics</title>
      <dc:creator>TAKUMI SUGATA</dc:creator>
      <pubDate>Tue, 12 May 2026 23:40:37 +0000</pubDate>
      <link>https://dev.to/taqq/measure-select-understanding-the-difference-between-network-metrics-and-routing-metrics-3ao0</link>
      <guid>https://dev.to/taqq/measure-select-understanding-the-difference-between-network-metrics-and-routing-metrics-3ao0</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;While studying for CompTIA Network+, I totally couldn't understand a difference between Network Metrics and Routing Metrics. Both terms have "Metrics", which confused me. &lt;br&gt;
Once I understood why each one existed, everything fell into place. So I decided to write it down.&lt;/p&gt;


&lt;h2&gt;
  
  
  Difference between two Metrics
&lt;/h2&gt;

&lt;p&gt;As a premise, two Metrics are used for different purposes.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Network Metrics：
　→ Indicator for measuring performance of network
　→ System managers use it for surveillance or troubleshooting

Routing Metrics：
　→ Value for selecting the best path
　→ Routers use it automatically
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Network Metrics
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Indicator for measuring performance of network&lt;/strong&gt;&lt;br&gt;
In a CompTIA Network+, 4 metrics are particularly important.&lt;/p&gt;


&lt;h3&gt;
  
  
  1. Bandwidth
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Keyword：Width of road
Meaning：Maximum amout of data that can be sent at one time
Unit：bps・Mbps・Gbps
Good condition：Higher is better
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Wide road → It enables many vehicles to drive at the same time
Large Bandwidth → It enebles large amounts of data to be sent at once
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  2. Latency
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Keyword：Period of time signal reaches
Meaning：the time it takes for data to travel from sender to receiver
Unit：ms（milliseconds）
Good condition：Lower is better (Under 20ms is preferable)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Example：
Online video games → 1ms（5G）
4G communication → 30〜50ms
Connection to servers overseas → over 100ms
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  3. Jitter
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Keyword：Variation in delay
Meaning：Latency becomes inconsistent rather than remaining constant
Unit：ms
Good condition：Lower is better
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Latency is stable（Low Jitter）：
　→ 10ms・10ms・10ms・10ms

Latency is unstable（High Jitter）：
　→ 10ms・50ms・5ms・80ms
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;In case of high Jitter：
・Video call and online video game are lagged
・Quality of voice through VoIP become worse
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  4. Packet Loss
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Keyword：Data loss
Meaning：Portion shows that data don't reach to the destination 
Unit：%
Good condition：Lower is better (0% is preferable)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Calculation for Packet Loss
In case that 95 packets are reached even if 100 packets are served：
　→ Packet Loss = 5%
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;In case of high Packet Loss：
・Delay to load Web pages
・Disturb video call
・Fail to download files
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Summary table
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metrics&lt;/th&gt;
&lt;th&gt;Meaning&lt;/th&gt;
&lt;th&gt;Unit&lt;/th&gt;
&lt;th&gt;Good condition&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Bandwidth&lt;/td&gt;
&lt;td&gt;Maximum amount of data transfer&lt;/td&gt;
&lt;td&gt;Mbps・Gbps&lt;/td&gt;
&lt;td&gt;Higher is better&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Latency&lt;/td&gt;
&lt;td&gt;Delay time for signal&lt;/td&gt;
&lt;td&gt;ms&lt;/td&gt;
&lt;td&gt;Lower is better&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Jitter&lt;/td&gt;
&lt;td&gt;Variation in travel time&lt;/td&gt;
&lt;td&gt;ms&lt;/td&gt;
&lt;td&gt;Lower is better&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Packet Loss&lt;/td&gt;
&lt;td&gt;Data loss&lt;/td&gt;
&lt;td&gt;%&lt;/td&gt;
&lt;td&gt;Lower is better&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;
&lt;h3&gt;
  
  
  Understanding with highway
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Bandwidth   = Width of road（The number of lanes）
Latency     = Arrival time
Jitter      =Bariation of required time
Packet Loss = The proportion for car going missing on the way
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Relationships between each metric
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Even if bandwidth is bigger, it makes you feel slow due to high latency
Even if latency is lower, call will be low quality due to high jitter
Even if above all is good condition, it makes you feel slow for resending due to high packet loss
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Routing Metrics
&lt;/h2&gt;

&lt;p&gt;** It is a value used by routing protocol to prioritize available routes. It works as cost or score for specific route. **&lt;/p&gt;

&lt;p&gt;In a nutshell, ** score for network route**.&lt;/p&gt;
&lt;h3&gt;
  
  
  Why is it needed
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Problem：
When multiple routes exists to the same destination, it becomes difficult to determine which one is optimal.

Solution：
Attach value (metric) on each route
　→ Give priority to the route having lower value
　→ Router can select the best route automatically
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Meaning of cost and score
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;cost：
　→ Lower is better
　→ Image of the cost for going through the way

score：
　→ Evaluation value
　→ It changes whether higher or lower is better depending on context
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;In CompTIA Network+ exam, it is enough to remember *&lt;em&gt;cost ( lower is better) *&lt;/em&gt;.&lt;/p&gt;
&lt;h3&gt;
  
  
  Practical image
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;In case that there are three routes to the destination：
Route A：Metric = 10  ← Lowest value = Top priority
Route B：Metric = 50
Route C：Metric = 100 ← Highest value = Bottom priority

Router selects Route A which has the lowest metric value
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Understanding with a car navigation
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Route A：Highway（The distance is long but fast）→ cost 10
Route B：Public road（The distance is short but slow）  → cost 50
Route C：Mountain path（The distance is long and slow）  → cost 100

A car navigation ( Router ) select Route A which has the lowest cost
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Kinds of routing metrics
&lt;/h3&gt;

&lt;p&gt;Used value differs from each protocols.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metrics&lt;/th&gt;
&lt;th&gt;Meaning&lt;/th&gt;
&lt;th&gt;Used protocol&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Hop Count&lt;/td&gt;
&lt;td&gt;The number of router that it go through&lt;/td&gt;
&lt;td&gt;RIP&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Bandwidth&lt;/td&gt;
&lt;td&gt;Maximum speed on the route&lt;/td&gt;
&lt;td&gt;OSPF&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Latency&lt;/td&gt;
&lt;td&gt;Delay time for overall route&lt;/td&gt;
&lt;td&gt;EIGRP&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cost&lt;/td&gt;
&lt;td&gt;Weigh set up by system managers&lt;/td&gt;
&lt;td&gt;OSPF&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;


&lt;h2&gt;
  
  
  Organize two metrics table
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Item&lt;/th&gt;
&lt;th&gt;Network Metrics&lt;/th&gt;
&lt;th&gt;Routing Metrics&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Purpose&lt;/td&gt;
&lt;td&gt;Measure the performance&lt;/td&gt;
&lt;td&gt;Select routes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Use case&lt;/td&gt;
&lt;td&gt;Monitoring・Troubleshooting&lt;/td&gt;
&lt;td&gt;Route selection by Router&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Representative indicator&lt;/td&gt;
&lt;td&gt;Bandwidth・Latency・Jitter・Packet Loss&lt;/td&gt;
&lt;td&gt;Hop Count・Cost・Bandwidth・Latency&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;User&lt;/td&gt;
&lt;td&gt;Network administrator&lt;/td&gt;
&lt;td&gt;Router（auto）&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;


&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Firstly, I couldn't distinguish the difference between each metric.&lt;br&gt;
Once I understood the difference, the purpose behind each metric became clear.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Network Metrics  = Measure performance
Routing Metrics  = Select route
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



</description>
      <category>network</category>
      <category>beginners</category>
    </item>
    <item>
      <title>SSID vs ESSID — One Is a Name, the Other Is a Mechanism</title>
      <dc:creator>TAKUMI SUGATA</dc:creator>
      <pubDate>Sun, 10 May 2026 08:34:17 +0000</pubDate>
      <link>https://dev.to/taqq/ssid-vs-essid-one-is-a-name-the-other-is-a-mechanism-55ge</link>
      <guid>https://dev.to/taqq/ssid-vs-essid-one-is-a-name-the-other-is-a-mechanism-55ge</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;While studying for CompTIA Network+, I totally couldn't understand SSID and ESSID. &lt;br&gt;
I could remember " SSID is the name of Wi-Fi ", but I couldn't grasp how it is different. &lt;br&gt;
Once I learned about the structures, everything fell into place, so I decided to write it down.&lt;/p&gt;


&lt;h2&gt;
  
  
  What is SSID
&lt;/h2&gt;

&lt;p&gt;SSID stands for &lt;strong&gt;Service Set Identifier&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;The name displayed on the smartphone for Wi-Fi settings like "○○-Wi-Fi","Coffee_Shop_Free"
　→All of these names are SSID
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Why SSID is needed
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Problem：
Radio waves are invisible to the human eye, so we have no way of knowing which Wi-Fi network to connect to.

Solution：
Name each Wi-Fi
　→ Users can identify and choose the network they want to connect to
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Familiar example
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Wi-Fi router at home
　→ The name of "My_Home_Wi-Fi"
　→ This is SSID

We can use Wi-Fi inside a range that a router reach 
The signal weakens as we move further away
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Configuration diagram
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Smartphone
　↓ Connect to "My_Home_Wi-Fi"
Access point (One unit)
　↓
Internet
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  What is ESSID
&lt;/h2&gt;

&lt;p&gt;ESSID stands for &lt;strong&gt;Extended Service Set Identifier&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;In a nutshell, it is a mechanism that allows multiple access points to share the same name, enabling seamless connectivity. &lt;/p&gt;

&lt;p&gt;&lt;code&gt;E&lt;/code&gt; means &lt;strong&gt;Extended&lt;/strong&gt;&lt;br&gt;
This is an extended concept that expands SSID across multiple access points&lt;/p&gt;
&lt;h3&gt;
  
  
  Why ESSID is needed
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Problem：
Single access point cannot cover wide range area 

Example： University campus・ Airport・ Large commercial facility
　→ Each building requires its own access point to provide adequate coverage
　→ Each time we move to other building, we have to re-connect to the Wi-Fi

Solution：
Multiple access points share the same name
　→ Wherever we move, our devices can connect to it automatically
　→ We don't have to re-connect to the Wi-Fi
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Practical example
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Overall university campus
　→ Building A, B, and C have several access points
　→ All access points have the same name of "University_Wi-Fi" 
　→ This is ESSID

Wherever we move, our devices keep connecting to the same Wi-Fi name
→ Need not re-connect
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Configuration diagram
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;　　　Smartphone（ Using while moving ）
　　　　　　　　　↓
┌──────────────────────────────────────────────┐
│  "University_Wi-Fi"（ESSID）                 │
│  ┌───────────┐ ┌───────────┐  ┌───────────┐  │
│  │ AP-1　    │ │ AP-2      │  │ AP-3      │  │
│  │ Building A│ │ Building B│  │ Building C│  │
│  └───────────┘ └───────────┘  └───────────┘  │
└──────────────────────────────────────────────┘
　　　　　　　　　↓
　　　 　　   Internet 

Even if we connect our devices to any access point, we can use it as a same network
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  The difference between SSID and ESSID
&lt;/h2&gt;

&lt;p&gt;This is the most confused point&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;SSID：
　→ The name itself
　→ Identifier named for the single access point
　→ Only valid for that single access point

ESSID：
　→ The name + the concept for integration
　→ The mechanism multiple access points share the same name 
　→ Works through the coordination of multiple access points behind the scenes
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Understanding with convenience store
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;SSID：" Seven-Eleven ○○store"
　→ The unique name
　→ The name cannot use the other store for identification

ESSID：" Seven-Eleven" as a a brand name
　→ Every store offers the same service and products
　→ Each store ( access point ) integrate each other on the backend
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Summary table
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Item&lt;/th&gt;
&lt;th&gt;SSID&lt;/th&gt;
&lt;th&gt;ESSID&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Official name&lt;/td&gt;
&lt;td&gt;Service Set Identifier&lt;/td&gt;
&lt;td&gt;Extended Service Set Identifier&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Meaning&lt;/td&gt;
&lt;td&gt;The name of a Wi-Fi network&lt;/td&gt;
&lt;td&gt;A mechanism where multiple access points share the same name&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Scope&lt;/td&gt;
&lt;td&gt;Single access point&lt;/td&gt;
&lt;td&gt;Multiple access points&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Use&lt;/td&gt;
&lt;td&gt;House ・Small scale&lt;/td&gt;
&lt;td&gt;Office・ University・ Large scale facility&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Reconnection&lt;/td&gt;
&lt;td&gt;Every time we move to the other area&lt;/td&gt;
&lt;td&gt;No need&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h2&gt;
  
  
  Supplement in the modern era
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Actual fact：
SSID  → Identifier for single access point
ESSID → Identifier bundled by multiple access points 

In the modern era：
In practice, SSID and ESSID are used interchangeably, as Wi-Fi settings typically display both simply as "SSID"
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For the CompTIA Network+ exam, it is sufficient to understand ESSID as an extended concept that unifies multiple access points under a single network name.&lt;/p&gt;




&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;I couldn't understand the difference between SSID and ESSID.&lt;br&gt;
Once I understood why we don't need to reconnect every time we move around an airport or university campus, everything clicked. &lt;/p&gt;

</description>
      <category>network</category>
      <category>comptia</category>
      <category>wifi</category>
      <category>essid</category>
    </item>
    <item>
      <title>Four network protocols (LACP, LLDP, L2TP, and LDAP) that are hard to memorize</title>
      <dc:creator>TAKUMI SUGATA</dc:creator>
      <pubDate>Sat, 09 May 2026 02:59:26 +0000</pubDate>
      <link>https://dev.to/taqq/four-network-protocols-lacp-lldp-l2tp-and-ldap-that-are-hard-to-memorize-i1j</link>
      <guid>https://dev.to/taqq/four-network-protocols-lacp-lldp-l2tp-and-ldap-that-are-hard-to-memorize-i1j</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;While studying for CompTIA Network+, many network protocols made me messed up.&lt;br&gt;
It confused me a lot because of the similar names such as LACP, LLDP, L2TP, and LDAP.&lt;br&gt;
I didn't understand each name and how they act in network. &lt;br&gt;
Once I understood why each one existed, everything fell into place. So, I decided to write it down.&lt;/p&gt;


&lt;h2&gt;
  
  
  Overview table
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Protocol&lt;/th&gt;
&lt;th&gt;Purpose&lt;/th&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;Similar example&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;LACP&lt;/td&gt;
&lt;td&gt;Bundle cables&lt;/td&gt;
&lt;td&gt;Layer 2&lt;/td&gt;
&lt;td&gt;1 Lane→4 Lanes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;LLDP&lt;/td&gt;
&lt;td&gt;Discover adjacent devices&lt;/td&gt;
&lt;td&gt;Layer 2&lt;/td&gt;
&lt;td&gt;Greet neighbor&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;L2TP&lt;/td&gt;
&lt;td&gt;Create VPN tunnel&lt;/td&gt;
&lt;td&gt;Layer 2&lt;/td&gt;
&lt;td&gt;Sending a letter in an envelop&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;LDAP&lt;/td&gt;
&lt;td&gt;Manage user authentication&lt;/td&gt;
&lt;td&gt;Layer 7&lt;/td&gt;
&lt;td&gt;One staff ID card opens all doors&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;


&lt;h2&gt;
  
  
  LACP ( Link Aggregation Control Protocol )
&lt;/h2&gt;
&lt;h3&gt;
  
  
  Understanding in a nutshell
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;This protocol is a mechanism that bundles multiple cables into a single logical link.&lt;/strong&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  Why it is needed
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Problem：
Only one cable limits the speed (Maximum 1 Gbps) 
The connection will be stopped, if it breaks down.

Solution：
Bundle multiple cables
　→ Accelerate the speed
　→ Continue to connect, if a cable breaks down.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Familiar example
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;One lane road （A normal cable）
　→ Cause traffic jam, which slow the speed down
　→ Impossible to function by accident or construction work

Four lane roads（ Bundle four cables by LACP）
　→ Avoid the cause of congestion
　→ Possible to function by accident or construction work due to the presence of other lanes
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Specific structure
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Normal：
Switch ──── 1Gbps ──── Server
　　　　   　　↑
　 　   Only one cable

LACP：
　　　　　　　┌── 1Gbps ──┐
Switch ──────┼── 1Gbps ──┼───── Server
　　　　 　　 ├── 1Gbps ──┤
　　　　　　　└── 1Gbps ──┘
　　Total 4Gbps（Logically one cable)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  2 main pros
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;1. Expand bandwidth
　→ Logically four times as fast as only one cable, if four cables are bundled.

2. Ensure redundancy
　→ The remaining cables enable maintain the connection even if one cable fails.
　→ Endure technical issues
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  LLDP ( Link Layer Discovery Protocol )
&lt;/h2&gt;
&lt;h3&gt;
  
  
  Understanding in a nutshell
&lt;/h3&gt;

&lt;p&gt;** This protocol automatically discovers information about neighboring devices.**&lt;/p&gt;
&lt;h3&gt;
  
  
  Why it is needed
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Problem：
In a large scale network, it is hard to grasp that where devices are connected

Solution：
Devices automatically tell adjacent devices the own information each other 
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Familiar example
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;When you move home
　→ You don't find the people who live next door
　→ Greeting makes you understand who he or she is

Without LLDP
　→ Manager have to confirm each device by hand 

With LLDP
　→ Each device automatically tell their information each other
　→ Managers can understand the entire network structure without leaving their desk 
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Information it can collect
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;・Name of the device
・Kind of the device ( Switch, Router etc. )
・Port number
・IP address
・Manufacturer
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Use case
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Troubleshooting：
　→ Instant check "Which device is connected to this port"

Network management：
　→ Connect to the tool that automatically create configuration diagram

Replace device：
　→ New device automatically introduces itself to adjacent devices 
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  L2TP ( Layer 2 Tunneling Protocol )
&lt;/h2&gt;
&lt;h3&gt;
  
  
  Understanding in a nutshell
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;This protocol creates a virtual tunnel over the Internet to enable secure communication&lt;/strong&gt; &lt;/p&gt;
&lt;h3&gt;
  
  
  Why it is needed
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Problem：
Possible to leak important information to the Internet

Solution：
Create virtual tunnel and send data within the tunnel 
　→ Disabled to see the data from outside
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Familiar example
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Normal internet connection：
　→ Send with a postcard
　→ Anyone can read the content

L2TP tunnel：
　→ Send with an envelop
　→ No one can read the content
　→ Reach to the destination securely
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Specific structure
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Home PC
　↓
Internet（ Public line ）
　↓ L2TP tunnel（ Virtual dedicated line）
Office network

See from outside：
　→ Cannot see inside data
　→ Just like working at the office
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Combination with IPsec
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Only L2TP：
　→ Just create tunnel
　→ Without encryption

L2TP/IPsec：
　→ Tunnel + Encryption
　→ More secure VPN connection
　→ In practice, they are almost always used together
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  LDAP ( Lightweight Directory Access Protocol )
&lt;/h2&gt;
&lt;h3&gt;
  
  
  Understanding in a nutshell
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;This protocol is a mechanism that centrally manage user information and use them for authentication&lt;/strong&gt; &lt;/p&gt;
&lt;h3&gt;
  
  
  Why it is needed
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Problem：
A lot of login information are needed if there are many system
　→ Hard to manage multiple passwords

Solution：
Collect user information in one place and manage it centrally
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Familiar example
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Without LDAP：
　→ Separately manage several information such as Admission badge, PC password, mail password, system password
　→ Both managers and users are hard to manage them

With LDAP：
　→ Only one ID and password enables users to login all systems
　→ Admission badge makes us possible unlock all doors 
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Specific structure
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;PC（ Require login）
　↓
LDAP server（ Active Directory etc.）
　↓ " Has this user already been registered?"
　↓ " Has this user had which role?"
　↓
Authentication succeed → User can access the system
Authentication failed → User cannot access the system
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  What is Directory
&lt;/h3&gt;

&lt;p&gt;Directory in LDAP is like address list for user information&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Registered information：
・Name
・Mail address
・Department
・Password（ Hashed ）
・Role（ Common user or manager ）
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Relationship with Active Directory
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;LDAP ：A protocol（ a set of communication rules ）
Active Directory： A Microsoft product that uses LDAP internally
LDAP is one of network protocols that Active Directory uses
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Organize 4 protocols difference
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;LACP： Enhance physical connection
　→ Speed up and enforce redundancy by bundling cables

LLDP： Automatically identify network topology
　→ Automatically research what the adjacent device is

L2TP：Securely connect with remote area
　→ Create virtual tunnel in the Internet

LDAP： Manage users
　→ Centrally manage user authentication
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Relationship with OSI reference model
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Layer 7  Application  ← Where LDAP operates
Layer 6  Presentation │
Layer 5  Session      │
Layer 4  Transport    │
Layer 3  Network      │
─────────────────────────────
Layer 2  Data Link    ← Where LACP・LLDP・L2TP operate
Layer 1  Physical     │
─────────────────────────────
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Summary ( repost )
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Protocol&lt;/th&gt;
&lt;th&gt;Purpose&lt;/th&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;Similar example&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;LACP&lt;/td&gt;
&lt;td&gt;Bundle cables&lt;/td&gt;
&lt;td&gt;Layer 2&lt;/td&gt;
&lt;td&gt;1 Lane→4 Lanes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;LLDP&lt;/td&gt;
&lt;td&gt;Discover adjacent devices&lt;/td&gt;
&lt;td&gt;Layer 2&lt;/td&gt;
&lt;td&gt;Greet neighbor&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;L2TP&lt;/td&gt;
&lt;td&gt;Create VPN tunnel&lt;/td&gt;
&lt;td&gt;Layer 2&lt;/td&gt;
&lt;td&gt;Sent letter in an envelop&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;LDAP&lt;/td&gt;
&lt;td&gt;Management user authentication&lt;/td&gt;
&lt;td&gt;Layer 7&lt;/td&gt;
&lt;td&gt;Open all doors with an staff identity card&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;In this article, I covered four protocols that are easy to confuse due to their similar names. Once I understood the purpose behind each one, everything clicked. I hope this helps anyone else who is struggling with the same confusion.&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>learning</category>
      <category>networking</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>I Finally Understood Routers and Switches by Connecting Them to Real-Life Examples</title>
      <dc:creator>TAKUMI SUGATA</dc:creator>
      <pubDate>Thu, 07 May 2026 23:11:41 +0000</pubDate>
      <link>https://dev.to/taqq/i-finally-understood-routers-and-switches-by-connecting-them-to-real-life-examples-47d8</link>
      <guid>https://dev.to/taqq/i-finally-understood-routers-and-switches-by-connecting-them-to-real-life-examples-47d8</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;While studying for CompTIA Network+, I couldn't totally grasp the difference between routers and switches. Even when I memorized their functions, the knowledge never stuck. However, once I knew the reason why they are needed, everything clicked. So, I decided to write it down. &lt;/p&gt;




&lt;h2&gt;
  
  
  Understand the difference between routers and switches
&lt;/h2&gt;

&lt;p&gt;Comparing these two devices side by side makes it much easier to understand.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Switch：
　→ Transfer data inside the same network
　→ Use MAC address
　→ Layer 2（Data Link Layer）

Router：
　→ Transfer data in different networks
　→ Use IP Address
　→ Layer 3（Network Layer）
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Familiar example
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Switch = extension call in the office
　→ Connect with people from the same company

Router = international telephone exchange
　→ Connects people from different countries (networks)
　→ Determines which route to use

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Division of roles of routers and switches
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;　　　　　　        Internet
　　　　　　　　  　    │
　　　　　┌────────────┴──────────┐
　　　　　│      Router           │ ← Layer 3
　　　　　│ Different NW Transfer │ Judge from IP address
　　　　　└────────────┬──────────┘
　　　　　　　　      　│
　　　　　┌────────────┴─────────────┐
　　　　　│            Switch         │ ← Layer 2
　　　　　│ The same NW Transfer      │ Judging from MAC address
　　　　　└───────┬──────────┬────────┘
　　　　　  　  　│　　　     │
　　　　  　   ┌──┴──┐   　┌──┴──┐
　　　　     　│PC-A │　   │PC-B │
　　　　  　   └─────┘　   └─────┘
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  The main role of routers
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Routing ( Route Selection )
&lt;/h3&gt;

&lt;p&gt;It decides routes that head to the destination.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Tokyo → Osaka：
  Route A： Tokyo → Nagoya → Osaka
　Route B： Tokyo → Kyoto → Osaka
　　↓
　Choose the best path for data transfer  
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  2. Network segmentation・ border
&lt;/h3&gt;

&lt;p&gt;The router acts as the boundary between the Internet and the internal network.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;   　　　　　　Internet
　　　　　　　　　│
　　　　　　　　　│ Global IP
　　　　　　　　　│ 203.0.113.1
　　　　　┌──────┴──────┐
　　　　　│   Router    │
　　　　　└──────┬──────┘
　　　　　　　　　│ Private IP
　　　　　　　　　│ 192.168.1.1
　　　　　┌──────┴──────┐
　　　　　│   Switch    │
　　　　　└──┬───────┬──┘
　　　　　 　│　　  　│
　　　　　┌──┴──┐ ┌──┴──┐
　　　　　│PC-A │ │PC-B │
　　　　　│~.1.2│ │~.1.3│
　　　　　└─────┘ └─────┘
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  3. NAT ( Network Address Translation)
&lt;/h3&gt;

&lt;p&gt;NAT is a mechanism that allows multiple devices to share a single global IP address.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;【NAT（ Sharing one IP address by multiple PCs）】

Internal Network (Office)        Internet
┌───────────────────┐            ┌───────────────┐
│ PC-A 192.168.1.2  │            │               │
│ PC-B 192.168.1.3  ├── Router ──┤  203.0.113.1  │
│ PC-C 192.168.1.4  │            │  （Just one） │
└───────────────────┘            └───────────────┘
Multiplex private IPs           　1 Global IP
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  4. Data flow
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;【PC-A → Data flow to the Internet】

PC-A（192.168.1.2）
　↓ " I need to send this to the Internet"
Switch
　↓ head to Router
Router
　↓ exchange to global IP（NAT）
　↓ select the best path
Internet
　↓
Destination server
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  5. Packet filtering
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
A basic security feature that blocks unauthorized access 
from outside the network.

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Routing Table
&lt;/h2&gt;

&lt;p&gt;Routers have maps called routing table.&lt;br&gt;
They look at it and select the path for destinations.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight csvs"&gt;&lt;code&gt;&lt;span class="k"&gt;Destination&lt;/span&gt; &lt;span class="k"&gt;network&lt;/span&gt;  &lt;span class="err"&gt;|&lt;/span&gt; &lt;span class="k"&gt;Next&lt;/span&gt; &lt;span class="k"&gt;router&lt;/span&gt;      &lt;span class="err"&gt;|&lt;/span&gt; &lt;span class="k"&gt;Distance&lt;/span&gt;
&lt;span class="mf"&gt;192.168.1.0&lt;/span&gt;&lt;span class="err"&gt;/&lt;/span&gt;&lt;span class="mf"&gt;24&lt;/span&gt;  &lt;span class="err"&gt;|&lt;/span&gt; &lt;span class="k"&gt;Direct&lt;/span&gt; &lt;span class="k"&gt;connection&lt;/span&gt;        &lt;span class="err"&gt;|&lt;/span&gt; &lt;span class="mf"&gt;0&lt;/span&gt;
&lt;span class="mf"&gt;10.0.0.0&lt;/span&gt;&lt;span class="err"&gt;/&lt;/span&gt;&lt;span class="mf"&gt;8&lt;/span&gt;      &lt;span class="err"&gt;|&lt;/span&gt; &lt;span class="mf"&gt;192.168.2.1&lt;/span&gt;     &lt;span class="err"&gt;|&lt;/span&gt; &lt;span class="mf"&gt;1&lt;/span&gt;
&lt;span class="mf"&gt;0.0.0.0&lt;/span&gt;&lt;span class="err"&gt;/&lt;/span&gt;&lt;span class="mf"&gt;0&lt;/span&gt;       &lt;span class="err"&gt;|&lt;/span&gt; &lt;span class="mf"&gt;203.0.113.1&lt;/span&gt;     &lt;span class="err"&gt;|&lt;/span&gt; &lt;span class="k"&gt;Default&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Static routing and Dynamic routing
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Static routing
&lt;/h3&gt;

&lt;p&gt;It is a method to configure the routing tables by hand.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Administrator
　↓ Configure the route by hand
Router A ──→ Router B ──→ Router C
　　　　　　　　　　　　　　　↓
　　　　　　　　　　　　　Destination NW

Static route → If you need change, you have to update it by hand as well
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Features：
・For small scale network
・Best suited for environments where routes rarely change 
・Simple settings
・Gives administrators full control over routing decisions
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Dynamic routing
&lt;/h3&gt;

&lt;p&gt;It is a method to configure the routing tables automatically.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Router A ←→ Router B ←→ Router C
　↕　　　　　　↕　　　　　　↕
Exchange routing information each other　
Choose the best path automatically 
Handle automatically, if routes change
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Features：
・For large scale network
・Best suited for environments where routes change frequently
・Handle automatically, if routes change
・Protocols： RIP・OSPF・BGP etc…
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Proper use
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Static Routing  → Small scale and the least update environment
Dynamic Routing → Large scale and frequent update environment
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Links with OSI reference model
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Layer 7  Application  │
Layer 6  Presentation │
Layer 5  Session      │  Not applicable for routers
Layer 4  Transport    │
─────────────────────────────
Layer 3  Network      ← Router function （IP Address）
─────────────────────────────
Layer 2  Data Link    ← Switch function （MAC Address）
Layer 1  Physical     ← Cable・ Physical signal
─────────────────────────────
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Familiar example for routers
&lt;/h2&gt;

&lt;p&gt;A home Wi-Fi router is actually an all-in-one device that combines a router, a switch, and a Wi-Fi access point.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Domestic Wi-Fi Router
┌─────────────────────────────────────────────────────────────────┐
│ Router function→ Connect between domestic network and Internet  │
│ Switch function→ Connect PC with wired connection               │
│ Wi-Fi AP function→ Connect devices with wireless connection     │          
└─────────────────────────────────────────────────────────────────┘
　　　　　　　↕
　　     Internet
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Summary
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Router = Devices that transfer data between different networks

Main role：
　→ Routing（ Selection for the best route）
　→ Border for network
　→ NAT（ Sharing one IP by multiple PCs）
　→ Packet filtering

The difference of Router and Switch：
　Router → Layer 3・IP address・ Between different NWs
　Switch → Layer 2・MAC address・ Between same NWs

Routing kinds：
　Static  → manual・ for small scale
　Dynamic → automatic・ for large scale

OSI Layer： Layer 3（Network Layer）
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;When I started to study for them, I couldn't remember each functions of these devices. &lt;br&gt;
Once I connected each function to a familiar real-world example, everything fell into place. Understanding the difference between routers and switches makes these types of questions much easier to handle.&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>learning</category>
      <category>networking</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Understanding Loopback Adapter Through Its Structure</title>
      <dc:creator>TAKUMI SUGATA</dc:creator>
      <pubDate>Mon, 04 May 2026 04:09:48 +0000</pubDate>
      <link>https://dev.to/taqq/understanding-loopback-adapter-through-its-structure-51jl</link>
      <guid>https://dev.to/taqq/understanding-loopback-adapter-through-its-structure-51jl</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;While studying for CompTIA Network+, I couldn't grasp what a Loopback Plug actually does. I understood that it was used for testing, but had no idea how it worked in practice. As a result, I kept getting questions about it wrong. Once I understood the structure behind it, everything clicked. So I decided to write it down.&lt;/p&gt;




&lt;h2&gt;
  
  
  What is NIC
&lt;/h2&gt;

&lt;p&gt;NIC stands for &lt;strong&gt;Network Interface Card&lt;/strong&gt;.&lt;br&gt;
A NIC is &lt;strong&gt;a component inside a computer that enables it to connect to a network&lt;/strong&gt;.&lt;/p&gt;
&lt;h2&gt;
  
  
  Familiar example
&lt;/h2&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Computer = Human beings
NIC      = Ears and mouth

Without ears, we cannot hear voice.
Without mouth, we cannot convey voice.

Similar to these example, computers cannot receive and send signal without NIC.

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;h3&gt;
  
  
  Physical position
&lt;/h3&gt;

&lt;p&gt;NIC is built-in computers.&lt;br&gt;
The visible part is the port where you plug in a LAN cable - the RJ-45 port.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;PC's back or sides
┌───────────────────────────────┐
│  [USB] [USB] [RJ-45] [HDMI]   │
└───────────────────────────────┘
                  ↑
              NIC port
     The hole to insert LAN cable
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  The role for NIC
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;1. Electric signal ↔ Digital data
　→ It transfer electric signal in Network to the data that computers can read

2. MAC address management
　→ Each NIC has a unique identifier called a MAC address
　→ The only number in the world

3. Control for sending and receiving
　→ It controls the timing for sending and receiving data
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Relationship with OSI reference model
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Layer 2  Data Link ← Management for MAC address
Layer 1  Physical  ← Sending and receiving electric signal
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;NIC involves in both Physical and Data Link layers. &lt;/p&gt;




&lt;h2&gt;
  
  
  What is Lookback Plug
&lt;/h2&gt;

&lt;p&gt;A loopback Plug is a &lt;strong&gt;dedicated testing tool used to verify whether a NIC is functioning correctly&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Normally, other devices is needed to connect to Network, but &lt;strong&gt;lookback plug enables us to test for NIC without cables or other devices.&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Normal connection：
PC → cable → switch → the other PC

Loopback Plug：
PC → signal loops back to itself → received by itself
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Kinds
&lt;/h2&gt;

&lt;p&gt;There are two types in Lookback Plug.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;1. RJ-45 Loopback Plug（ for copper wire cables）
2. Fiber Loopback（ for optical fiber）
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  The structure of RJ-45 Lookback Plug
&lt;/h2&gt;

&lt;p&gt;Inside the RJ-45 connector, the sending pins (TX) and receiving pins (RX) are directly connected.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;【RJ-45 Loopback Plug （front）】

┌───────────────────────────────────────────────┐
│  1     2     3     4     5     6     7     8  │
│  TX   TX    RX  　  　         RX      　  　  │
└───────────────────────────────────────────────┘
     │     │ │                   │
     │     └ │ ──────────────────┘    
     └───────┘
    （Connect TX to RX）
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The sent signal loops back inside the plug and returns to the receiving pin.&lt;/p&gt;




&lt;h2&gt;
  
  
  The structure of Fiber Lookback
&lt;/h2&gt;

&lt;p&gt;The Fiber Loopback connects the TX and RX ports using an external cable.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;【Fiber Loopback structure】

        ┌────────────────┐
        │                │
   TX ──┤ &amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt; ├── RX
        │ Electric fiber │
        └────────────────┘

   Sent electric signal turn around to the receiving port
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;【Connector （front）】

  送信側          受信側
┌──────┐   ┌──────┐
│ [TX] │~~~│ [RX] │
│ port │   │ port │
└──────┘   └──────┘
   └──────────┘
Connect with loop cable
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  What is the test purpose with those adapters
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Insert Loopback Plug to NIC port
　↓
Test tools send a signal
　↓
TX （sending pin） sends a signal
　↓
The signal turn around to RX (Receiving pin) within Loopback Plug 
　↓
The same signal comes back
　↓
✓ If it returns → NIC・ port is normal
✗ If it doesn't return → NIC・ port has problems
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  What specifically can we learn
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;✓ What we can know：
・Whether NIC can send and receive signal
・Whether physical port breaks
・Whether NIC itself is normal without cables

✗ What we cannot know：
・Cable issues
・Switch issues
・IP address settings issues
・Internet connection issues
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  How to use in troubleshooting
&lt;/h2&gt;

&lt;p&gt;When PC cannot connect to Network, lookback plug is used to isolate the problems.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Step 1：Test with Loopback Plug
　→ failed → NIC・ port is the cause of problem
　→ success → NIC・ port is not the cause of problem

Step 2：Test with cable
　→ failed → cable is the cause of problem
　→ success → cable is not the cause of problem

Step 3：Test with switch
　→ failed → switch is the cause of problem
　→ success → network settings is the cause of problem
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;** Isolating the root cause step by step** is the fundamental approach to troubleshooting.&lt;/p&gt;




&lt;h2&gt;
  
  
  Relationship with OSI reference model
&lt;/h2&gt;

&lt;p&gt;Lookback plug is used for test in *&lt;em&gt;Physical layer (Layer 1) *&lt;/em&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Layer 7  Application    │
Layer 6  Presentation │  Not subjecting to testing
Layer 5  Session           │
Layer 4  Transport       │
Layer 3  Network         │
Layer 2  Data Link        │
─────────────────────────────
Layer 1  Physical     ← Subjecting to testing with Loopback Plug
─────────────────────────────
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The standard approach is to confirm Physical Layer first, then work upward through each layer.&lt;/p&gt;




&lt;h2&gt;
  
  
  Summary
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;NIC = Computer's components to connect to network
　→ NIC port for LAN cable inserting
　→ Involves in Physical and Data Link layers

Loopback Plug = Plug for testing whether NIC port is normal
　→ Sent signal turn around itself
　→ Kinds：RJ-45・Fiber
　→ What it can test： Physical normalcy in NIC・ port
　→ What it cannot test： cable・ switch・ settings problems
　→ OSI層：Only Physical Layer （Layer 1）
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;I used to struggle with Loopback Plug because I didn't even know what a NIC was in the first place.&lt;br&gt;
Not knowing what NIC was made it impossible to understand what the plug was actually testing. &lt;br&gt;
Once I understood NIC first and then the structure of the Loopback Plug, everything fell into place.&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>learning</category>
      <category>networking</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Understanding Mobile Generation with Netflix</title>
      <dc:creator>TAKUMI SUGATA</dc:creator>
      <pubDate>Sat, 02 May 2026 05:10:11 +0000</pubDate>
      <link>https://dev.to/taqq/understanding-mobile-generation-with-netflix-1fdc</link>
      <guid>https://dev.to/taqq/understanding-mobile-generation-with-netflix-1fdc</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;While studying for CompTIA Network+, I couldn't totally remember each speed for mobile generations; 3G・4G・5G.&lt;/p&gt;

&lt;p&gt;The numbers alone meant nothing to me - I had no way to visualize what they actually felt like. Once I matched each generation's speed to Netflix streaming quality, everything clicked. &lt;/p&gt;




&lt;h2&gt;
  
  
  What is Theoretical Max and Typical Speed
&lt;/h2&gt;

&lt;p&gt;There are two kinds of the speed in mobile communication.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Theoretical Max（ Theoretical value）
　→ The max speed under the ideal condition
　→ No obstacles, directly beside the base station, no congestion

Typical Speed（ Typical value）
　→ The average speed in the actual use environment
　→ Inside buildings, far from base station, congestion
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  The reason why each speed is different
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Radio waves interference
　→ Buildings ・ walls ・ obstacles weak signal

Distance from base station
　→ The farther the base station, the weaker the signal

Number of simultaneous connection
　→ Many users sharing the same base station causes speed to be distributed across all connections

Frequency band
　→ 5G, use high frequency (millimeter wave) , is fast, but short range
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Understanding familiar example
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Theoretical Max = The maximum speed achieved by driving on a highway with no traffic, no traffic lights, and no obstacles

Typical Speed   = The actual average speed in commuting rushing hours
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Even the highest-performing standard is affected by factors such as interference, distance, and the number of simultaneous connections. 
&lt;/h2&gt;

&lt;h2&gt;
  
  
  The speed of each mobile generation
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Generation&lt;/th&gt;
&lt;th&gt;Theoretical Max&lt;/th&gt;
&lt;th&gt;Typical Speed&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;3G&lt;/td&gt;
&lt;td&gt;2Mbps&lt;/td&gt;
&lt;td&gt;384Kbsp〜2Mbps&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4G（LTE）&lt;/td&gt;
&lt;td&gt;1Gbps&lt;/td&gt;
&lt;td&gt;30〜150Mbps&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5G&lt;/td&gt;
&lt;td&gt;20Gbps&lt;/td&gt;
&lt;td&gt;100Mbps〜3Gbps&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h2&gt;
  
  
  Imagine in Netflix
&lt;/h2&gt;

&lt;p&gt;I know it is too hard to think of the just numbers, so I gave an example about Netflix. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;the standard number&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Watch Netflix HD videos = Need approximately 5Mbps
Watch Netflix 4K videos = Need approximately 25Mbps
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h3&gt;
  
  
  3G (Typical Speed：384Kbps〜2Mbps）
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;・Netflix HD → Impossible（ Need 5Mbps, but not stable）
・YouTube (low video quality) → Just barely
・Send message → No problem
・Google search → A bit slower

Downloading time for a 1GB file : about 20 minutes ～ 1 hour
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  This generation spread in 2000s was the first standard that enabled smartphone internet access, but it is no longer in use today.
&lt;/h2&gt;

&lt;h3&gt;
  
  
  4G LTE (Typical Speed：30〜150Mbps)
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;・Netflix HD → Comfortable（ Enough by 5Mbps）
・Netflix 4K → Limited (Need 25Mbps, just barely reached) 
・Video call → Comfortable
・Downloading huge size application → A few minute

Downloading time for a 1GB file : about 3 minutes ～ 7 minutes
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;LTE&lt;/code&gt; stands for &lt;strong&gt;Long Term Evolution&lt;/strong&gt;&lt;br&gt;
This is the most common standard in today's world.&lt;/p&gt;


&lt;h3&gt;
  
  
  5G（Typical Speed：100Mbps〜3Gbps）
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;・Netflix 4K → No problem at all - overwhelmingly faster than the required 25Mbps
・8K Video → Possible
・Simultaneously connection with multiple devices → Comfortable
・Downloading 1GB size application → tens of seconds

Downloading time for a 1GB file : about 10 seconds ～ 1 minute
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;The theoretical maximum of 5G is 20 times faster than of 4G.&lt;br&gt;
But, typical value highly depends on the environments.&lt;br&gt;
This technology is expected to use in the field for IoT, automatic device and smart city.&lt;/p&gt;


&lt;h2&gt;
  
  
  Array of these three generation
&lt;/h2&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Downloading time of 1GB：
3G  → about 20 minutes 〜 an hour
4G  → about 3 〜 7 minutes
5G  → about 10 seconds 〜1 minute
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Features of each generation
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;3G&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;・Spread in 2000's 
・This is the generation for the first time in smartphone use with Internet
・No service in today's world
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;4G LTE&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;・LTE = Long Term Evolution
・Main communication standard in today's world
・Video streaming is comfortable in this generation
・The most common standard over the world
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;5G&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;・Theoretical value is as 20 times as 4G
・Simultaneously connection is as 100 times as 4G
・Latency is approximately 1/30th of 4G (about 1ms)
・Expected to use in the area of IoT ・ automatic drive ・ smart city 
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Summary
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Generation&lt;/th&gt;
&lt;th&gt;Theoretical Max&lt;/th&gt;
&lt;th&gt;Typical Speed&lt;/th&gt;
&lt;th&gt;Netflix HD&lt;/th&gt;
&lt;th&gt;Netflix 4K&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;3G&lt;/td&gt;
&lt;td&gt;2Mbps&lt;/td&gt;
&lt;td&gt;384Kbps〜2Mbps&lt;/td&gt;
&lt;td&gt;✗&lt;/td&gt;
&lt;td&gt;✗&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4G LTE&lt;/td&gt;
&lt;td&gt;1Gbps&lt;/td&gt;
&lt;td&gt;30〜150Mbps&lt;/td&gt;
&lt;td&gt;✓&lt;/td&gt;
&lt;td&gt;△&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5G&lt;/td&gt;
&lt;td&gt;20Gbps&lt;/td&gt;
&lt;td&gt;100Mbps〜3Gbps&lt;/td&gt;
&lt;td&gt;✓&lt;/td&gt;
&lt;td&gt;✓&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h2&gt;
  
  
  How to memorize
&lt;/h2&gt;

&lt;p&gt;It is important to memorize that &lt;strong&gt;relative speed in each  generation&lt;/strong&gt; rather than detailed numbers&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;3G  = Mbps unit（ Cannot totally watch Netflix HD）
4G  = tens Mbps（ Comfortable to watch Netflix HD ・limited to watch 4K video）
5G  = Hundreds of Mbps 〜 Gbps（ Netflix 4K with no issues）
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;I used to struggle with memorizing the speeds for each generation. &lt;br&gt;
Once I connected them to real-world download times, everything fell into place. &lt;br&gt;
Attaching numbers to real experiences makes them far easier to retain. &lt;/p&gt;

</description>
      <category>mobilegeneration</category>
      <category>comptia</category>
      <category>network</category>
    </item>
    <item>
      <title>Understanding the Evolution of CAT Standards Makes Memorization Unnecessary.</title>
      <dc:creator>TAKUMI SUGATA</dc:creator>
      <pubDate>Wed, 29 Apr 2026 04:39:20 +0000</pubDate>
      <link>https://dev.to/taqq/understanding-the-evolution-of-cat-standards-makes-memorization-unnecessary-2g2a</link>
      <guid>https://dev.to/taqq/understanding-the-evolution-of-cat-standards-makes-memorization-unnecessary-2g2a</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;While studying for CompTIA Network+, I couldn't remember CAT standards in LAN cable field. &lt;br&gt;
The sheer number of specification made it difficult to answer related questions confidently.&lt;br&gt;
Once I understand how each standard evolved from the previous one, everything clicked.&lt;/p&gt;


&lt;h2&gt;
  
  
  What is CAT standards
&lt;/h2&gt;

&lt;p&gt;LAN cable has CAT (Category) standards, which shows that higher number perform better. &lt;br&gt;
Understanding the logic behind each standard is more effective than memorizing numbers. &lt;/p&gt;


&lt;h2&gt;
  
  
  Why higher standard accelerates speed
&lt;/h2&gt;

&lt;p&gt;LAN cables consist of 8 copper wires. Trying to increase signal speed introduced two key challenges.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Problem 1：Crosstalk
Receive electrical interference from the adjacent copper cables
→ Signal degrades

Problem 2：Attenuation 
Longer distance weakens signal
→ Not be able to reach
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The higher standards are designed to solve these problems.&lt;/p&gt;




&lt;h2&gt;
  
  
  What is the solution in each evolution stages
&lt;/h2&gt;

&lt;h3&gt;
  
  
  CAT5 → CAT5e
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Problem： Frequent Crosstalk
Solution： Twist Copper cables
Result：100Mbps → 1Gbps
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Twisting has an advantage to solve signal interference.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Rough twisting → More interference → slower
Fine twisting → Less interference → faster
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;e&lt;/code&gt; shows &lt;strong&gt;Enhanced&lt;/strong&gt; .&lt;/p&gt;




&lt;h3&gt;
  
  
  CAT5e → CAT6
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Problem： Pushing beyond 1Gbps increases susceptibility to Crosstalk
Solution： Introduce spine in a center of the cable and more twist
Result：1Gbps → 10Gbps
※10Gbps reaches under 55 meters
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;** Why CAT6 cannot reach over 55 meters in using 10Gbps&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Faster signal = Increase electrical interference
　↓
Longer distance can degrade the signal due to accumulation of interference
　↓
Over 55m cannot retain the speed of 10Gbps
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Without shielding, the cable is susceptible to outside interference.&lt;/p&gt;




&lt;h3&gt;
  
  
  CAT6 → CAT6a
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Problem：CAT6 cannot reach over 55m in 10Gbps
Solution： Wrap the cable by shield (metal shroud), which blocks outer interference
Result：55m (10Gbps) → 100m
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Without shield（CAT6）
→Influenced by outer electric devices 
→Longer distance degrades signal

With shield（CAT6a）
→Block outer interference
→Retain longer distance at 10Gbps
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;a&lt;/code&gt;  shows  &lt;strong&gt;Augmented&lt;/strong&gt; .&lt;/p&gt;




&lt;h3&gt;
  
  
  CAT6a → CAT7
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Problem：CAT6a still has interference at high frequencies between wire pairs 
Solution：Wrap each individual wire pair with its own shield
Result：Crosstalk between pairs reduced to nearly zeeo
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The difference between CAT6a and CAT7 lies in the shielding structure.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;CAT6a：
┌─────────────────────────────────────┐
│ Whole Shield                        │
│  ○ ○ ○ ○（The pair without shield） │
└─────────────────────────────────────┘

CAT7：
┌───────────────────────────────────┐
│ Whole Shield                      │
│ [○][○][○][○]（Individual shield ）│
└───────────────────────────────────┘
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  CAT7 → CAT8
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Problem： Lacking with 10Gbps for data center
Solution： Enforce the quality of copper cables and shield
Result：10Gbps → 40Gbps, but reach just 30m
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;The reason why CAT8 can reach just 30m&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;High speed signal (40Gbps)
　↓
High electrical interference 
　↓
Shield cannot function to retain the signal strength for long distance
　↓
Use under 30m
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;CAT8 is designed for connecting to server racks inside data center.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Server rack A ──── 30m ────→ Server rack B
　↓
The length is enough for data center 
　↓
It prioritize the speed rather than distance
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Why CAT5-CAT6a are the length of 100m
&lt;/h2&gt;

&lt;p&gt;This is the reason for &lt;strong&gt;the designed standard&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The typical distance from one end of an office floor to the other is approximately 100m.&lt;br&gt;
Ethernet standard is designed for architectural standard.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;The edge of the office ──── 100m ────→ Server room
　↓
Ethernet standard can cover them
　↓
CAT5〜CAT6a = 100m
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Understanding whole structure
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Need for fast speed
　↓
Problem for interference and attenuation
　↓
Solution①：more twisted（CAT5e・CAT6）
Solution②：cover with whole shield（CAT6a）
Solution③：cover each pair with individual shield（CAT7）
Solution④：enhance the quality of materials and structure（CAT8）
　↓
The faster the speed, the greater the interference challenges become.
　↓
The limited distance for the fastest speed（CAT8の30m）
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Summary
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Standard&lt;/th&gt;
&lt;th&gt;Speed&lt;/th&gt;
&lt;th&gt;Distance&lt;/th&gt;
&lt;th&gt;Improvement&lt;/th&gt;
&lt;th&gt;Use case&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;CAT5&lt;/td&gt;
&lt;td&gt;100Mbps&lt;/td&gt;
&lt;td&gt;100m&lt;/td&gt;
&lt;td&gt;Normal structure&lt;/td&gt;
&lt;td&gt;Traditional environment&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CAT5e&lt;/td&gt;
&lt;td&gt;1Gbps&lt;/td&gt;
&lt;td&gt;100m&lt;/td&gt;
&lt;td&gt;Twist Copper cables&lt;/td&gt;
&lt;td&gt;Household・Office&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CAT6&lt;/td&gt;
&lt;td&gt;10Gbps&lt;/td&gt;
&lt;td&gt;55m※&lt;/td&gt;
&lt;td&gt;Introduce spine in a center of the cable&lt;/td&gt;
&lt;td&gt;Enterprise office&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CAT6a&lt;/td&gt;
&lt;td&gt;10Gbps&lt;/td&gt;
&lt;td&gt;100m&lt;/td&gt;
&lt;td&gt;Wrap whole cable by shield&lt;/td&gt;
&lt;td&gt;Data center&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CAT7&lt;/td&gt;
&lt;td&gt;10Gbps&lt;/td&gt;
&lt;td&gt;100m&lt;/td&gt;
&lt;td&gt;Wrap the individual cable by shield&lt;/td&gt;
&lt;td&gt;High performance enterprise network&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CAT8&lt;/td&gt;
&lt;td&gt;40Gbps&lt;/td&gt;
&lt;td&gt;30m&lt;/td&gt;
&lt;td&gt;Enforce the quality of copper cables and shield&lt;/td&gt;
&lt;td&gt;Inside data center&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;※CAT6: 10Gbps can reach 55m, but 1Gbps can reach 100m.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key numbers from the exam&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;CAT6  = 10Gbps → 55m (not 100m)
CAT6a = 10Gbps → 100m
CAT8            → 30m
All others      → 100m
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;I used to struggle with these questions.&lt;br&gt;
Each standard exists to solve a specific interference problem. &lt;br&gt;
Once you understand that evolution, the numbers take care of themselves&lt;/p&gt;




</description>
      <category>beginners</category>
      <category>learning</category>
      <category>networking</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Just Choose by Distance — A Simple Guide to Understanding Transceiver and Fiber Cable Compatibility</title>
      <dc:creator>TAKUMI SUGATA</dc:creator>
      <pubDate>Mon, 27 Apr 2026 22:36:13 +0000</pubDate>
      <link>https://dev.to/taqq/just-choose-by-distance-a-simple-guide-to-understanding-transceiver-and-fiber-cable-compatibility-104c</link>
      <guid>https://dev.to/taqq/just-choose-by-distance-a-simple-guide-to-understanding-transceiver-and-fiber-cable-compatibility-104c</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;While studying for CompTIA network+, I couldn't grasp the relationships between Transceiver and Fiber cable. &lt;br&gt;
I could memorize 10GBase-SR uses MMF, but I didn't understand what is that.&lt;/p&gt;

&lt;p&gt;Once I understood the structure, everything cleared up. So I decided to write it down.&lt;/p&gt;


&lt;h2&gt;
  
  
  Why optical fiber is needed
&lt;/h2&gt;

&lt;p&gt;In my last post, I introduced LAN cables (copper cables), which have a limited range.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;LAN cable → Max 100m
Optical fiber  → A few kilometers to tens of kilometers
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In an office use, it is enough to use LAN cable.&lt;br&gt;
However, optical fiber is necessary for connections inside data centers or between remote locations over long distances.&lt;/p&gt;


&lt;h2&gt;
  
  
  What is Transceiver
&lt;/h2&gt;

&lt;p&gt;Switches and routers handle &lt;strong&gt;electrical signals&lt;/strong&gt; internally. &lt;br&gt;
On the other hand, Optical fiber connects with &lt;strong&gt;optical signal&lt;/strong&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Electrical signal → Transceiver → Optical signal → Fiber Cable → Transceiver → Electrical
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A Transceiver is a small module that plugs into a dedicated port called an SFP slot, found on switches and routers.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
Switch
┌────────────────────────────────────┐
│ Port1  Port2  Port3  [SFP slot]    │
└────────────────────────────────────┘
                           ↑
                 Transceiver's port
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  3 parts for connection
&lt;/h2&gt;

&lt;p&gt;There are 3 essential parts involved in this type of connection.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;1. Transceiver （Exchange module）
    This is inserted to Switch's SFP slot
    This plays a role for conversion between electric and light

2. Fiber Cable （Optical fiber cable）
    This is a cable itself to connect between Transceivers
    There are two kinds of MMF or SMF

3. Switch or Router 
    These devices have a dedicated port for Transceiver
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It is important to know that &lt;strong&gt;a single Transceiver alone is not enough&lt;/strong&gt;- you need one at each end.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Switch A                                 Switch B
┌────────────┐                           ┌────────────┐
│ [SFP slot] │                           │ [SFP slot] │
│ Transceiver├─────── Fiber Cable ───────┤Transceiver │
└────────────┘                           └────────────┘ 
　↑                                        ↑
Electrical signal → Optical signal      Optical signal → Electrical signal
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Understanding by familiar analogy
&lt;/h2&gt;

&lt;p&gt;Transceiver is like HDMI conversion adapter for smartphone.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Smartphone （USB-C）
　↓
Conversion adapter （USB-C → HDMI）← Transceiver
　↓
HDMI cable ← Fiber Cable
　↓
Conversion adapter （HDMI → other terminal）← another Transceiver
　↓
TV
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Just as a smartphone can only handle USB-C natively, it can connect to an HDMI cable through an adapter. In the same way, a switch can connect to optical fiber through a Transceiver.&lt;/p&gt;




&lt;h2&gt;
  
  
  Fiber cable type
&lt;/h2&gt;

&lt;p&gt;There are two types of optic fiber cables; MMF and SMF.&lt;/p&gt;

&lt;h3&gt;
  
  
  MMF (Multi-Mode Fiber)
&lt;/h3&gt;

&lt;p&gt;Inside this cable, light proceeds with reflecting many times.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Images of cross section of the cable 

　　↗ ↘ ↗ ↘
→　　　　　　　→（Proceed with reflection）
　　↘ ↗ ↘ ↗
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The more reflections occur, the more the signal degrades.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Features
・Thick core（50〜62.5μm）
・For short distance（〜about 300m）
・Cheap
・Use in data center
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h3&gt;
  
  
  SMF (Single-Mode Fiber)
&lt;/h3&gt;

&lt;p&gt;Inside this cable, light travels in a single straight path without reflection.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Images of cross section of the cable 
→→→→→→→→→→→→（Proceed straightly）
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This type of the cable is more stable, which makes it possible to use for long distance.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Features
・Thin core（9μm）
・For long distance（〜10km以上）
・Expensive
・Use between bases
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  What is 10GBase-SR and 10GBase-LR
&lt;/h2&gt;

&lt;p&gt;Transceiver has two kinds of SR and LR.&lt;br&gt;
Understanding the naming structure eliminates the need for memorization.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;10G  Base  SR
 │    │    │
 │    │    └ S = Short （Short distance）/ L = Long （Long distance）
 │    │      R = Fiber （Optic fiber）
 │    └ Baseband transmission
 └ 10Gbps（Communication speed）
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Standard&lt;/th&gt;
&lt;th&gt;Transceiver&lt;/th&gt;
&lt;th&gt;Fiber Cable&lt;/th&gt;
&lt;th&gt;Distance&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;10GBase-SR&lt;/td&gt;
&lt;td&gt;SR compatible module&lt;/td&gt;
&lt;td&gt;MMF&lt;/td&gt;
&lt;td&gt;〜300m&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;10GBase-LR&lt;/td&gt;
&lt;td&gt;LR compatible module&lt;/td&gt;
&lt;td&gt;SMF&lt;/td&gt;
&lt;td&gt;〜10km&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h2&gt;
  
  
  The concept of how to use them differently
&lt;/h2&gt;

&lt;p&gt;It is essential to understand that Transceiver and Fiber Cable must always be selected as a matching set.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;✓ SR compatible Transceiver + MMF → correct
✗ SR compatible Transceiver + SMF → no function
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Decision making orders↓&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;1. Decide distance
　 → short distance （inside data center） or long distance （between bases）

2. Select Transceiver
　 → short distance = SR / long distance = LR

3. Match Fiber Cable
　 → SR = MMF / LR = SMF
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Big picture
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;【short distance: e.g. inside data center】

Switch A
　└ SFP slot
　　　└ Transceiver（10GBase-SR）
　　　　　└ MMF（〜300m）
　　　　　　　└ Transceiver（10GBase-SR）
　　　　　　　　　└ SFP slot
　　　　　　　　　　　└ Switch B

【long distance ：e.g. between bases】

Switch in Tokyo office
　└ SFP slot
　　　└ Transceiver（10GBase-LR）
　　　　　└ SMF（〜10km）
　　　　　　　└ Transceiver（10GBase-LR）
　　　　　　　　　└ SFP slot
　　　　　　　　　　　└ Switch in Osaka office
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;I used to struggle with memorizing these concepts because I lacked a deep understanding of the structure. Transceiver and Fiber Cable are completely separate components. Once you understand that the choice is driven by distance requirements, everything falls into place.&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>learning</category>
      <category>networking</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>I finally understood the types of LAN cables by focusing on how they actually work.</title>
      <dc:creator>TAKUMI SUGATA</dc:creator>
      <pubDate>Sun, 26 Apr 2026 05:15:42 +0000</pubDate>
      <link>https://dev.to/taqq/i-finally-understood-the-types-of-lan-cables-by-focusing-on-how-they-actually-work-387g</link>
      <guid>https://dev.to/taqq/i-finally-understood-the-types-of-lan-cables-by-focusing-on-how-they-actually-work-387g</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;While studying for CompTIA Network+, I couldn't memorize the types of LAN cables and their use cases. Every time I faced these questions in mock tests, I got them wrong because of the complexity. Understanding the structure behind them cleared things up, so I decided to write it down. &lt;/p&gt;




&lt;h2&gt;
  
  
  What is LAN cable
&lt;/h2&gt;

&lt;p&gt;LAN cable is the cable that connects between computers and network devices physically. The official name is Ethernet cable. &lt;/p&gt;

&lt;p&gt;The connectors attached to both ends of the cable are called RJ-45, and each consists of 8 thin wires (pins).&lt;/p&gt;




&lt;h2&gt;
  
  
  What is a pin
&lt;/h2&gt;

&lt;p&gt;There are 8 thin copper cables inside LAN cable.&lt;br&gt;
These wires, called pins, are each numbered from 1 to 8. Understanding that there are TX (send) and RX (receive) pins is the key to understanding why different cable types exist.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Cross section of RJ-45 connector (8 pins)

┌────────────────────────┐
│ 1  2  3  4  5  6  7  8 │
└────────────────────────┘
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;4 pins are used to send and receive data.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;No 1 &amp;amp; 2 pin →  send data (TX)
No 3 &amp;amp; 6 pin →  receive data (RX)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;As a premise, there are &lt;strong&gt;TX and RX&lt;/strong&gt;, which makes us easy to understand the type of LAN cable.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why we need each type of cables
&lt;/h2&gt;

&lt;p&gt;This is main part of this post.&lt;br&gt;
In the data transfer, both sending and receiving sides are needed.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Device A - sending pin (TX)  → Device B - receiving pin (RX) 
Device B - sending pin (TX)  → Device A - receiving pin (RX)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This TX → RX combination is what makes communication possible. &lt;/p&gt;




&lt;h2&gt;
  
  
  Cable type
&lt;/h2&gt;

&lt;h3&gt;
  
  
  ■Straight-Through
&lt;/h3&gt;

&lt;p&gt;This is the cable that pin at both ends are set &lt;strong&gt;at the same order&lt;/strong&gt;.&lt;br&gt;
This cable is used to connect between &lt;strong&gt;different devices&lt;/strong&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;One end          the other end 
No 1 pin  ─────→ No 1 pin
No 2 pin  ─────→ No 2 pin
No 3 pin  ─────→ No 3 pin
…
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h3&gt;
  
  
  Why this is used to connect different devices
&lt;/h3&gt;

&lt;p&gt;This is an example of different devices (PC and Switch) ;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;PC is designed to send data at No 1 and 2 pins
Switch is designed to receive data at No 1 and 2 pins 
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;PC and Switch are initially designed to transfer data at reverse pins. &lt;br&gt;
Because of this design difference, using a Straight-Through cable naturally results in a proper TX → RX connection between different devices. &lt;/p&gt;

&lt;p&gt;So, it is just to use Straight-Through for sending and receiving data at different devices due to each structure.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;PC : TX (No 1 and 2) ──→ Switch : RX (No 1 and 2)
Switch : TX (No 3 and 6) ──→ PC : RX ( No 3 and 6)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h3&gt;
  
  
  Use case
&lt;/h3&gt;

&lt;p&gt;This type of cable is used to connect to different types of devices.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;PC → Switch
PC → HUB
Router → Switch
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h3&gt;
  
  
  ■Crossover
&lt;/h3&gt;

&lt;p&gt;This is the cable that pin at both ends are set &lt;strong&gt;at crossed order&lt;/strong&gt;.&lt;br&gt;
This cable is used to connect between &lt;strong&gt;the same type of devices&lt;/strong&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;One end          the other end 
No 1 pin  ─────→ No 3 pin
No 2 pin  ─────→ No 6 pin
No 3 pin  ─────→ No 1 pin
No 6 pin  ─────→ No 2 pin
…
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h3&gt;
  
  
  Why this is used to connect the same type of devices
&lt;/h3&gt;

&lt;p&gt;This is an example of the same type of devices (PCs) ;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Both PC-A and PC-B are the same design to send data at No 1 and 2 pins.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If we use Straight-Through cable;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;PC-A : TX (No 1 and 2) ──→ PC-B : TX (No 1 and 2)
　→ Both devices end up connected on the sending side, so neither can receive data. 
　→ No connection
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Therefore, the cable designed crossed pins is needed in this situation.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;PC-A : TX (No 1 and 2) ──→ PC-B : RX (No 3 and 6)
PC-B : TX (No 3 and 6) ──→ PC-A : RX (No 1 and 2)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is the role of crossover cable.&lt;/p&gt;




&lt;h3&gt;
  
  
  Use case
&lt;/h3&gt;

&lt;p&gt;This type of cable is used to connect to the same type of devices.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;PC → PC
Switch → Switch
Router → Router
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h3&gt;
  
  
  ■Rollover
&lt;/h3&gt;

&lt;p&gt;This is the cable that pins are &lt;strong&gt;reversed totally&lt;/strong&gt;. &lt;br&gt;
This is also called Console cable.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;One end          the other end 
No 1 pin  ─────→ No 8 pin
No 2 pin  ─────→ No 7 pin
No 3 pin  ─────→ No 6 pin
…
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is not for data transfer but for &lt;strong&gt;managing or configuring devices&lt;/strong&gt;.&lt;/p&gt;




&lt;h3&gt;
  
  
  Use case
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;PC → Router's console port
PC → Switch's console port
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  What is console port
&lt;/h2&gt;

&lt;p&gt;First of all, we need to understand what console port is.&lt;br&gt;
This is the physical connecting port attached at Router or Switches.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Router's main body
┌───────────────────────┐
│ [LAN] [WAN] [Console] │
└───────────────────────┘
                ↑
This is the console port, which is used to connect by Rollover cable
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h3&gt;
  
  
  Why the connection used by console port is needed
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Normal networking connection（ via LAN）
　→ no connection without IP address settings

Console connection
　→ connection without IP address settings 
　→ use for initial settings or recovery for mechanical issues
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Whether you are setting up a device for the first time or have misconfigured it and lost network access, the console port allows you to access the device directly. &lt;/p&gt;




&lt;h2&gt;
  
  
  Summary
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Cable&lt;/th&gt;
&lt;th&gt;Pin's array&lt;/th&gt;
&lt;th&gt;Use case&lt;/th&gt;
&lt;th&gt;Key words&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Straight-Through&lt;/td&gt;
&lt;td&gt;Same order&lt;/td&gt;
&lt;td&gt;Different devices&lt;/td&gt;
&lt;td&gt;Different = Straight&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Crossover&lt;/td&gt;
&lt;td&gt;Crossed order&lt;/td&gt;
&lt;td&gt;Same devices&lt;/td&gt;
&lt;td&gt;Same = Cross&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Rollover&lt;/td&gt;
&lt;td&gt;Reversed order&lt;/td&gt;
&lt;td&gt;Console access&lt;/td&gt;
&lt;td&gt;Only for setting&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h2&gt;
  
  
  Additional Tips
&lt;/h2&gt;

&lt;p&gt;Most modern NICs (Network Interface Cards) and switches come with &lt;strong&gt;Auto-MDI/MDIX&lt;/strong&gt; built in. This feature allows devices to connect even if the wrong cable type is used.&lt;/p&gt;

&lt;p&gt;Therefore, these function makes us possible to connect with incorrect cables. &lt;br&gt;
However, in the exam of CompTIA Network +, we have to understand each type of cables and those use cases. &lt;/p&gt;




&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;I used to struggle with these questions when I tried to rely on memorization alone.&lt;br&gt;
Once I grasped how TX and RX pins work, everything fell into place.&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>learning</category>
      <category>networking</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Why Does Level 0 Mean the Most Severe? Understanding Syslog Severity Levels</title>
      <dc:creator>TAKUMI SUGATA</dc:creator>
      <pubDate>Thu, 23 Apr 2026 22:59:22 +0000</pubDate>
      <link>https://dev.to/taqq/why-does-level-0-mean-the-most-severe-understanding-syslog-severity-levels-141l</link>
      <guid>https://dev.to/taqq/why-does-level-0-mean-the-most-severe-understanding-syslog-severity-levels-141l</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;While studying for CompTIA Network+, I couldn't totally grasp the severity levels in Syslog. There are 8 levels (0 to 7), and what made it even harder was that &lt;strong&gt;a smaller number means higher severity&lt;/strong&gt;  - which felt completely counterintuitive.&lt;/p&gt;

&lt;p&gt;Once I connected it to practical use cases, everything clicked. So I decided to write it down. &lt;/p&gt;




&lt;h2&gt;
  
  
  What is Syslog
&lt;/h2&gt;

&lt;p&gt;Firstly, let's understand what Syslog is. It is a protocol used by network devices to send and receive log message. &lt;/p&gt;

&lt;p&gt;If errors happen in routers or switches, it can centrally manage the log information by collecting in Syslog server.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;routers ──→
switches ──→ Syslog server (manage network device logs)
servers ──→

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h3&gt;
  
  
  Why central management is needed
&lt;/h3&gt;

&lt;p&gt;Without a Syslog server, engineers have to log in to each network device individually to check logs when an issue occurs. This increases the risk of oversight and makes it harder to identify the root cause quickly. &lt;/p&gt;

&lt;p&gt;However, Syslog server is useful in case of that because it collects logs from multiple network devices in chronological order. An engineer is able to pursue a chain of system failures like below. &lt;br&gt;
" 8 p.m. Level 2 error happens at a router, two minutes later Level 3 error happens at a switch. "&lt;/p&gt;


&lt;h3&gt;
  
  
  Protocol structure
&lt;/h3&gt;

&lt;p&gt;Most network devices have a built-in function to send logs.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;NW devices (Router・Switch)
　└ Attached a function sends Syslog 
　　　↓ Sending Port : UDP 514
Syslog server (Receiving・Accumulating・Visualization)

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Role&lt;/th&gt;
&lt;th&gt;Name&lt;/th&gt;
&lt;th&gt;Example&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Sending side&lt;/td&gt;
&lt;td&gt;Syslog clients  / Generator&lt;/td&gt;
&lt;td&gt;Router ・ Switch&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Receiving side&lt;/td&gt;
&lt;td&gt;Syslog server / Collector&lt;/td&gt;
&lt;td&gt;Splunk・Graylog&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h3&gt;
  
  
  Port Number
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Protocol&lt;/th&gt;
&lt;th&gt;Port&lt;/th&gt;
&lt;th&gt;Features&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;UDP 514&lt;/td&gt;
&lt;td&gt;Default&lt;/td&gt;
&lt;td&gt;Lightweight ・Fast・No delivery guarantee&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;TCP 514&lt;/td&gt;
&lt;td&gt;Partial use&lt;/td&gt;
&lt;td&gt;Delivery guaranteed ・ Reliable&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;TCP 6514&lt;/td&gt;
&lt;td&gt;TLS encryption&lt;/td&gt;
&lt;td&gt;Secure sending&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;In a CompTIA Network+ exam, memorizing &lt;strong&gt;UDP 514&lt;/strong&gt; is enough.&lt;/p&gt;

&lt;p&gt;The reason why UDP is used is that common systems focus to prioritize the speed and light weight in spite of the lack of some logs.&lt;/p&gt;




&lt;h2&gt;
  
  
  What is Severity Level
&lt;/h2&gt;

&lt;p&gt;Syslog message has 8 Level severity.&lt;/p&gt;

&lt;p&gt;It is important to know &lt;strong&gt;Smaller number is more severe&lt;/strong&gt;.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Level&lt;/th&gt;
&lt;th&gt;Name&lt;/th&gt;
&lt;th&gt;Meaning&lt;/th&gt;
&lt;th&gt;Example&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;Emergency&lt;/td&gt;
&lt;td&gt;Whole system is down&lt;/td&gt;
&lt;td&gt;OS crash&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;Alert&lt;/td&gt;
&lt;td&gt;Need to instant handle&lt;/td&gt;
&lt;td&gt;Just before memory exhaustion&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;Critical&lt;/td&gt;
&lt;td&gt;Severe error&lt;/td&gt;
&lt;td&gt;Hardware issue&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;Error&lt;/td&gt;
&lt;td&gt;Error occurance&lt;/td&gt;
&lt;td&gt;Interface down&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;Warning&lt;/td&gt;
&lt;td&gt;Warnings&lt;/td&gt;
&lt;td&gt;High disk usage&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;Notice&lt;/td&gt;
&lt;td&gt;Normal but need to beware&lt;/td&gt;
&lt;td&gt;Configuraion change&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;Informational&lt;/td&gt;
&lt;td&gt;Common information&lt;/td&gt;
&lt;td&gt;User login&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;Debug&lt;/td&gt;
&lt;td&gt;Detail for debug&lt;/td&gt;
&lt;td&gt;Detailed trace for Packet&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h3&gt;
  
  
  Why Number zero is the most severe
&lt;/h3&gt;

&lt;p&gt;The numbering confused me at first because it feels counterintuitive.&lt;/p&gt;

&lt;p&gt;In a computer field, it is common that &lt;strong&gt;Number 0  regards as a top priority&lt;/strong&gt;.&lt;br&gt;
Syslog follow this concept as well. &lt;/p&gt;

&lt;p&gt;An imagination of thermometer can provide easy understanding.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;0 Emergency  ← 🔥 The hottest（Unless instant solution, the system die）
1 Alert
2 Critical
3 Error
4 Warning
5 Notice
6 Informational
7 Debug       ← 🧊 The coldest（A detailed log for a developer）
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Practical use is below&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Level 0 Emergency → Even midnight, engineers need to handle 
Level 7 Debug     → Engineers glance at it over a cup of coffee
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;The higher number, the more calm&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Memorization
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;E&lt;/strong&gt;very &lt;strong&gt;A&lt;/strong&gt;wesome &lt;strong&gt;C&lt;/strong&gt;isco &lt;strong&gt;E&lt;/strong&gt;ngineer &lt;strong&gt;W&lt;/strong&gt;ill &lt;strong&gt;N&lt;/strong&gt;eed &lt;strong&gt;I&lt;/strong&gt;ced &lt;strong&gt;D&lt;/strong&gt;rink&lt;/p&gt;
&lt;/blockquote&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Word&lt;/th&gt;
&lt;th&gt;Level&lt;/th&gt;
&lt;th&gt;Name&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Every&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;Emergency&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Awesome&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;Alert&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cisco&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;Critical&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Engineer&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;Error&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Will&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;Warning&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Need&lt;/td&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;Notice&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Iced&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;Informational&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Drink&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;Debug&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h2&gt;
  
  
  Practical use
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Set a policy
&lt;/h3&gt;

&lt;p&gt;First of all, we have to set a policy that which severity level are needed to send to Syslog server.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Production environment → Over Level 3（Error）
Development environment → All of Level 7（Debug）
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If all levels are forwarded to the Syslog server, the sheer volume of logs can make it easy to overlook critical ones.  Therefore, it is common to set a limited policy in production environment.&lt;/p&gt;




&lt;h3&gt;
  
  
  Consider accumulation and correspondence
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Level 0〜2 → Immediate response
Level 3〜4 → Confirm it until next business day
Level 5〜7 → Confirm it in regular review
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Point to note about UDP
&lt;/h3&gt;

&lt;p&gt;UDP is the port that prioritizes speed rather than secure and trust, therefore it is not guaranteed to reach to the destination correctly. With UDP, in case of network issue, the log may not send to Syslog server. &lt;/p&gt;

&lt;p&gt;On the other hand, because TCP or TLS is more trustable protocol, they are used in more important system such as production environment. &lt;/p&gt;




&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;The counterintuitive numbering - where a smaller number means higher severity - combined with eight levels to memorize, made this topic one of the hardest to grasp.&lt;/p&gt;

&lt;p&gt;The mnemonic and thermometer analogy make it easier to remember. Connecting it to practical use cases accelerates understanding even further. &lt;/p&gt;

</description>
      <category>beginners</category>
      <category>monitoring</category>
      <category>networking</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Stop Memorizing the PDU names — Understand It Like Amazon Delivery</title>
      <dc:creator>TAKUMI SUGATA</dc:creator>
      <pubDate>Wed, 22 Apr 2026 22:35:15 +0000</pubDate>
      <link>https://dev.to/taqq/stop-memorizing-the-pdu-names-understand-it-like-amazon-delivery-38km</link>
      <guid>https://dev.to/taqq/stop-memorizing-the-pdu-names-understand-it-like-amazon-delivery-38km</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;While studying for CompTIA Network+, I couldn't totally grasp the PDU names in the OSI model. I could memorize them, but I never understood why the names are what they are.&lt;/p&gt;

&lt;p&gt;One day, while ordering some items on Amazon, it hit me — the ordering process maps perfectly to the OSI model. So I decided to write it down.&lt;/p&gt;




&lt;h2&gt;
  
  
  What is OSI model
&lt;/h2&gt;

&lt;p&gt;The OSI model is a framework that divides network communication into 7 layers. Separating responsibilities by layer makes it easier to identify which layer is causing a problem. &lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;Name&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;Application&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;Presentation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;Session&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;Transport&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;Network&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;Data Link&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;Physical&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Note: This mnemonic goes from Layer 1 to 7 (bottom to top).&lt;br&gt;
Physical → Data Link → Network  → Transport  → Session  → Presentation  → Applicaion&lt;/p&gt;




&lt;h2&gt;
  
  
  What is PDU
&lt;/h2&gt;

&lt;p&gt;PDU (Protocol Data Unit) is the name given to data at each layer. Each time data passes through a layer, it gets a new name. &lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;PDU name&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;7–5&lt;/td&gt;
&lt;td&gt;Data&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;Segment&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;Packet&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;Frame&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;Bit&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;We can memorize them:&lt;br&gt;
" Do Some People Fear Birthdays?"&lt;/p&gt;

&lt;p&gt;Data → Segment  → Packet  → Frame  → Bit&lt;/p&gt;




&lt;h2&gt;
  
  
  What is Encapsulation and Decapsulation
&lt;/h2&gt;

&lt;p&gt;-Encapsulation: The process of adding headers to data as it moves down the layers (sender side).&lt;br&gt;
-Decapsulation: The process of removing headers from data as it moves up the layers (receiver side).&lt;/p&gt;

&lt;p&gt;We can memorize them:&lt;/p&gt;

&lt;p&gt;-En = put in an envelope → Top to Bottom (7-1), adding header when sending.&lt;br&gt;
-De = take out of the envelope → Bottom to Top (1-7), removing header when receiving.&lt;/p&gt;




&lt;h2&gt;
  
  
  Understand the concept with Amazon ordering
&lt;/h2&gt;

&lt;p&gt;This section is the main part of this article.&lt;br&gt;
When I think about Amazon ordering process - from ordering items to delivering them, I could understand them easily. &lt;/p&gt;




&lt;h3&gt;
  
  
  Layer 7-5 (Data) - Items themselves
&lt;/h3&gt;

&lt;p&gt;Data represents the items we ordered in Amazon.&lt;br&gt;
T-shirts, gadgets, or other items stays in Amazon warehouse. &lt;br&gt;
It is not wrapped yet.&lt;/p&gt;

&lt;h3&gt;
  
  
  Layer 4 (Segment) - Dividing and Numbering them
&lt;/h3&gt;

&lt;p&gt;It can be difficult to deliver them, if the order consists of multiple items. &lt;br&gt;
Therefore, we need to divide into small portion and numbering them 1,2,3…&lt;/p&gt;

&lt;p&gt;Without numbers, it would be impossible to identify which piece is missing if they arrive out of order.&lt;/p&gt;

&lt;h3&gt;
  
  
  Layer 3 (Packet) - Putting in boxes and Labeling them
&lt;/h3&gt;

&lt;p&gt;In this process, divided items are put into boxes and labeling each of them. &lt;br&gt;
Labels show the destination address about receiver (IP address).&lt;br&gt;
The multiple boxes come to do have same address labels.&lt;/p&gt;

&lt;p&gt;The labels are useful to determine routes to deliver. &lt;/p&gt;

&lt;h3&gt;
  
  
  Layer 2 (Frame) - Adding relay labels about next delivering center to Boxes
&lt;/h3&gt;

&lt;p&gt;The destination address (IP address) always stays the same, but the package doesn't travel directly to the final destination -it goes through multiple delivery centers along the way.  &lt;/p&gt;

&lt;p&gt;The actual delivering process is going through many delivering center in each locations until completing delivering, and relay labels, shows destination center, are replaced each time.&lt;br&gt;
This label is the Frame (MAC Address).&lt;/p&gt;

&lt;p&gt;-Destination address label (IP Address) = Final destination = stays same&lt;br&gt;
-Relay label (MAC Address) = Next center destination = replaced whenever the items go through delivering center&lt;/p&gt;

&lt;h3&gt;
  
  
  Layer 1 (Bit) - Transporting
&lt;/h3&gt;

&lt;p&gt;Actually, those boxes are transported physically by track.&lt;br&gt;
Items go through cables or wireless as electrical or light signal (0,1) .&lt;br&gt;
Ultimately, any data are exchanged to 0 and 1.&lt;/p&gt;




&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;[Sending side: Encapsulation]&lt;br&gt;
Items (Data)&lt;br&gt;
↓ Dividing and numbering&lt;br&gt;
Segments&lt;br&gt;
↓ Labeling with destination address (IP Address)&lt;br&gt;
Packets&lt;br&gt;
↓ Labeling with next delivery center (MAC Address)&lt;br&gt;
Frames&lt;br&gt;
↓ Physical transport&lt;br&gt;
Bits → Network&lt;/p&gt;

&lt;p&gt;[Receiving side: Decapsulation]&lt;br&gt;
Bits ← Network&lt;br&gt;
↓ Removing relay labels at each delivery center&lt;br&gt;
Frames → Packets → Segments&lt;br&gt;
↓ Reassembling and unpacking&lt;br&gt;
Items (Data)&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>learning</category>
      <category>networking</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
