<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Capturing IEC 60870-5-101 traffic with serial tap]]></title><description><![CDATA[<p dir="auto">I'm trying out my newly purchased serial tap. It works fine and it captures the traffic in a serial line. But the protocol IEC 60870-5-101 is not supported by the IO Ninja software so I can only see Hex information.</p>
<p dir="auto">So I thought of two ways to translate this protocol</p>
<ol>
<li>
<p dir="auto">I have a software that can translate this protocol but it can only listen to com ports. Is there a way to get the serial tap to act like a com port in windows?</p>
</li>
<li>
<p dir="auto">Wireshark can translate this protocol as well. Is there a way to listen to a serial tap in Wireshark? I saw that it was possible to do that with the ethernet tap using pipes.</p>
</li>
</ol>
]]></description><link>http://64.23.185.212/forum/topic/88/capturing-iec-60870-5-101-traffic-with-serial-tap</link><generator>RSS for Node</generator><lastBuildDate>Wed, 13 May 2026 15:28:38 GMT</lastBuildDate><atom:link href="http://64.23.185.212/forum/topic/88.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 16 Mar 2023 18:12:01 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Capturing IEC 60870-5-101 traffic with serial tap on Sun, 19 Mar 2023 12:41:08 GMT]]></title><description><![CDATA[<p dir="auto">If this is a half-duplex link, you can utilize a regular 3rd-party USB-to-Serial adapter from this application of yours that you say can decode 60870-5-101.</p>
<p dir="auto">It's also theoretically possible to post-process an <code>.njlog</code> captured with a Serial Tap and convert it into a <code>.pcap</code> for further analysis in Wireshark. However, it looks like Wireshark can only decode IEC-60870-5-103:</p>
<p dir="auto"><img src="/forum/assets/uploads/files/1679229529590-46768dab-7f64-4da7-9f52-cce87ef2f6f6-image.png" alt="46768dab-7f64-4da7-9f52-cce87ef2f6f6-image.png" class=" img-responsive img-markdown" width="1052" height="670" /></p>
]]></description><link>http://64.23.185.212/forum/post/304</link><guid isPermaLink="true">http://64.23.185.212/forum/post/304</guid><dc:creator><![CDATA[Vladimir]]></dc:creator><pubDate>Sun, 19 Mar 2023 12:41:08 GMT</pubDate></item><item><title><![CDATA[Reply to Capturing IEC 60870-5-101 traffic with serial tap on Fri, 17 Mar 2023 14:45:06 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://64.23.185.212/forum/uid/2">@vladimir</a></p>
<p dir="auto">Half duplex.</p>
<p dir="auto">More information about the protocol:<br />
<a href="https://en.wikipedia.org/wiki/IEC_60870-5" rel="nofollow ugc">https://en.wikipedia.org/wiki/IEC_60870-5</a><br />
<a href="https://www.ensotest.com/iec-60870-5-104/introduction-to-the-iec-60870-5-104-standard/" rel="nofollow ugc">https://www.ensotest.com/iec-60870-5-104/introduction-to-the-iec-60870-5-104-standard/</a></p>
<p dir="auto"><img src="/forum/assets/uploads/files/1679064292713-d1d5d207-e243-424c-ad66-10c39b16f570-image.png" alt="d1d5d207-e243-424c-ad66-10c39b16f570-image.png" class=" img-responsive img-markdown" width="1237" height="1119" /></p>
]]></description><link>http://64.23.185.212/forum/post/301</link><guid isPermaLink="true">http://64.23.185.212/forum/post/301</guid><dc:creator><![CDATA[Andreas Wanzelius]]></dc:creator><pubDate>Fri, 17 Mar 2023 14:45:06 GMT</pubDate></item><item><title><![CDATA[Reply to Capturing IEC 60870-5-101 traffic with serial tap on Fri, 17 Mar 2023 10:55:38 GMT]]></title><description><![CDATA[<p dir="auto">Which is the underlying link you are sniffing with your Serial Tap? Is it half-duplex or full-duplex?</p>
]]></description><link>http://64.23.185.212/forum/post/298</link><guid isPermaLink="true">http://64.23.185.212/forum/post/298</guid><dc:creator><![CDATA[Vladimir]]></dc:creator><pubDate>Fri, 17 Mar 2023 10:55:38 GMT</pubDate></item></channel></rss>