<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Ethernet · Network Doodles</title><link>https://networkdoodles.com/tags/ethernet/</link><description>Network automation, from first playbook to agentic operations. Ansible, NetBox, MCP, Python and the occasional doodle.</description><language>en-us</language><managingEditor>David Henderson</managingEditor><lastBuildDate>Mon, 16 Nov 2026 09:00:00 -0500</lastBuildDate><atom:link href="https://networkdoodles.com/tags/ethernet/index.xml" rel="self" type="application/rss+xml"/><item><title>What a Packet Capture Shows You (Wireshark 101, Lesson 1)</title><link>https://networkdoodles.com/lessons/wireshark-101/what-a-capture-shows/</link><pubDate>Mon, 16 Nov 2026 09:00:00 -0500</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/lessons/wireshark-101/what-a-capture-shows/</guid><category>wireshark</category><category>packet-capture</category><category>networking-basics</category><category>ethernet</category><description>What a packet capture records, how Wireshark's three panes map to the layers, pcap vs pcapng, and why where you capture decides what you can see.</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>A packet capture is a recording of every frame that crossed one point in the network while the recording
ran: each one bit for bit, with the time it was seen. Wireshark opens that recording and decodes it, layer by
layer. The most important thing to know about a capture is that it only shows <strong>its own point</strong>. Pick the
wrong cable and you see nothing, and <em>nothing</em> looks exactly like <em>it never happened</em>.</p>
<p><a href="/lessons/networking-101/">Networking 101</a> explained what MAC addresses, IP addresses, switches and routers
are. This course shows you what they actually put on the wire. This first lesson is about the tool itself:
what&rsquo;s in a capture, how Wireshark lays it out, what the timestamps mean, the two file formats, and the
question every capture starts with: <em>where am I listening?</em></p>
<hr>
<h2 id="what-is-a-packet-capture">What is a packet capture?</h2>
<p>Everything you&rsquo;ve used to look at a network so far is a summary. <code>ip neigh</code> shows what a host <em>concluded</em>
about its neighbors. <code>show mac address-table</code> shows what a switch <em>learned</em>. A routing table shows what a
router <em>decided</em>. They&rsquo;re all useful, and they&rsquo;re all someone&rsquo;s interpretation.</p>
<p>A capture isn&rsquo;t. It&rsquo;s the frames themselves, in the order they were seen, with nothing left out and nothing
summarized. When a show command and a capture disagree, the capture is the one that&rsquo;s telling you what
happened. That&rsquo;s why engineers reach for it when everything else says the network is fine and the
application says it isn&rsquo;t.</p>
<p>Two words before we go on. A <strong>frame</strong> is a message in its layer 2 envelope: an Ethernet header with a <em>to</em>
and a <em>from</em> MAC address, and something inside. A <strong>packet</strong> is, strictly, the layer 3 thing inside it, with
IP addresses. Wireshark and everyone else say &ldquo;packet&rdquo; for both, and so will I, except where the difference
matters.</p>
<p>Each frame in a capture is stored with a few extra facts the capture added:</p>
<ul>
<li><strong>when</strong> it was seen, to the nanosecond in the lab&rsquo;s files;</li>
<li><strong>where</strong> it was seen: the name of the interface it was captured on;</li>
<li><strong>how long</strong> it was on the wire, and how many of those bytes were saved (more on that in
<a href="/lessons/wireshark-101/capture-vs-display-filters/">lesson 2</a>).</li>
</ul>
<p>Then the bytes, exactly as they were.</p>
<hr>
<h2 id="how-do-wiresharks-three-panes-map-to-the-layers">How do Wireshark&rsquo;s three panes map to the layers?</h2>
<p>Open a capture and Wireshark shows three panes, top to bottom.</p>
<table>
  <thead>
      <tr>
          <th>Pane</th>
          <th>What it shows</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td><strong>Packet list</strong></td>
          <td>one line per frame: number, time, source, destination, protocol, length, a one-line summary</td>
      </tr>
      <tr>
          <td><strong>Packet details</strong></td>
          <td>the frame you clicked, one layer per line, each one opens to show its fields</td>
      </tr>
      <tr>
          <td><strong>Packet bytes</strong></td>
          <td>the same frame as raw hex. Click a field in the details and its bytes light up</td>
      </tr>
  </tbody>
