New in the Community? Get started here

Schneider Electric Exchange Community

Discuss and solve problems in energy management and automation. Join conversations and share insights on products and solutions. Co-innovate and collaborate with a global network of peers.

Register Now
Knowledge Base
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

- Discover the Exchange Community Top members of October here!

- Check out the ESS Active Energy Management Blog now! 

- Watch now the replay of The Power of a Sustainable Ecosystem panel with Hervé Coureil and other experts 

How to capture localhost traffic with Wireshark to help troubleshoot EWS communication issues.

Issue

When the EWS is installed on the same machine using the service then all packets will be going to the localhost and will not hit the NIC so will not be captured in a Wireshark packet capture.

Product Line

EcoStruxure Building Operation, Security Expert

Environment

  • Security Expert
  • EBO

Cause

Packets sent between services on the same machine (like SOAP and EWS) do not hit the NIC and therefore cannot be captured with the default configuration of Wireshark using the WinPcap packet sniffing library. 

Resolution

Replace WinPcap with Npcap to emulate a loopback NIC for packet capture.

  1. Go to https://nmap.org/npcap/ for details on the library.
  2. Download the library installer from https://nmap.org/npcap/#download
  3. Uninstall WinPcap.
  4. Install Npcap.
  5. Npcap will create an adapter named Npcap Loopback Adapter for you. In Wireshark choose this adapter to capture, you will see all loopback traffic the same way as other non-loopback adapters.
  6. You can test this out by typing in commands like "ping 127.0.0.1" (IPv4)  or "ping ::1" (IPv6).
Tags (1)
No ratings