<?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: JackedIN</title>
    <description>The latest articles on DEV Community by JackedIN (@jackedin_app).</description>
    <link>https://dev.to/jackedin_app</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4248049%2F37cdb92f-af03-4ef9-b0a7-354d96283cd4.png</url>
      <title>DEV Community: JackedIN</title>
      <link>https://dev.to/jackedin_app</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jackedin_app"/>
    <language>en</language>
    <item>
      <title>Scripting network console sessions with a local API</title>
      <dc:creator>JackedIN</dc:creator>
      <pubDate>Sun, 22 Nov 2026 00:36:45 +0000</pubDate>
      <link>https://dev.to/jackedin_app/scripting-network-console-sessions-with-a-local-api-16n5</link>
      <guid>https://dev.to/jackedin_app/scripting-network-console-sessions-with-a-local-api-16n5</guid>
      <description>&lt;p&gt;A lot of network work still happens on a console: a USB-serial cable for the first SSH key, a Telnet jump on a lab switch, then a normal SSH session once the box is up. The painful part is not the protocols. It is repeating the same login, pager, and &lt;code&gt;show&lt;/code&gt; command in a window you cannot script.&lt;/p&gt;

&lt;p&gt;This post is about driving those sessions from a command line and from a small local API, using JackedIN, a terminal we build for network gear. Built-in profiles for Junos, Cisco IOS/NX-OS, Arista, Nokia, MikroTik and more. Every download is a full 72-hour trial: the window, the CLI, and the API, with no card and no sign-up.&lt;/p&gt;

&lt;p&gt;If you want short demos and explainers, subscribe to Been There, Built That on YouTube: &lt;a href="https://www.youtube.com/@BeenThere.BuiltThat" rel="noopener noreferrer"&gt;https://www.youtube.com/@BeenThere.BuiltThat&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  One program, three ways in
&lt;/h2&gt;

&lt;p&gt;Run &lt;code&gt;jackedin&lt;/code&gt; with no arguments and you get the desktop window: tabs, saved sessions, serial, SSH, and Telnet. Run it with a command and it stays in the terminal, prints a result, and exits, which is what you want in a script:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;jackedin ports
jackedin connect --serial /dev/ttyUSB0 --baud 9600
jackedin connect --host 192.0.2.10 --user netops
&lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s1"&gt;'show version'&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; jackedin connect --protocol telnet --host 192.0.2.10
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On Windows the serial port looks like &lt;code&gt;COM5&lt;/code&gt;. Use a device you own or are allowed to manage, and keep secrets out of the command line. JackedIN can take an enable secret from an environment variable instead of argv.&lt;/p&gt;

&lt;p&gt;The same engine is also a local automation API. It is off by default, listens only on the local machine, and needs a token. You turn it on when you want scripts on that computer to open a session, send a command, wait for output, and close it, or to run ping, traceroute, and a port scan against gear you are allowed to test.&lt;/p&gt;

&lt;h2&gt;
  
  
  See the plan before you touch the device
&lt;/h2&gt;

&lt;p&gt;Dry-run is the habit that keeps a typo from becoming a change window. Nothing connects and no password is sent:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;jackedin &lt;span class="nb"&gt;exec&lt;/span&gt; --host 192.0.2.10 --dry-run --cmd &lt;span class="s1"&gt;'show version'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If the output looks right, drop &lt;code&gt;--dry-run&lt;/code&gt; and run it for real. You can also pass expect rules so a run fails when the output is wrong, not only when the connection drops.&lt;/p&gt;

&lt;h2&gt;
  
  
  Python on the same computer
&lt;/h2&gt;

&lt;p&gt;The Python client and the optional Nornir plugin are free on PyPI, but they drive the JackedIN app, so you still need the trial or a license on that machine:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pip install jackedin
&lt;span class="c"&gt;# optional&lt;/span&gt;
pip install nornir-jackedin
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;jackedin&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;Jackedin&lt;/span&gt;

&lt;span class="n"&gt;device&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;Jackedin&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"192.0.2.10"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;username&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"netops"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;  &lt;span class="c1"&gt;# password from JACKEDIN_PASSWORD&lt;/span&gt;
&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;device&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;dry_run&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"show version"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;text&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;report&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;device&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;run&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"show version"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;expect&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s2"&gt;"command"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"show version"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"expect_match"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Version"&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;report&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That is enough to hang a lab check off a script: confirm a version string, grab a show command, or fail a job when the prompt is not what you expected. There is also a Nornir task if you already keep inventory that way, and an Ansible collection in the portable zip.&lt;/p&gt;