</table>
<p>The packet list is for finding things. Here&rsquo;s the start of the lab&rsquo;s first capture, taken on the laptop&rsquo;s
cable while it pings the printer, as tshark (Wireshark&rsquo;s command-line twin, version 4.6.5 here) prints it:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">    3 2.177114918 aa:aa:aa:11:11:11 → Broadcast    ARP 42 Who has 192.168.1.20? Tell 192.168.1.175
</span></span><span class="line"><span class="cl">    4 2.177311459 aa:aa:aa:22:22:22 → aa:aa:aa:11:11:11 ARP 42 192.168.1.20 is at aa:aa:aa:22:22:22
</span></span><span class="line"><span class="cl">    5 2.177313709 192.168.1.175 → 192.168.1.20 ICMP 98 Echo (ping) request  id=0x0926, seq=1/256, ttl=64
</span></span><span class="line"><span class="cl">    6 2.177450834 192.168.1.20 → 192.168.1.175 ICMP 98 Echo (ping) reply    id=0x0926, seq=1/256, ttl=64 (request in 5)
</span></span></code></pre></div><p>Two things in that list are worth knowing straight away. The <strong>Protocol</strong> column is the <em>highest</em> layer
Wireshark recognized, not the only one: a ping is ICMP inside IP inside Ethernet. And the source and
destination columns show IP addresses when there&rsquo;s an IP layer, and fall back to MAC addresses when there
isn&rsquo;t, which is why the ARP lines look different.</p>
<p>The details pane is where the layers from Networking 101&rsquo;s
<a href="/lessons/networking-101/task-1-2/">OSI lesson</a> become visible. Click frame 5 and you get:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">Frame 5: Packet, 98 bytes on wire (784 bits), 98 bytes captured (784 bits) on interface laptop:eth1, id 0
</span></span><span class="line"><span class="cl">Ethernet II, Src: aa:aa:aa:11:11:11 (aa:aa:aa:11:11:11), Dst: aa:aa:aa:22:22:22 (aa:aa:aa:22:22:22)
</span></span><span class="line"><span class="cl">Internet Protocol Version 4, Src: 192.168.1.175, Dst: 192.168.1.20
</span></span><span class="line"><span class="cl">Internet Control Message Protocol
</span></span></code></pre></div><table>
  <thead>
      <tr>
          <th>Line</th>
          <th>Layer</th>
          <th>What it holds</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td><strong>Frame</strong></td>
          <td>none: Wireshark&rsquo;s own notes</td>
          <td>when and where the capture saw it, its length</td>
      </tr>
      <tr>
          <td><strong>Ethernet II</strong></td>
          <td>2, data link</td>
          <td>the MAC addresses, and the type of what&rsquo;s inside</td>
      </tr>
      <tr>
          <td><strong>Internet Protocol Version 4</strong></td>
          <td>3, network</td>
          <td>the IP addresses, the TTL, the protocol inside</td>
      </tr>
      <tr>
          <td><strong>Internet Control Message Protocol</strong></td>
          <td>3, carried in IP</td>
          <td>the ping itself</td>
      </tr>
  </tbody>
