<?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: Ivan 'w1ldy0uth' Shurygin</title>
    <description>The latest articles on DEV Community by Ivan 'w1ldy0uth' Shurygin (@w1ldy0uth).</description>
    <link>https://dev.to/w1ldy0uth</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%2F3956766%2F582e80c2-7f28-4dbd-8744-06620537a3e8.jpeg</url>
      <title>DEV Community: Ivan 'w1ldy0uth' Shurygin</title>
      <link>https://dev.to/w1ldy0uth</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/w1ldy0uth"/>
    <language>en</language>
    <item>
      <title>From a Friend's Suggestion to My First Open-Source Tool</title>
      <dc:creator>Ivan 'w1ldy0uth' Shurygin</dc:creator>
      <pubDate>Thu, 28 May 2026 14:48:00 +0000</pubDate>
      <link>https://dev.to/w1ldy0uth/from-a-friends-suggestion-to-my-first-open-source-tool-3fkg</link>
      <guid>https://dev.to/w1ldy0uth/from-a-friends-suggestion-to-my-first-open-source-tool-3fkg</guid>
      <description>&lt;p&gt;A couple of years ago, a friend of mine — half-joking, half-serious — said: "you should write an ARP scanner, it's a good exercise."&lt;/p&gt;

&lt;p&gt;I had some Python experience, knew vaguely what ARP was, and had nothing better to do that weekend. So I did it. A single &lt;code&gt;arp.py&lt;/code&gt; file using Scapy, broadcasting ARP requests to discover hosts on the local subnet, with a hardcoded /24 CIDR. Rough as it was, it worked — and I felt unreasonably proud of it.&lt;/p&gt;

&lt;p&gt;Then I kept going.&lt;/p&gt;

&lt;h2&gt;
  
  
  The First Burst (2020–2021)
&lt;/h2&gt;

&lt;p&gt;With the ARP scanner done, the next obvious question was: &lt;em&gt;which of these hosts have open ports?&lt;/em&gt; So I added a TCP port scanner — another standalone script, ports hardcoded, scanning consecutively. On a range of 1024 ports with a 3-second timeout each, you'd be waiting a while. I also added a simple ICMP pinger around the same time, again as its own file taking a single IP as argument.&lt;/p&gt;

&lt;p&gt;By the end of this phase I had three separate scripts that didn't really talk to each other. Functional, but not a tool in any meaningful sense.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Gap
&lt;/h2&gt;

&lt;p&gt;Then life happened. The scripts sat untouched for about two years. I'd use them occasionally, patch something when it broke, but there was no real forward motion.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Rework (September 2023)
&lt;/h2&gt;

&lt;p&gt;In September 2023 I decided to take it seriously. The scattered scripts got collapsed into a proper package with a single entrypoint and a CLI argparser. More importantly, I added threading — parallel packet dispatch transformed the port scanner from something painfully slow into something actually usable. You could now set custom timeouts and thread counts from the command line.&lt;/p&gt;

&lt;p&gt;This felt like the project crossing a threshold: from a collection of scripts to something that behaved like a real tool.&lt;/p&gt;

&lt;h2&gt;
  
  
  What sondare does today
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;sondare&lt;/strong&gt; is a Python CLI for auditing local networks, built on Scapy. Here's a quick picture of what it covers:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Scanning:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;sondare arp                               &lt;span class="c"&gt;# discover all hosts on the subnet&lt;/span&gt;
&lt;span class="nb"&gt;sudo &lt;/span&gt;sondare ping                              &lt;span class="c"&gt;# ICMP sweep&lt;/span&gt;
&lt;span class="nb"&gt;sudo &lt;/span&gt;sondare tcp &lt;span class="nt"&gt;--target&lt;/span&gt; 192.168.1.1:1-1024   &lt;span class="c"&gt;# TCP SYN port scan&lt;/span&gt;
&lt;span class="nb"&gt;sudo &lt;/span&gt;sondare udp &lt;span class="nt"&gt;--target&lt;/span&gt; 192.168.1.1:1-1024   &lt;span class="c"&gt;# UDP scan&lt;/span&gt;
&lt;span class="nb"&gt;sudo &lt;/span&gt;sondare os &lt;span class="nt"&gt;--target&lt;/span&gt; 192.168.1.1           &lt;span class="c"&gt;# OS fingerprint&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Monitoring:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;sondare monitor arp                                &lt;span class="c"&gt;# watch for new hosts and MAC address changes&lt;/span&gt;
&lt;span class="nb"&gt;sudo &lt;/span&gt;sondare monitor hosts                              &lt;span class="c"&gt;# live host reachability table&lt;/span&gt;
&lt;span class="nb"&gt;sudo &lt;/span&gt;sondare monitor ports &lt;span class="nt"&gt;--target&lt;/span&gt; 192.168.1.1:1-1024  &lt;span class="c"&gt;# track port state changes&lt;/span&gt;
&lt;span class="nb"&gt;sudo &lt;/span&gt;sondare monitor traffic                            &lt;span class="c"&gt;# live packet capture with protocol breakdown&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Visualisation (the part I'm most proud of):&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;sondare graph &lt;span class="nt"&gt;--fingerprint&lt;/span&gt;   &lt;span class="c"&gt;# interactive HTML network map with OS info&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;graph&lt;/code&gt; command was the last thing I added and probably the most satisfying — it renders an interactive HTML file showing all discovered hosts on your subnet, optionally with OS fingerprint data for each one.&lt;/p&gt;

&lt;h2&gt;
  
  
  What surprised me along the way
&lt;/h2&gt;

&lt;p&gt;A few things I didn't expect:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sequential scanning is deceptively useless.&lt;/strong&gt; My original TCP scanner scanned ports one by one. On a /24 subnet with a modest timeout, that's minutes of waiting for something that should take seconds. Threading wasn't just an optimisation — it was the difference between a tool people would actually use and one they'd run once and forget.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;UDP is genuinely hard.&lt;/strong&gt; With TCP you get a SYN-ACK or a RST — clear signal either way. With UDP, an open port often just says nothing. You can only really distinguish "open" from "open|filtered" based on whether you get a UDP reply back, which most services don't send unless they have something to say. I ended up reporting both states honestly rather than pretending the ambiguity isn't there.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;ARP spoofing detection came almost by accident.&lt;/strong&gt; I added MAC-change monitoring to &lt;code&gt;monitor arp&lt;/code&gt; as a fairly low-effort addition. Then I ran it on a network at a friend's place and it immediately flagged something. Whether it was a misconfigured device or something more interesting, I never found out — but that moment validated the feature more than any design review could.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;If you run a homelab, work in networking, or just want to poke around your local network, give it a go:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;pipx &lt;span class="nb"&gt;install &lt;/span&gt;sondare &lt;span class="nt"&gt;--global&lt;/span&gt;
&lt;span class="nb"&gt;sudo &lt;/span&gt;sondare arp
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It's MIT licensed and the source is on GitHub: &lt;a href="https://github.com/w1ldy0uth/sondare" rel="noopener noreferrer"&gt;github.com/w1ldy0uth/sondare&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I'd genuinely love to hear what's missing, what's broken, or what you'd build on top of it. This started as a friend's offhand suggestion — it'd be nice to see where a community takes it.&lt;/p&gt;

</description>
      <category>network</category>
      <category>python</category>
      <category>security</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
