<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Iot on jfx's site</title><link>https://jfx.ac/tags/iot/</link><description>Recent content in Iot on jfx's site</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 31 Jul 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://jfx.ac/tags/iot/index.xml" rel="self" type="application/rss+xml"/><item><title>Homelab &amp; Mikrotik inspection network</title><link>https://jfx.ac/blog/homelab-mikrotik-inspect-network/</link><pubDate>Wed, 31 Jul 2024 00:00:00 +0000</pubDate><guid>https://jfx.ac/blog/homelab-mikrotik-inspect-network/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;I wanted to reverse engineer the protocols of IoT devices, but it had been a while since I&amp;rsquo;d last traffic inspected a device and I needed to set up something fresh.&lt;/p&gt;
&lt;p&gt;In the past I would&amp;rsquo;ve run Linux on a laptop, spawn an AP, run &lt;code&gt;tcpdump&lt;/code&gt; and call it a day. But I put &lt;em&gt;so much effort&lt;/em&gt; into building a home network with my Mikrotik router and Ubiquiti APs, and have the ability to use VLANs, so I wanted to do something better.&lt;/p&gt;</description></item></channel></rss>