</table>
<p>For a web request you&rsquo;d see TCP (layer 4) under IP, and HTTP under that. The order is the order of the
envelopes on the wire: outermost first. Reading top to bottom is unwrapping the package.</p>
<p>The <strong>Frame</strong> line is the one people misread. It isn&rsquo;t a protocol and nothing on the wire sent it. It&rsquo;s the
capture&rsquo;s own label on the frame: the arrival time, the interface, the lengths. You&rsquo;ll use it more than you&rsquo;d
think, because &ldquo;on interface laptop:eth1&rdquo; is the answer to &ldquo;where was this seen?&rdquo;.</p>
<p>The bytes pane is the honest one. The details pane is Wireshark&rsquo;s <em>interpretation</em> of those bytes, made by a
<strong>dissector</strong>: the piece of Wireshark that knows how to decode one protocol. Dissectors are very good, but
when one guesses wrong (a protocol on an unusual port, say), the bytes are still right.</p>
<hr>
<h2 id="what-do-the-timestamps-mean">What do the timestamps mean?</h2>
<p>Every frame gets a timestamp from the machine doing the capturing, at the moment the capture saw it. Not when
the sender built it, and not when the receiver read it. That distinction matters as soon as you capture at
more than one place, because two capture points have two clocks.</p>
<p>Wireshark shows the time in the packet list as <strong>seconds since the first frame</strong> by default. You can switch
it (View › Time Display Format) to the time of day, or to the time since the previous frame, which is what
you want when you&rsquo;re looking for a pause. The real time is always in the Frame line:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">Arrival Time: Nov 11, 2026 01:46:20.722588928 UTC
</span></span></code></pre></div><p>Timestamps are where a capture turns into measurements. In the capture above, the printer&rsquo;s ARP reply came
196.5 microseconds after the laptop&rsquo;s question (frame 3 to frame 4), and the first ping&rsquo;s reply came 137
microseconds after the request (frame 5 to frame 6). Those numbers are from the laptop&rsquo;s cable, so they include
the switch, the printer&rsquo;s own processing, and the switch again. A ping in the lab&rsquo;s second capture, to a web
server two routers away, took 566 microseconds, measured on the switch&rsquo;s port towards the first router. Time
between a question and its answer, measured on the asker&rsquo;s cable, is the round trip that user actually
experienced. Measured anywhere else, it&rsquo;s the round trip from that point onwards.</p>
<hr>
<h2 id="whats-the-difference-between-pcap-and-pcapng">What&rsquo;s the difference between pcap and pcapng?</h2>
<p>Captures are saved in one of two file formats.</p>
<p><strong>pcap</strong> is the original, from the tcpdump world. It&rsquo;s simple: a short file header, then one record per
frame. <strong>pcapng</strong> (<em>pcap next generation</em>) is what Wireshark saves by default today, and what the lab&rsquo;s
captures use. It&rsquo;s built from blocks, so it can say much more about the capture.</p>
<table>
  <thead>
      <tr>
          <th></th>
          <th>pcap</th>
          <th>pcapng</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Interfaces per file</td>
          <td>one link type, no names</td>
          <td>several, each with its name</td>
      </tr>
      <tr>
          <td>Timestamp resolution</td>
          <td>microseconds (the classic format)</td>
          <td>per interface; nanoseconds in the lab&rsquo;s files</td>
      </tr>
      <tr>
          <td>Comments</td>
          <td>no</td>
          <td>on the file and on each frame</td>
      </tr>
      <tr>
          <td>Which program made it</td>
          <td>no</td>
          <td>yes</td>
      </tr>
      <tr>
          <td>Who can read it</td>
          <td>nearly everything</td>
          <td>Wireshark, tshark, tcpdump&rsquo;s libpcap and most current tools</td>
      </tr>
  </tbody>