&lt;h2&gt;
  
  
  A few practical notes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;JackedIN 1.2.1 runs on Windows 10/11, Debian/Ubuntu, and Raspberry Pi OS 64-bit. There is no macOS build yet.&lt;/li&gt;
&lt;li&gt;Import works from PuTTY, SecureCRT, MobaXterm, and SSH config, which is useful when you are moving an existing session list rather than starting over.&lt;/li&gt;
&lt;li&gt;SFTP file transfer is included.&lt;/li&gt;
&lt;li&gt;The local API stays on the same machine. Do not treat it as a network service to open up.&lt;/li&gt;
&lt;li&gt;1.2.1 fixes serial consoles that only prompt &lt;code&gt;Password:&lt;/code&gt; and the &lt;code&gt;enable&lt;/code&gt; prompt on the console, which is the exact mess a first-boot script runs into.&lt;/li&gt;
&lt;li&gt;The Windows installer is not code-signed yet, so SmartScreen may say "Windows protected your PC." The portable zip does not need admin rights.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The trial, the user's guide, and the current 1.2.1 downloads are at &lt;a href="https://getjackedin.com" rel="noopener noreferrer"&gt;https://getjackedin.com&lt;/a&gt;. After the 72-hour trial, the launch price is $19 one-time (regular $29). There is also a Lab Bundle with PathProbe Pro for $24.99: &lt;a href="https://getpathprobe.com/bundle/" rel="noopener noreferrer"&gt;https://getpathprobe.com/bundle/&lt;/a&gt;. Students, teachers, and CTF teams can email &lt;a href="mailto:service@getpathprobe.com"&gt;service@getpathprobe.com&lt;/a&gt; for a 40% off code. If you already live in a terminal, start with the CLI. If you already live in Python, start with &lt;code&gt;pip install jackedin&lt;/code&gt; and a dry-run against a lab address.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: we build JackedIN. This post describes the current 1.2.1 app and the 1.2.0 Python packages, which work together.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>networking</category>
      <category>python</category>
      <category>automation</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Testing DHCP on tagged VLANs from a Raspberry Pi</title>
      <dc:creator>JackedIN</dc:creator>
      <pubDate>Sun, 22 Nov 2026 00:35:51 +0000</pubDate>
      <link>https://dev.to/jackedin_app/testing-dhcp-on-tagged-vlans-from-a-raspberry-pi-3n8e</link>
      <guid>https://dev.to/jackedin_app/testing-dhcp-on-tagged-vlans-from-a-raspberry-pi-3n8e</guid>
      <description>&lt;p&gt;A trunk port can look fine and still hand the wrong VLAN a DHCP lease. The usual check is to re-cable a laptop and add a temporary VLAN interface. A Raspberry Pi on the bench is a better test client: small, wired, and easy to leave on the switch port while you watch the offer.&lt;/p&gt;

&lt;p&gt;This post uses PathProbe, a command-line DHCP and VLAN tester we build, on Raspberry Pi OS 64-bit. The Free tier covers everything here except the optional QinQ example at the end. Use it only on a network you own or are authorized to test. &lt;code&gt;pathprobe dhcp run&lt;/code&gt; will not start without &lt;code&gt;--authorized&lt;/code&gt; (or &lt;code&gt;--i-am-authorized&lt;/code&gt;).&lt;/p&gt;

&lt;p&gt;If you want short demos and explainers, subscribe to Been There, Built That on YouTube: &lt;a href="https://www.youtube.com/@BeenThere.BuiltThat" rel="noopener noreferrer"&gt;https://www.youtube.com/@BeenThere.BuiltThat&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What you are proving
&lt;/h2&gt;

&lt;p&gt;First, an untagged DHCP client on the port should get a lease from the VLAN you expect for untagged traffic. Second, a client that sends an 802.1Q tag for VLAN 100 (or whichever ID you are allowed to test) should get a lease from &lt;em&gt;that&lt;/em&gt; VLAN, not the untagged one. If the first test works and the second fails, the port, the trunk, or the DHCP helper is not doing what the switch config claims.&lt;/p&gt;

&lt;h2&gt;
  
  
  Set up the Pi
