<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Wireshark on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/wireshark/</link>
    <description>Recent content in Wireshark on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 27 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/wireshark/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Your Android Bluetooth Traffic Captures Should Be Live</title>
      <link>https://insinuator.net/2026/07/your-android-bluetooth-traffic-captures-should-be-live/</link>
      <pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/07/your-android-bluetooth-traffic-captures-should-be-live/</guid>
      <description>&lt;p&gt;In this post I want to talk about a very essential part of my workflow when dealing with Bluetooth devices, particularly IoT devices with a corresponding mobile app: Live capture of Android Bluetooth traffic with Wireshark.&lt;/p&gt;&#xA;&lt;p&gt;Before you stop reading because you think you know how to do this already, the method does not involve pulling bug reports off your phone, and it does not require root. And most importantly it gives you a &lt;strong&gt;live&lt;/strong&gt; packet log in Wireshark.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Troopers 16: Wireshark in IP version 6</title>
      <link>https://insinuator.net/2016/03/troopers-16-wireshark-in-ip-version-6/</link>
      <pubDate>Tue, 29 Mar 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/03/troopers-16-wireshark-in-ip-version-6/</guid>
      <description>&lt;p&gt;Wireshark in IP version 6 workshop was a part of IPv6 summit sessions of Troopers 16. It was held by Jeffery Carrell on the second day of IPv6 summit on Tuesday, the 15th of March.  The workshop was generally divided into two sections: a short introduction to IPv6 and analyzing some IPv6 packets on Wireshark.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Introduction to IPv6&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;IPv6 protocol was defined at the end of 1990’s, mainly to provide a huge address pool after realizing that the world would run out of IPv4 addresses quickly. The work on IPv6 started before the introduction of NAT and Private addressing to IPv4, which are considered temporary solutions of IPv4 address shortage problem. IPv6 address consists of 128 bits, divided into 8 groups called &lt;em&gt;nibbles&lt;/em&gt;, &lt;em&gt;quibbles&lt;/em&gt; or &lt;em&gt;hextets&lt;/em&gt; separated by colons. Each nibble consists of four hexadecimal digits. The 128 bits address length provides 340 trillion trillion trillion addresses. An IPv6 address is divided into two parts: the left part is the network identifier while the right one is the host identifier. The default prefix is /64 which divided the IP address into two halves. An IPv6 address looks as follows: 2001:0db8:1010:61ab:f005:ba11:00da:11a5/64&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