</table>
<p>Here&rsquo;s what that means in practice. The lab&rsquo;s capture of two switch ports, converted from pcapng to pcap with
Wireshark&rsquo;s <code>editcap</code>, went from 1,524 bytes to 1,186. The bytes saved are the bad news: the interface names
<code>sw1:eth1</code> and <code>sw1:eth3</code> were gone (every frame now came from one nameless interface), and every timestamp
lost its last three digits:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">pcapng: 1794361588.669028918
</span></span><span class="line"><span class="cl">pcap:   1794361588.669028000
</span></span></code></pre></div><p>The interface name is the bit you&rsquo;ll miss. When one file holds two capture points, that name is the only way
to tell them apart. So keep captures in pcapng, and only convert when a tool demands pcap.</p>
<hr>
<h2 id="why-does-where-you-capture-decide-what-you-see">Why does where you capture decide what you see?</h2>
<p>This is the section to remember. A capture records one point in the network, and what crosses that point
depends on what&rsquo;s around it.</p>
<h3 id="a-hosts-own-port">A host&rsquo;s own port</h3>
<p>Capture on a host&rsquo;s cable, as the lab&rsquo;s first task does on the laptop, and you see everything that host sends
and everything sent to it, plus the network&rsquo;s broadcasts. That&rsquo;s the easy case, because the host is one end of
every conversation you&rsquo;re looking at.</p>
<h3 id="a-switch-port-other-peoples-unicast-isnt-there">A switch port: other people&rsquo;s unicast isn&rsquo;t there</h3>
<p>Networking 101&rsquo;s <a href="/lessons/networking-101/task-2-1/">lesson on switches</a> gave the rule. A switch sends a
frame for one MAC address out of <strong>one port</strong>, the one where it learned that address. It sends a broadcast
out of <strong>every</strong> port. It floods a frame for an address it hasn&rsquo;t learned yet out of every port too, but only
until it learns it.</p>
<p>So a capture on a switch port sees that port&rsquo;s own host, the broadcasts, and the occasional flood. Nothing
else. The lab shows it with two captures taken at once, on sw1&rsquo;s port towards r1 and its port towards the
printer, while the laptop pings a server on another network:</p>
<table>
  <thead>
      <tr>
          <th>Seen on</th>
          <th>ARP</th>
          <th>ICMP (pings and replies)</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>r1&rsquo;s port, <code>sw1:eth1</code></td>
          <td>the laptop&rsquo;s request and r1&rsquo;s reply</td>
          <td>all 6</td>
      </tr>
      <tr>
          <td>the printer&rsquo;s port, <code>sw1:eth3</code></td>
          <td>the laptop&rsquo;s request only</td>
          <td>0</td>
      </tr>
  </tbody>
</table>
<p>The printer&rsquo;s cable carried exactly one frame of that conversation: the ARP request, because it was a
broadcast. r1&rsquo;s reply was addressed to the laptop alone, and the pings were addressed to r1&rsquo;s MAC address, so
the switch never sent them anywhere near the printer. That&rsquo;s the switch doing its job.</p>
<p>It&rsquo;s also why &ldquo;I&rsquo;ll plug my laptop into a spare switch port and capture&rdquo; doesn&rsquo;t work. You&rsquo;ll see broadcasts,
your own traffic, and very little else. In the days of hubs, which repeated everything to everyone, it did
work. Switches ended that.</p>
<h3 id="mirror-ports-and-taps">Mirror ports and taps</h3>
<p>Real networks solve this in two ways.</p>
<p>A <strong>mirror port</strong> (Cisco calls it <strong>SPAN</strong>, for <em>switched port analyzer</em>) is a switch feature: you tell the
switch to send a copy of everything on one or more ports, or a whole VLAN, out of another port, where your
capture machine sits. It costs nothing but configuration. The catch is that it&rsquo;s the switch&rsquo;s best effort:
a mirror port can only send as much as its own link carries, so if you mirror more traffic than that, some
copies are dropped, and your capture is missing frames the real network delivered.</p>
<p>A <strong>tap</strong> is a small device you put in the cable itself. It passes the traffic through and copies it to a
monitoring port. It sees exactly what was on the wire, but you have to break the cable to install it, which
is why taps go in during planned work and stay there.</p>
<p>The lab does something closer to a tap: <code>containerlab capture</code> records a port from outside the node, so
nothing on the laptop or the switch knows it&rsquo;s being watched, and you can capture any cable in the network.</p>
<h3 id="inside-a-host-versus-on-the-wire">Inside a host versus on the wire</h3>
<p>There&rsquo;s one more place to capture: on the host itself, with Wireshark installed on the laptop. That&rsquo;s the
most common capture there is, and it comes with a surprise.</p>
<p>Modern network cards do work the operating system used to do. Two kinds of this <strong>offload</strong> change what a
capture on the host shows. With <em>checksum offload</em>, the card fills in the IP and TCP checksums just before
the frame leaves, so a capture of outgoing traffic, taken before the card, sees checksums that haven&rsquo;t been
calculated yet. With <em>segmentation offload</em>, the operating system hands the card one big block of data and
the card cuts it into frames, so the capture shows &ldquo;packets&rdquo; larger than the network&rsquo;s MTU, which no
real cable could have carried. Wireshark&rsquo;s own
<a href="https://wiki.wireshark.org/CaptureSetup/Offloading">page on offloading</a> explains both.</p>
<p>Neither is a fault. Both are the capture being honest about where it is: above the card, not on the wire.
If a host capture shows bad checksums on everything it sent, or 1,500-byte limits apparently ignored,
check offloads before you suspect the network.</p>
<table>
  <thead>
      <tr>
          <th>Capture point</th>
          <th>Sees</th>
          <th>Doesn&rsquo;t see</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>on the host itself</td>
          <td>what that host sent and received, as the OS saw it</td>
          <td>other hosts&rsquo; traffic; the final checksums and frame sizes</td>
      </tr>
      <tr>
          <td>a switch port</td>
          <td>that port&rsquo;s host, broadcasts, floods</td>
          <td>other hosts&rsquo; unicast</td>
      </tr>
      <tr>
          <td>a mirror (SPAN) port</td>
          <td>copies of the ports or VLAN you chose</td>
          <td>copies the switch dropped when the mirror was full</td>
      </tr>
      <tr>
          <td>a tap</td>
          <td>exactly what was on that cable</td>
          <td>anything on another cable</td>
      </tr>
  </tbody>