&lt;/h2&gt;

&lt;p&gt;Install the current arm64 package from &lt;a href="https://getpathprobe.com" rel="noopener noreferrer"&gt;getpathprobe.com&lt;/a&gt;. The live download at the time of writing is PathProbe 1.2.1:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo apt install ./pathprobe_1.2.1_arm64.deb
pathprobe interfaces
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Plug the Pi into the switch port under test. On a trunk, an untagged client and a tagged client should see different broadcast domains. Use a port you are allowed to test, and do not try to exhaust someone else's DHCP pool.&lt;/p&gt;

&lt;h2&gt;
  
  
  Untagged first
&lt;/h2&gt;

&lt;p&gt;Start with one client, a short run, and a capture you can open later in Wireshark:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo pathprobe dhcp run --iface eth0 --count 1 --family v4 \
  --duration 30s --capture lab-untagged.pcapng --authorized
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You should see a bind, an address in the range you expect (the examples in our docs use &lt;code&gt;192.0.2.x&lt;/code&gt;), and a pcapng in the current directory. If this already fails, fix the access VLAN, the helper address, or the pool before you start tagging.&lt;/p&gt;

&lt;h2&gt;
  
  
  Then send a tag
&lt;/h2&gt;

&lt;p&gt;On Free, PathProbe can send a single 802.1Q tag. &lt;code&gt;--vlan-seed&lt;/code&gt; is the VLAN ID. Change &lt;code&gt;100&lt;/code&gt; to the VLAN you are actually allowed to test. The MAC below is a documentation address, not a real adapter:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo pathprobe dhcp run --iface eth0 --count 1 --family v4 \
  --vlan single --vlan-seed 100 --duration 30s \
  --mac-seed 02:00:00:00:00:30 \
  --capture lab-vlan100.pcapng --authorized
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If the untagged test worked and this one does not, the port is not passing VLAN 100 the way you think it is. That is the useful result. In the two pcapng files, look for a DISCOVER with a VLAN tag, an OFFER from the right pool, and an ACK. PathProbe writes the capture; you read it in Wireshark or tcpdump.&lt;/p&gt;

&lt;p&gt;You can also start with five clients, which is the Free-tier limit:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo pathprobe dhcp run --iface eth0 --count 5 --vlan single \
  --vlan-seed 100 --authorized
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Optional: stacked tags
&lt;/h2&gt;

&lt;p&gt;QinQ (&lt;code&gt;--vlan qinq&lt;/code&gt;) is a Pro feature. On Free the command tells you that and exits:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo pathprobe dhcp run --iface eth0 --count 1 --family v4 \
  --vlan qinq --svlan-seed 200 --vlan-seed 100 --duration 30s --authorized
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;--svlan-seed&lt;/code&gt; is the outer tag; &lt;code&gt;--vlan-seed&lt;/code&gt; is the inner tag. The switch has to be set up for the stacked-tag mode you are testing.&lt;/p&gt;

&lt;h2&gt;
  
  
  A few rules that save pain
&lt;/h2&gt;

&lt;p&gt;Only test networks you own or are allowed to test, and do not publish screenshots or captures that show real IPs, MACs, hostnames, or usernames. PathProbe 1.2.1 can write a scrubbed copy of a run log with &lt;code&gt;pathprobe log share&lt;/code&gt; if you need to ask for help. Windows works too (it needs Npcap). There is no macOS build yet, and PathProbe is command-line only.&lt;/p&gt;

&lt;p&gt;The Free download, checksums, and the current feature split are at &lt;a href="https://getpathprobe.com" rel="noopener noreferrer"&gt;https://getpathprobe.com&lt;/a&gt;. Free never expires (up to 5 clients and a single 802.1Q tag). Pro is $9.99 one-time. There is also a Lab Bundle with JackedIN for $24.99: &lt;a href="https://getpathprobe.com/bundle/" rel="noopener noreferrer"&gt;https://getpathprobe.com/bundle/&lt;/a&gt;. Students, teachers, and CTF teams can email &lt;a href="mailto:service@getpathprobe.com"&gt;service@getpathprobe.com&lt;/a&gt; for a 40% off code. If a tagged offer ever surprises you, the capture is the evidence, not the switch port LED.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: we build PathProbe. The Free tier covers the untagged and single-tag examples in this post.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>networking</category>
      <category>raspberrypi</category>
      <category>homelab</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
