{"id":3800,"date":"2025-04-27T15:38:50","date_gmt":"2025-04-27T15:38:50","guid":{"rendered":"https:\/\/www.it-react.com\/?p=3800"},"modified":"2025-09-19T16:05:32","modified_gmt":"2025-09-19T16:05:32","slug":"esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2","status":"publish","type":"post","link":"https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/","title":{"rendered":"ESXi Packet Loss Troubleshooting with iPerf3 &amp; pktcap-uw \u2013 Part 2"},"content":{"rendered":"\n<div style=\"border-left: 4px solid #3498db; padding: 10px; background-color: #eef6fc;\">\n  <strong>This article is part of the 5-part series:<\/strong><br>\n  <em>\u201cESXi Packet Loss Troubleshooting with iPerf3 and pktcap-uw\u201d<\/em>\n  <ul style=\"margin-top: 5px; margin-bottom: 5px;\">\n    <li><a class=\"effect1\" href=\"https:\/\/www.it-react.com\/index.php\/2025\/04\/19\/esxi-packet-loss-troubleshooting-with-iperf3-and-pktcap-uw-part-1\/\" target=\"_blank\"><strong>Part 1:<\/strong> Baseline Testing and Setup<\/a><\/li>\n    <li><u><strong>Part 2:<\/strong> Capturing UDP Traffic Under Different CPU Loads<\/u> \u2190 You are here <\/li>\n    <li><a class=\"effect1\" href=\"https:\/\/www.it-react.com\/index.php\/2025\/05\/06\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-3\/\" target=\"_blank\"><strong>Part 3:<\/strong> Analyzing Packet Loss with Wireshark<\/a><\/li>\n    <li><a class=\"effect1\" href=\"https:\/\/www.it-react.com\/index.php\/2025\/05\/08\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-4\/\" target=\"_blank\"><strong>Part 4:<\/strong> UDP Loss from Link Flapping and Network Instability<\/a><\/li>\n    <li><a class=\"effect1\" href=\"https:\/\/www.it-react.com\/index.php\/2025\/05\/08\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-5\/\" target=\"_blank\"><strong>Part 5:<\/strong> Inter-VLAN UDP Loss Caused by Bandwidth Limits<\/a><\/li>\n  <\/ul>\n<\/div>\n\n\n\n<p>Welcome back! In the previous post, we laid the foundation by performing a baseline UDP performance test between two ESXi hosts using iPerf. That gave us a solid starting point to understand what \u201cnormal\u201d looks like.<\/p>\n\n\n\n<p>Now it\u2019s time to dive deeper.<\/p>\n\n\n\n<p>In this part, we\u2019ll simulate more complex and stressful conditions\u2014starting with CPU overload\u2014to see how it impacts packet loss and jitter. We\u2019ll also put the powerful pktcap-uw tool to good use, capturing traffic at different layers of the network stack to get a clearer picture of where things might go wrong.<\/p>\n\n\n\n<p>Whether you&#8217;re dealing with UDP-heavy workloads, troubleshooting VoIP issues, or just curious about network behavior in virtualized environments, this part is where things really start to get interesting.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Lab Setup <\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Sending VM<\/strong>: 192.168.110.101 (VLAN 110)<\/li>\n\n\n\n<li><strong>Receiving VM<\/strong>: 192.168.110.103 (VLAN 110)<\/li>\n\n\n\n<li><strong>Simulate CPU Load<\/strong>: CPUStres on VMs<\/li>\n\n\n\n<li><strong>Traffic Generator<\/strong>: iPerf3 using UDP, sustained for 300 seconds<\/li>\n<\/ul>\n\n\n\n<figure data-wp-context=\"{&quot;imageId&quot;:&quot;69fa7b5e6bf3c&quot;}\" data-wp-interactive=\"core\/image\" class=\"wp-block-image size-large wp-lightbox-container\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"487\" data-wp-class--hide=\"state.isContentHidden\" data-wp-class--show=\"state.isContentVisible\" data-wp-init=\"callbacks.setButtonStyles\" data-wp-on-async--click=\"actions.showLightbox\" data-wp-on-async--load=\"callbacks.setButtonStyles\" data-wp-on-async-window--resize=\"callbacks.setButtonStyles\" src=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/iperf_windows_vmnic-1024x487.jpg\" alt=\"\" class=\"wp-image-3880\" srcset=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/iperf_windows_vmnic-1024x487.jpg 1024w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/iperf_windows_vmnic-300x143.jpg 300w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/iperf_windows_vmnic-768x365.jpg 768w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/iperf_windows_vmnic-1536x730.jpg 1536w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/iperf_windows_vmnic-2048x974.jpg 2048w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><button\n\t\t\tclass=\"lightbox-trigger\"\n\t\t\ttype=\"button\"\n\t\t\taria-haspopup=\"dialog\"\n\t\t\taria-label=\"Enlarge\"\n\t\t\tdata-wp-init=\"callbacks.initTriggerButton\"\n\t\t\tdata-wp-on-async--click=\"actions.showLightbox\"\n\t\t\tdata-wp-style--right=\"state.imageButtonRight\"\n\t\t\tdata-wp-style--top=\"state.imageButtonTop\"\n\t\t>\n\t\t\t<svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"12\" height=\"12\" fill=\"none\" viewBox=\"0 0 12 12\">\n\t\t\t\t<path fill=\"#fff\" d=\"M2 0a2 2 0 0 0-2 2v2h1.5V2a.5.5 0 0 1 .5-.5h2V0H2Zm2 10.5H2a.5.5 0 0 1-.5-.5V8H0v2a2 2 0 0 0 2 2h2v-1.5ZM8 12v-1.5h2a.5.5 0 0 0 .5-.5V8H12v2a2 2 0 0 1-2 2H8Zm2-12a2 2 0 0 1 2 2v2h-1.5V2a.5.5 0 0 0-.5-.5H8V0h2Z\" \/>\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Identify Active vmnics on Sending and Receiving ESXi Hosts<\/strong><\/h2>\n\n\n\n<p>Since we\u2019re using IP hash-based load balancing, one challenge is identifying which vmnic is actually being used to send traffic. We&#8217;ll generate traffic with iPerf3 and use esxtop to monitor traffic levels per NIC and determine the active path, then start pktcap-uw on that vmnic to capture packets at the physical layer.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step one: Generate Traffic to Identify vmnics on Both Hosts with esxtop<\/strong><\/h3>\n\n\n\n<p>We start by generating high traffic between the two VMs using iPerf3. One VM acts as the server, the other as the client \u2014 and for this task, it\u2019s preferable to use <strong>TCP<\/strong> traffic, as it\u2019s easier to spot in monitoring tools like esxtop.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"695\" height=\"230\" src=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/grafik-7.png\" alt=\"\" class=\"wp-image-3846\" srcset=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/grafik-7.png 695w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/grafik-7-300x99.png 300w\" sizes=\"auto, (max-width: 695px) 100vw, 695px\" \/><\/figure>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"693\" height=\"221\" src=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/grafik-8.png\" alt=\"\" class=\"wp-image-3847\" srcset=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/grafik-8.png 693w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/grafik-8-300x96.png 300w\" sizes=\"auto, (max-width: 693px) 100vw, 693px\" \/><\/figure>\n\n\n\n<p>At this stage, we\u2019re not analyzing performance or packet quality; the only goal is to identify which physical NIC (vmnic) is used on both the <strong>sending<\/strong> and <strong>receiving<\/strong> ESXi hosts.<\/p>\n\n\n\n<p>To do that, we connect to each host via SSH, launch <strong><em>esxtop<\/em><\/strong>, and press <strong><em>n<\/em><\/strong> to enter the network view. While the traffic is running, we observe which vmnic shows increased throughput \u2014 that\u2019s the one carrying the traffic.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"308\" src=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-1024x308.png\" alt=\"\" class=\"wp-image-3850\" srcset=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-1024x308.png 1024w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-300x90.png 300w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-768x231.png 768w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image.png 1097w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"363\" src=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-1-1024x363.png\" alt=\"\" class=\"wp-image-3851\" srcset=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-1-1024x363.png 1024w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-1-300x106.png 300w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-1-768x272.png 768w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-1.png 1095w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>IP Host 192.168.1.10 &#8211; Sending Host using vmnic2<br>IP Host 192.168.2.12 &#8211; Receiving Hosts using vmnic0<\/p>\n\n\n\n<p>Using the above commands, we can also identify the switch ports assigned to each VM. In our case, the sending VM (DC01) is connected to port <strong>67108883<\/strong>, while the receiving VM (Windows Server 2022) is connected to port <strong>67108882<\/strong>. As you can see, the ESXi hosts are managed by different vCenter instances.<br><br>Another useful command to display the VMs and their respective switch and switchports is:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>net-stats -l <\/code><\/pre>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"224\" src=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-6-1024x224.png\" alt=\"\" class=\"wp-image-3876\" srcset=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-6-1024x224.png 1024w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-6-300x65.png 300w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-6-768x168.png 768w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-6.png 1095w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step two: What If You Can\u2019t Identify the vmnic Easily?<\/strong><\/h3>\n\n\n\n<p>In environments with multiple VMs and active connections, pinpointing the correct vmnic can be tricky. Traffic might be spread across interfaces due to load balancing, or the load may be too light to stand out in esxtop.<\/p>\n\n\n\n<p>If you&#8217;re unable to clearly identify the active NICs for either host, you can take a different approach: run <strong><em>pktcap-uw<\/em><\/strong> on all physical NICs one by one and look for packets matching your test traffic. <br>pktcap-uw allows capturing packets inside the ESXi network stack, at different points like the virtual switchport or the physical uplink.<\/p>\n\n\n\n<p>You can list all physical uplinks with:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>esxcli network nic list<\/code><\/pre>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"154\" src=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-2-1024x154.png\" alt=\"\" class=\"wp-image-3854\" srcset=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-2-1024x154.png 1024w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-2-300x45.png 300w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-2-768x116.png 768w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-2.png 1094w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Then, start a capture on each vmnic until you spot the iPerf traffic.<\/p>\n\n\n\n<p>On the sending host, we issued the command below and, just like before, confirmed that the traffic flows through vmnic2.:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>#pktcap-uw --uplink vmnic2 --dstip 192.168.110.103 --proto 0x06 -p 10101 --dir 1 -o trace_vmnic2.pcap<\/code><\/pre>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"270\" src=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-3-1024x270.png\" alt=\"\" class=\"wp-image-3856\" srcset=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-3-1024x270.png 1024w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-3-300x79.png 300w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-3-768x202.png 768w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-3.png 1094w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>On the receiving host, we issued the command below:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>pktcap-uw --uplink vmnic0 --srcip 192.168.110.101 --proto 0x06 -p 10101 --dir 0 -o trace_vmnic0.pcap\n<\/code><\/pre>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"271\" src=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-4-1024x271.png\" alt=\"\" class=\"wp-image-3857\" srcset=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-4-1024x271.png 1024w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-4-300x79.png 300w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-4-768x203.png 768w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-4.png 1093w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Scenario 2: UDP Performance Test on Windows VMs<\/strong><\/h2>\n\n\n\n<p><strong>Goal: <\/strong>In this test, the goal was to evaluate how different CPU load conditions inside the virtual machines impact UDP packet transmission and reception.<\/p>\n\n\n\n<p>To achieve this, we prepared and tested three distinct sub-scenarios:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>No CPU Load<\/strong>\n<ul class=\"wp-block-list\">\n<li>Both the sending and receiving VMs operated under normal CPU utilization, with no artificial load introduced.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>High CPU Load on the Sending VM<\/strong>\n<ul class=\"wp-block-list\">\n<li>The sending VM was stressed using <a class=\"effect1\" href=\"https:\/\/learn.microsoft.com\/en-us\/sysinternals\/downloads\/cpustres\">Microsoft&#8217;s CpuStres<\/a> tool to simulate a heavy CPU load condition, while the receiving VM remained idle.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>High CPU Load on the Receiving VM<\/strong>\n<ul class=\"wp-block-list\">\n<li>The receiving VM was stressed with high CPU utilization, while the sending VM remained idle.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Method:<\/strong> For each scenario, we generated UDP traffic between the two Windows Server VMs using iPerf3 and simultaneously captured the network traffic at multiple layers:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The virtual switchport of each VM<\/li>\n\n\n\n<li>The physical uplink NICs on both ESXi hosts<\/li>\n\n\n\n<li>The physical switch connecting the hosts<\/li>\n<\/ul>\n\n\n\n<p>All packet captures will be saved and later analyzed in Wireshark to identify any inconsistencies.<\/p>\n\n\n\n<p>Let&#8217;s see now the steps for generating and capturing the traffic.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step one: Start iPerf3 on Windows VMs<\/strong><\/h3>\n\n\n\n<p>Start iPerf3 server and client on Windows VMs to generate UDP traffic:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>iperf3 -s -B 192.168.110.103 -p 10101 --&gt; Server \niperf3 -c 192.168.110.103 -u -b 5M -l 1400 -t 100 -p 10101 --&gt; Client<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step Two: Start pktcap-uw packet capture<\/strong><\/h3>\n\n\n\n<p>Connect to sending host via SSH, find a location on the datastore to save the pcap files and then start the trace on both switchport and vmnic.<\/p>\n\n\n\n<p>It\u2019s not recommended to save files in the \/tmp directory. Ideally, you should identify a VMFS datastore and save your files there instead.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\npktcap-uw --switchport 67108883 --capture VnicTx --dstip 192.168.110.103 --proto 0x11 -o \/vmfs\/volumes\/Datastore\/traces\/esxi0.switchport.67108883.pcapng &amp;  pktcap-uw --uplink vmnic2 --capture UplinkSndKernel --dstip 192.168.110.103 --proto 0x11 -p 10101 -o \/vmfs\/volumes\/Datastore\/traces\/esxi0.uplink.vmnic2.pcapng &amp;<\/code><\/pre>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"423\" src=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-9-1024x423.png\" alt=\"\" class=\"wp-image-3924\" srcset=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-9-1024x423.png 1024w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-9-300x124.png 300w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-9-768x317.png 768w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-9.png 1099w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Connect to the receiving host via SSH, choose a location on a datastore to save the pcap files, and then start packet capture on both the switch port and the vmnic.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>pktcap-uw --switchport 67108882 --capture VnicRx --srcip 192.168.110.101 --proto 0x11 -o \/vmfs\/volumes\/DatastoreESXi2\/traces\/esxi2.switchport.67108882.pcapng &amp; pktcap-uw --uplink vmnic0 --srcip 192.168.110.101 --proto 0x11 -p 10101 -o \/vmfs\/volumes\/DatastoreESXi2\/traces\/esxi2.uplink.vmnic0.pcapng &amp;<\/code><\/pre>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"423\" src=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-10-1024x423.png\" alt=\"\" class=\"wp-image-3925\" srcset=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-10-1024x423.png 1024w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-10-300x124.png 300w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-10-768x317.png 768w, https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/04\/image-10.png 1099w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>To stop pktcap-uw tracing use the kill command: <\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>kill $(lsof | grep pktcap-uw | awk '{print $1}' | sort -u) <\/code><\/pre>\n\n\n\n<p>To be sure that all pktcap-uw traces are stopped, run this command:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>lsof | grep pktcap-uw | awk '{print $1}' | sort -u<\/code><\/pre>\n\n\n\n<p><br>Now that we\u2019ve gathered all the traces from our three scenarios and safely stored the evidence, maybe it\u2019s a good moment to catch our breath.<br>After all, analyzing hundreds of thousands of packets deserves a fresh coffee \u2014 and perhaps a bit of suspense.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What&#8217;s Next<\/strong><\/h2>\n\n\n\n<p>In the next part of this series, we will analyze the captured packet traces in detail using Wireshark, and compare the results across the three CPU load scenarios. We will pinpoint exactly where packet loss occurs and how CPU stress inside VMs affects UDP traffic quality. Stay tuned!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This article is part of the 5-part series: \u201cESXi Packet Loss Troubleshooting with iPerf3 and pktcap-uw\u201d Part 1: Baseline Testing and Setup Part 2: Capturing UDP Traffic Under Different CPU Loads \u2190 You are here Part 3: Analyzing Packet Loss with Wireshark Part 4: UDP Loss from Link Flapping and Network Instability Part 5: Inter-VLAN [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4159,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"_FSMCFIC_featured_image_caption":"","_FSMCFIC_featured_image_nocaption":"","_FSMCFIC_featured_image_hide":"","footnotes":""},"categories":[7,62,15],"tags":[],"class_list":["post-3800","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux","category-network","category-vmware"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.5 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>ESXi Packet Loss Troubleshooting with iPerf3 &amp; pktcap-uw \u2013 Part 2 - IT-REACT<\/title>\n<meta name=\"description\" content=\"Capture UDP traffic in ESXi under different CPU load scenarios using pktcap-uw. Prepare traces for analyzing packet loss and jitter in virtual environments.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"ESXi Packet Loss Troubleshooting with iPerf3 &amp; pktcap-uw \u2013 Part 2 - IT-REACT\" \/>\n<meta property=\"og:description\" content=\"Capture UDP traffic in ESXi under different CPU load scenarios using pktcap-uw. Prepare traces for analyzing packet loss and jitter in virtual environments.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/\" \/>\n<meta property=\"og:site_name\" content=\"IT-REACT\" \/>\n<meta property=\"article:published_time\" content=\"2025-04-27T15:38:50+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-09-19T16:05:32+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/05\/ChatGPT-Image-8.-Mai-2025-15_25_07_edit-e1746719839549.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\n\t<meta property=\"og:image:height\" content=\"570\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Ioan Penu\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ioan Penu\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.it-react.com\\\/index.php\\\/2025\\\/04\\\/27\\\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.it-react.com\\\/index.php\\\/2025\\\/04\\\/27\\\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\\\/\"},\"author\":{\"name\":\"Ioan Penu\",\"@id\":\"https:\\\/\\\/www.it-react.com\\\/#\\\/schema\\\/person\\\/bf08cffeb4b02ee6baff5d56ab17c8f0\"},\"headline\":\"ESXi Packet Loss Troubleshooting with iPerf3 &amp; pktcap-uw \u2013 Part 2\",\"datePublished\":\"2025-04-27T15:38:50+00:00\",\"dateModified\":\"2025-09-19T16:05:32+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.it-react.com\\\/index.php\\\/2025\\\/04\\\/27\\\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\\\/\"},\"wordCount\":1034,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.it-react.com\\\/#\\\/schema\\\/person\\\/bf08cffeb4b02ee6baff5d56ab17c8f0\"},\"image\":{\"@id\":\"https:\\\/\\\/www.it-react.com\\\/index.php\\\/2025\\\/04\\\/27\\\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.it-react.com\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/ChatGPT-Image-8.-Mai-2025-15_25_07_edit-e1746719839549.jpg\",\"articleSection\":[\"Linux\",\"Network\",\"VMWare\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.it-react.com\\\/index.php\\\/2025\\\/04\\\/27\\\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.it-react.com\\\/index.php\\\/2025\\\/04\\\/27\\\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\\\/\",\"url\":\"https:\\\/\\\/www.it-react.com\\\/index.php\\\/2025\\\/04\\\/27\\\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\\\/\",\"name\":\"ESXi Packet Loss Troubleshooting with iPerf3 &amp; pktcap-uw \u2013 Part 2 - IT-REACT\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.it-react.com\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.it-react.com\\\/index.php\\\/2025\\\/04\\\/27\\\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.it-react.com\\\/index.php\\\/2025\\\/04\\\/27\\\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.it-react.com\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/ChatGPT-Image-8.-Mai-2025-15_25_07_edit-e1746719839549.jpg\",\"datePublished\":\"2025-04-27T15:38:50+00:00\",\"dateModified\":\"2025-09-19T16:05:32+00:00\",\"description\":\"Capture UDP traffic in ESXi under different CPU load scenarios using pktcap-uw. Prepare traces for analyzing packet loss and jitter in virtual environments.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.it-react.com\\\/index.php\\\/2025\\\/04\\\/27\\\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.it-react.com\\\/index.php\\\/2025\\\/04\\\/27\\\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.it-react.com\\\/index.php\\\/2025\\\/04\\\/27\\\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.it-react.com\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/ChatGPT-Image-8.-Mai-2025-15_25_07_edit-e1746719839549.jpg\",\"contentUrl\":\"https:\\\/\\\/www.it-react.com\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/ChatGPT-Image-8.-Mai-2025-15_25_07_edit-e1746719839549.jpg\",\"width\":1024,\"height\":570,\"caption\":\"Ioan Penu with ChatGPT\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.it-react.com\\\/index.php\\\/2025\\\/04\\\/27\\\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.it-react.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"ESXi Packet Loss Troubleshooting with iPerf3 &amp; pktcap-uw \u2013 Part 2\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.it-react.com\\\/#website\",\"url\":\"https:\\\/\\\/www.it-react.com\\\/\",\"name\":\"it-react\",\"description\":\"Ctrl\u2022Alt\u2022Automate\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.it-react.com\\\/#\\\/schema\\\/person\\\/bf08cffeb4b02ee6baff5d56ab17c8f0\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.it-react.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/www.it-react.com\\\/#\\\/schema\\\/person\\\/bf08cffeb4b02ee6baff5d56ab17c8f0\",\"name\":\"Ioan Penu\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2a2a1b6be0f322a113eea11669895227e284c6091424d65be6c3c706c2822975?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2a2a1b6be0f322a113eea11669895227e284c6091424d65be6c3c706c2822975?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2a2a1b6be0f322a113eea11669895227e284c6091424d65be6c3c706c2822975?s=96&d=mm&r=g\",\"caption\":\"Ioan Penu\"},\"logo\":{\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2a2a1b6be0f322a113eea11669895227e284c6091424d65be6c3c706c2822975?s=96&d=mm&r=g\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"ESXi Packet Loss Troubleshooting with iPerf3 &amp; pktcap-uw \u2013 Part 2 - IT-REACT","description":"Capture UDP traffic in ESXi under different CPU load scenarios using pktcap-uw. Prepare traces for analyzing packet loss and jitter in virtual environments.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/","og_locale":"en_US","og_type":"article","og_title":"ESXi Packet Loss Troubleshooting with iPerf3 &amp; pktcap-uw \u2013 Part 2 - IT-REACT","og_description":"Capture UDP traffic in ESXi under different CPU load scenarios using pktcap-uw. Prepare traces for analyzing packet loss and jitter in virtual environments.","og_url":"https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/","og_site_name":"IT-REACT","article_published_time":"2025-04-27T15:38:50+00:00","article_modified_time":"2025-09-19T16:05:32+00:00","og_image":[{"width":1024,"height":570,"url":"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/05\/ChatGPT-Image-8.-Mai-2025-15_25_07_edit-e1746719839549.jpg","type":"image\/jpeg"}],"author":"Ioan Penu","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Ioan Penu","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/#article","isPartOf":{"@id":"https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/"},"author":{"name":"Ioan Penu","@id":"https:\/\/www.it-react.com\/#\/schema\/person\/bf08cffeb4b02ee6baff5d56ab17c8f0"},"headline":"ESXi Packet Loss Troubleshooting with iPerf3 &amp; pktcap-uw \u2013 Part 2","datePublished":"2025-04-27T15:38:50+00:00","dateModified":"2025-09-19T16:05:32+00:00","mainEntityOfPage":{"@id":"https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/"},"wordCount":1034,"commentCount":0,"publisher":{"@id":"https:\/\/www.it-react.com\/#\/schema\/person\/bf08cffeb4b02ee6baff5d56ab17c8f0"},"image":{"@id":"https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/#primaryimage"},"thumbnailUrl":"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/05\/ChatGPT-Image-8.-Mai-2025-15_25_07_edit-e1746719839549.jpg","articleSection":["Linux","Network","VMWare"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/","url":"https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/","name":"ESXi Packet Loss Troubleshooting with iPerf3 &amp; pktcap-uw \u2013 Part 2 - IT-REACT","isPartOf":{"@id":"https:\/\/www.it-react.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/#primaryimage"},"image":{"@id":"https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/#primaryimage"},"thumbnailUrl":"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/05\/ChatGPT-Image-8.-Mai-2025-15_25_07_edit-e1746719839549.jpg","datePublished":"2025-04-27T15:38:50+00:00","dateModified":"2025-09-19T16:05:32+00:00","description":"Capture UDP traffic in ESXi under different CPU load scenarios using pktcap-uw. Prepare traces for analyzing packet loss and jitter in virtual environments.","breadcrumb":{"@id":"https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/#primaryimage","url":"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/05\/ChatGPT-Image-8.-Mai-2025-15_25_07_edit-e1746719839549.jpg","contentUrl":"https:\/\/www.it-react.com\/wp-content\/uploads\/2025\/05\/ChatGPT-Image-8.-Mai-2025-15_25_07_edit-e1746719839549.jpg","width":1024,"height":570,"caption":"Ioan Penu with ChatGPT"},{"@type":"BreadcrumbList","@id":"https:\/\/www.it-react.com\/index.php\/2025\/04\/27\/esxi-packet-loss-troubleshooting-with-iperf3-pktcap-uw-part-2\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.it-react.com\/"},{"@type":"ListItem","position":2,"name":"ESXi Packet Loss Troubleshooting with iPerf3 &amp; pktcap-uw \u2013 Part 2"}]},{"@type":"WebSite","@id":"https:\/\/www.it-react.com\/#website","url":"https:\/\/www.it-react.com\/","name":"it-react","description":"Ctrl\u2022Alt\u2022Automate","publisher":{"@id":"https:\/\/www.it-react.com\/#\/schema\/person\/bf08cffeb4b02ee6baff5d56ab17c8f0"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.it-react.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/www.it-react.com\/#\/schema\/person\/bf08cffeb4b02ee6baff5d56ab17c8f0","name":"Ioan Penu","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/2a2a1b6be0f322a113eea11669895227e284c6091424d65be6c3c706c2822975?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/2a2a1b6be0f322a113eea11669895227e284c6091424d65be6c3c706c2822975?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/2a2a1b6be0f322a113eea11669895227e284c6091424d65be6c3c706c2822975?s=96&d=mm&r=g","caption":"Ioan Penu"},"logo":{"@id":"https:\/\/secure.gravatar.com\/avatar\/2a2a1b6be0f322a113eea11669895227e284c6091424d65be6c3c706c2822975?s=96&d=mm&r=g"}}]}},"_links":{"self":[{"href":"https:\/\/www.it-react.com\/index.php\/wp-json\/wp\/v2\/posts\/3800","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.it-react.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.it-react.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.it-react.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.it-react.com\/index.php\/wp-json\/wp\/v2\/comments?post=3800"}],"version-history":[{"count":126,"href":"https:\/\/www.it-react.com\/index.php\/wp-json\/wp\/v2\/posts\/3800\/revisions"}],"predecessor-version":[{"id":4442,"href":"https:\/\/www.it-react.com\/index.php\/wp-json\/wp\/v2\/posts\/3800\/revisions\/4442"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.it-react.com\/index.php\/wp-json\/wp\/v2\/media\/4159"}],"wp:attachment":[{"href":"https:\/\/www.it-react.com\/index.php\/wp-json\/wp\/v2\/media?parent=3800"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.it-react.com\/index.php\/wp-json\/wp\/v2\/categories?post=3800"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.it-react.com\/index.php\/wp-json\/wp\/v2\/tags?post=3800"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}