</table>
<hr>
<h2 id="what-i-see-go-wrong">What I see go wrong</h2>
<p><strong>Capturing in the wrong place, and believing the silence.</strong> Someone captures on the server, sees no
request, and concludes the client never sent one. Maybe it didn&rsquo;t. Or maybe it was dropped on the way, or
went to a different server. A capture can prove a frame crossed a point. Its absence only proves it didn&rsquo;t
cross <em>that</em> point. The fix is a second capture closer to the sender, and lesson 8 of this course is built
around it.</p>
<p><strong>Expecting a switch port to show everyone.</strong> It won&rsquo;t, as the table above shows. If you need someone else&rsquo;s
traffic, capture on their port, on the uplink they use, or on a mirror of it.</p>
<p><strong>Comparing timestamps from two machines.</strong> Two captures taken on two computers use two clocks. A few
milliseconds&rsquo; difference between them is often just the clocks disagreeing. Compare times <em>within</em> one capture,
or use one machine that records both points into one file, which is what the lab does.</p>
<p><strong>Reading checksum errors as damage.</strong> On a host capture, outgoing frames with &ldquo;incorrect&rdquo; checksums are
almost always checksum offload. Damaged frames on a real wire usually don&rsquo;t reach a capture at all, because
the receiving card throws them away.</p>
<p><strong>Saving in a format that loses the answer.</strong> A multi-point capture converted to pcap has lost the one field
that says which point each frame came from.</p>
<hr>
<h2 id="try-it">Try it</h2>
<p><a href="/labs/wireshark-101/#chapter-1">Chapter 1 of the lab</a> has you take your first capture on the laptop&rsquo;s cable,
open it in Wireshark in your browser, read the three panes, and then capture two switch ports at once to see
for yourself which cable carried which frames.</p>
<h2 id="whats-next">What&rsquo;s next</h2>
<p>A busy network gives you thousands of frames a second.
<a href="/lessons/wireshark-101/capture-vs-display-filters/">Lesson 2</a> is about cutting that down: capture filters,
which decide what&rsquo;s saved at all, and display filters, which decide what you look at, and the one small
operator whose meaning changed under everyone&rsquo;s feet.</p>
]]></content:encoded></item></channel></rss>