<?xml version='1.0' encoding='utf-8' ?>
<!-- Made with love by pretalx v2025.2.2. -->
<schedule>
    <generator name="pretalx" version="2025.2.2" />
    <version>2026-03-28</version>
    <conference>
        <title>SharkFest&apos;26 US</title>
        <acronym>sf26us</acronym>
        <start>2026-07-18</start>
        <end>2026-07-23</end>
        <days>6</days>
        <timeslot_duration>00:05</timeslot_duration>
        <base_url>https://conference.wireshark.org</base_url>
        <logo>https://conference.wireshark.org/media/sharkfest-25-us/img/sf_logo_big_Xf7UCdI.png</logo>
        <time_zone_name>CST6CDT</time_zone_name>
        
        
        <track name="Beginner" slug="30-beginner"  color="#00ab9b" />
        
        <track name="Intermediate" slug="31-intermediate"  color="#2b9ecf" />
        
        <track name="Expert / Developer" slug="32-expert-developer"  color="#9d6dec" />
        
        <track name="Security" slug="33-security"  color="#72b406" />
        
        <track name="A.I." slug="34-ai"  color="#e60757" />
        
        <track name="Pre-conference class" slug="35-pre-conference-class"  color="#0c590d" />
        
        <track name="Organization" slug="36-organization"  color="#3c8bc4" />
        
    </conference>
    <day index='1' date='2026-07-18' start='2026-07-18T04:00:00-05:00' end='2026-07-19T03:59:00-05:00'>
        <room name='Room 1' guid='91d4d02b-7495-5eb4-946a-6a24e4f87481'>
            <event guid='415214cc-a53e-527d-a081-f1edb959abff' id='189'>
                <room>Room 1</room>
                <title>Pre-Conference Class I: Practical Wireshark Skills for IT professionals</title>
                <subtitle></subtitle>
                <type>Pre Conference Class</type>
                <date>2026-07-18T09:00:00-05:00</date>
                <start>09:00</start>
                <duration>08:00</duration>
                <abstract>**Hands on Wireshark Lab and Wireshark Certified Analyst Prep**

Practical Wireshark Troubleshooting is a two-day, hands-on course designed to strengthen your packet analysis and troubleshooting skills. On Day 1, Ross Bagurdes guides you through Wireshark&#8217;s key features, capture methods, filtering techniques, and foundational protocols at the Data Link and Network layers. On Day 2, Chris Greer takes you deeper into Transport and Application layer analysis, focusing on TCP, UDP, and the tools that uncover real-world performance problems. By the end, you&#8217;ll know how to approach network issues with confidence &#8212; and be better prepared for the Wireshark Certified Analyst exam.</abstract>
                <slug>sf26us-189-0-pre-conference-class-i-practical-wireshark-skills-for-it-professionals</slug>
                <track>Pre-conference class</track>
                
                <persons>
                    <person id='138'>Ross Bagurdes</person><person id='8'>Chris Greer</person>
                </persons>
                <language>en</language>
                <description>Level up your Wireshark skills and get ready for Sharkfest! This hands-on course will provide core Wireshark skills for IT pros of all experience levels. Participants will gain a solid understanding of how to use Wireshark to capture, analyze, and troubleshoot network traffic. The course is designed with beginners in mind, but even seasoned packet people will pick up new tips and tricks.</description>
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/BSA8P7/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/BSA8P7/feedback/</feedback_url>
            </event>
            
        </room>
        
    </day>
    <day index='2' date='2026-07-19' start='2026-07-19T04:00:00-05:00' end='2026-07-20T03:59:00-05:00'>
        <room name='Room 1' guid='91d4d02b-7495-5eb4-946a-6a24e4f87481'>
            <event guid='987f7bf9-4da2-56f6-b74c-10bd081e2627' id='189'>
                <room>Room 1</room>
                <title>Pre-Conference Class I: Practical Wireshark Skills for IT professionals</title>
                <subtitle></subtitle>
                <type>Pre Conference Class</type>
                <date>2026-07-19T09:00:00-05:00</date>
                <start>09:00</start>
                <duration>08:00</duration>
                <abstract>**Hands on Wireshark Lab and Wireshark Certified Analyst Prep**

Practical Wireshark Troubleshooting is a two-day, hands-on course designed to strengthen your packet analysis and troubleshooting skills. On Day 1, Ross Bagurdes guides you through Wireshark&#8217;s key features, capture methods, filtering techniques, and foundational protocols at the Data Link and Network layers. On Day 2, Chris Greer takes you deeper into Transport and Application layer analysis, focusing on TCP, UDP, and the tools that uncover real-world performance problems. By the end, you&#8217;ll know how to approach network issues with confidence &#8212; and be better prepared for the Wireshark Certified Analyst exam.</abstract>
                <slug>sf26us-189-1-pre-conference-class-i-practical-wireshark-skills-for-it-professionals</slug>
                <track>Pre-conference class</track>
                
                <persons>
                    <person id='138'>Ross Bagurdes</person><person id='8'>Chris Greer</person>
                </persons>
                <language>en</language>
                <description>Level up your Wireshark skills and get ready for Sharkfest! This hands-on course will provide core Wireshark skills for IT pros of all experience levels. Participants will gain a solid understanding of how to use Wireshark to capture, analyze, and troubleshoot network traffic. The course is designed with beginners in mind, but even seasoned packet people will pick up new tips and tricks.</description>
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/BSA8P7/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/BSA8P7/feedback/</feedback_url>
            </event>
            
        </room>
        
    </day>
    <day index='3' date='2026-07-20' start='2026-07-20T04:00:00-05:00' end='2026-07-21T03:59:00-05:00'>
        <room name='Room 1' guid='91d4d02b-7495-5eb4-946a-6a24e4f87481'>
            <event guid='902e8e03-54cc-5233-a277-e18dee25ec41' id='190'>
                <room>Room 1</room>
                <title>Pre-Conference Class II: Introduction to Stratoshark for Network Engineers</title>
                <subtitle></subtitle>
                <type>Pre Conference Class</type>
                <date>2026-07-20T09:00:00-05:00</date>
                <start>09:00</start>
                <duration>08:00</duration>
                <abstract>Stratoshark brings Wireshark-style visibility to the Linux system, letting you see what&apos;s happening inside the OS alongside the network traffic it generates. In this hands-on workshop, you&apos;ll learn to use sysdig and Stratoshark to trace system calls, correlate them with packet data, and answer questions that packets alone can&apos;t &#8212; like which process handled a connection or how a service behaved under load. Designed for network engineers ready to go one level deeper, the session blends short lectures with guided exercises using cloud-based lab systems. You&apos;ll leave with a working understanding of Stratoshark and the confidence to begin using it in your own analysis.</abstract>
                <slug>sf26us-190-pre-conference-class-ii-introduction-to-stratoshark-for-network-engineers</slug>
                <track>Pre-conference class</track>
                
                <persons>
                    <person id='6'>Josh Clark</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/A3PJVZ/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/A3PJVZ/feedback/</feedback_url>
            </event>
            <event guid='8cb11da3-b08e-5883-b105-779c7b2e0846' id='186'>
                <room>Room 1</room>
                <title>SharkFest&apos;26 US Welcome Dinner &amp; Sponsor Showcase</title>
                <subtitle></subtitle>
                <type>Dinner</type>
                <date>2026-07-20T17:30:00-05:00</date>
                <start>17:30</start>
                <duration>03:00</duration>
                <abstract>Let&apos;s kick-off the conference in style!</abstract>
                <slug>sf26us-186-sharkfest-26-us-welcome-dinner-sponsor-showcase</slug>
                <track>Organization</track>
                
                <persons>
                    
                </persons>
                <language>en</language>
                <description>SharkFest&apos;26 US Welcome Dinner &amp; Sponsor Showcase</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/X73HTY/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/X73HTY/feedback/</feedback_url>
            </event>
            
        </room>
        
    </day>
    <day index='4' date='2026-07-21' start='2026-07-21T04:00:00-05:00' end='2026-07-22T03:59:00-05:00'>
        <room name='Room 1' guid='91d4d02b-7495-5eb4-946a-6a24e4f87481'>
            <event guid='cd3b8e9e-70c9-5f81-94f0-d16f227fc097' id='191'>
                <room>Room 1</room>
                <title>Things I Love About Wireshark (and maybe a couple of things I don&apos;t)</title>
                <subtitle></subtitle>
                <type>Organization</type>
                <date>2026-07-21T09:00:00-05:00</date>
                <start>09:00</start>
                <duration>01:00</duration>
                <abstract>Gerald Combs &amp; Friends talk about the new developments over the past year</abstract>
                <slug>sf26us-191-things-i-love-about-wireshark-and-maybe-a-couple-of-things-i-don-t</slug>
                <track>Organization</track>
                
                <persons>
                    
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/H89ETP/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/H89ETP/feedback/</feedback_url>
            </event>
            <event guid='e75788b9-ac20-595b-bcd7-9fe22a5b1abb' id='165'>
                <room>Room 1</room>
                <title>Don&#8217;t blame the network &#8211; ask the network!</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-21T10:15:00-05:00</date>
                <start>10:15</start>
                <duration>01:00</duration>
                <abstract>When systems have problems often times engineers say it is a network problem&#8230; and they&#8217;ll say this without any actual data pointing the finger at the network. Sometimes it is a blamestorming session &#8211; database group is blaming the network, network is blaming the software, software is blaming the hardware speed, and hardware is blaming the database.

When this happens, the best thing to do is kick everyone out of the room, sniff the data, and see where/what the bottleneck is. More often than not it isn&#8217;t one particular thing but the interactions between two endpoints that just don&#8217;t completely like each other. Identifying that is the first step in getting the right groups talking to each other and resolving the root of the issue.

In this talk I&#8217;ll setup N real world scenarios, describe the problem, show the captured data and how if you ask the capture in the right way how the problem will reveal itself.</abstract>
                <slug>sf26us-165-don-t-blame-the-network-ask-the-network</slug>
                <track>Intermediate</track>
                <logo>/media/sharkfest-25-us/submissions/M8KMKW/Teaser_K1luPWE.PNG</logo>
                <persons>
                    <person id='125'>David Soussan</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/M8KMKW/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/M8KMKW/feedback/</feedback_url>
            </event>
            <event guid='eab92e08-0569-5657-a547-f0b20135ed59' id='169'>
                <room>Room 1</room>
                <title>Lessons learned in troubleshooting</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-21T11:30:00-05:00</date>
                <start>11:30</start>
                <duration>01:00</duration>
                <abstract>**Lessons learned in troubleshooting Westpac Bank application issues using Wireshark**

Westpac bank in Australia has a vast number of applications that traverse our network and interact with multiple network components.  It is not uncommon to have intermittent failures that involve interactions with F5 load balancers and firewalls, subtle TLS handshake failures, unsuitable TCP configuration settings, VOIP application dropouts, international (MQSeries based) messaging performance issues and communication channel drops, poorly performing &amp; failed file transfer failures etc. We will show how Wireshark helped locate root cause or prove &quot;it&apos;s not the network&quot;.</abstract>
                <slug>sf26us-169-lessons-learned-in-troubleshooting</slug>
                <track>Intermediate</track>
                <logo>/media/sharkfest-25-us/submissions/PKFXEY/WestpacPresentationWireshark_NHfwrUx.png</logo>
                <persons>
                    <person id='128'>Kevin Tobin</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/PKFXEY/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/PKFXEY/feedback/</feedback_url>
            </event>
            <event guid='80ecd092-3c9d-5377-b2db-c105f5effbdf' id='166'>
                <room>Room 1</room>
                <title>Lost In Transmission</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-21T13:30:00-05:00</date>
                <start>13:30</start>
                <duration>01:00</duration>
                <abstract>Finding and counting packet losts in each layer</abstract>
                <slug>sf26us-166-lost-in-transmission</slug>
                <track>Intermediate</track>
                
                <persons>
                    <person id='12'>Megumi Takeshita</person>
                </persons>
                <language>en</language>
                <description>Packets lost occur in many situations, showing the shape in various layers.
Differences in the number of packets between the passive start tap. (layer1,2)
The same IPID and a different offset as disappearance in the packet buffer in the router processing
Retransmission of TCP segments as a result of a traffic jam.
UDP application works with packet loss.

In this session, you can learn the major case of packet loss and you can find the way to find and count packet loss and retransmissions. Megumi shares the best way to understand invisible packet losses with Wireshark!</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/SAY8D9/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/SAY8D9/feedback/</feedback_url>
            </event>
            <event guid='fa62fd63-e2a1-5f58-a5b2-4ace8e77a8f6' id='196'>
                <room>Room 1</room>
                <title>Wireshark: The Prequel - What to do BEFORE you look at a capture</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-21T14:45:00-05:00</date>
                <start>14:45</start>
                <duration>01:00</duration>
                <abstract>&quot;Something is wrong with the network. I used to get 4Gbps transfers but now I&apos;m only getting 120Mbps. Did you change something recently?&quot;

Sound familiar? If you&apos;ve spent any time supporting production systems, you&apos;ve probably heard some variation of this complaint. Before jumping to conclusions about where the problem lies, we need to understand what&apos;s actually happening at the TCP layer on both endpoints.</abstract>
                <slug>sf26us-196-wireshark-the-prequel-what-to-do-before-you-look-at-a-capture</slug>
                <track>Intermediate</track>
                
                <persons>
                    <person id='139'>Rob MacDonald</person>
                </persons>
                <language>en</language>
                <description>This presentation is inspired by a series of articles I wrote on LinkedIn focused on practical, real world troubleshooting of application network performance issues.  Instead of deep diving in to packet captures, this presentation will highlight the various tools and metrics available on Linux systems that help engineers and administrators pinpoint the true source(s) of application performance problems when &quot;the network&quot; is blamed.  

We will focus on how packets are processed in a Linux system from the NIC, through the OS, up to the application.  We will then take a closer look at TCP itself, utilizing native Linux tooling to introspect on individual TCP socket performance.  This TCP socket introspection will dive in to each socket&apos;s calculated network latency (RTT), packet sizing (MTU and MSS), and packet loss (retransmissions, SACK, duplicate ACKs</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/XPYXAB/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/XPYXAB/feedback/</feedback_url>
            </event>
            <event guid='eceaf760-f10c-5370-bcef-000937dd35b2' id='197'>
                <room>Room 1</room>
                <title>Feeding Frenzy of Wild Ideas: When Sharks Brainstorm</title>
                <subtitle></subtitle>
                <type>Organization</type>
                <date>2026-07-21T16:00:00-05:00</date>
                <start>16:00</start>
                <duration>01:00</duration>
                <abstract>Innovation doesn&#8217;t always start with a perfectly reasonable idea&#8212;sometimes it starts with something gloriously absurd. This session invites both developers and users to surface their most unconventional, impractical, or outright bizarre ideas for Wireshark and packet analysis. Nothing is too silly, too quirky, or too infeasible to share.

By creating a space free of judgment and full of curiosity, we open the door to unexpected breakthroughs. 99 wild suggestions may go nowhere&#8230; but the 100th can trigger a spark that becomes a feature, a tool, or even a whole new product direction.
Join us for an hour where creativity takes the wheel, seriousness stays at the shore, and every idea&#8212;no matter how ridiculous&#8212;gets its moment in the water.</abstract>
                <slug>sf26us-197-feeding-frenzy-of-wild-ideas-when-sharks-brainstorm</slug>
                <track>Beginner</track>
                <logo>/media/sf26us/submissions/FYWGV9/shark_waci_j4GEXty.png</logo>
                <persons>
                    
                </persons>
                <language>en</language>
                <description>*Goal:*
Generate offbeat, humorous, impossible or &#8220;why would anyone even&#8230;&#8221; suggestions that just might reveal a surprisingly valuable insight for Wireshark&#8217;s future capabilities.

*Format:*
* Why absurd ideas matter.
* Warm Up
* Open SharkTank
* The &#8216;Maybe&#8230;&#8217; scan

*Ground Rules:*
* All ideas are welcome.
* No shooting down concepts&#8212;only building on them.
* Humor encouraged; feasibility optional.
* The wilder, the better.

*Who Should Attend:*
Anyone who uses Wireshark, contributes to it, builds tooling around it, or likes thinking sideways. No technical depth required&#8212;just curiosity and a willingness to have fun.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/FYWGV9/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/FYWGV9/feedback/</feedback_url>
            </event>
            <event guid='2e6a4435-1f25-5e6f-91a7-329d982f6ac4' id='199'>
                <room>Room 1</room>
                <title>Packets in the Power Grid: A Journey Inside the Substation</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-21T17:15:00-05:00</date>
                <start>17:15</start>
                <duration>01:00</duration>
                <abstract>Ever wondered what really happens inside a power substation during everyday operations? In this session, we&#8217;ll take a dynamic &#8220;flyover&#8221; of a small-to-medium-sized substation, exploring critical points where power and data intersect and uncovering the interactions that keep the power system stable and responsive.

We&#8217;ll look at how these elements work together to keep the lights on&#8212;and how their digital nervous system communicates in real time. 

To bring it all together, we&#8217;ll walk through a real-world power system event, following the flow of communication from the initial fault detection all the way to the control center&#8217;s response and back to the field. Along the way, we&#8217;ll decode how these messages orchestrate recovery and maintain reliability. Whether you&#8217;re a packet sleuth or a power systems enthusiast, this session gives you a front-row seat to the intersection of operational technology and network analysis.</abstract>
                <slug>sf26us-199-packets-in-the-power-grid-a-journey-inside-the-substation</slug>
                <track>Beginner</track>
                <logo>/media/sf26us/submissions/LRBBM8/Packets_in_the_Power_Grid_Lopez_Session_Image_tfk_TO2yCQv.webp</logo>
                <persons>
                    <person id='90'>Daniel Lopez</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/LRBBM8/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/LRBBM8/feedback/</feedback_url>
            </event>
            <event guid='e65ddf83-bd86-5982-b329-45566f710965' id='187'>
                <room>Room 1</room>
                <title>Sponsor Technology Showcase Reception and Dinner</title>
                <subtitle></subtitle>
                <type>Dinner</type>
                <date>2026-07-21T18:30:00-05:00</date>
                <start>18:30</start>
                <duration>03:00</duration>
                <abstract>Sponsor Showcase and dinner</abstract>
                <slug>sf26us-187-sponsor-technology-showcase-reception-and-dinner</slug>
                <track>Organization</track>
                
                <persons>
                    
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/WNWRRU/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/WNWRRU/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Room 2' guid='a25c3679-1842-5652-94a2-5218804e6fd8'>
            <event guid='b1f84748-76a6-5759-929d-44dd659a0b44' id='201'>
                <room>Room 2</room>
                <title>MAC Privacy Protocol Wireshark Plugin</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-21T13:30:00-05:00</date>
                <start>13:30</start>
                <duration>01:00</duration>
                <abstract>Engineers at Pacific Northwest National Laboratory (PNNL) have been working to add support for MAC Privacy Protection protocol (IEEE 802.1AEdk) to the Linux kernel. MAC Privacy is a Layer 2 protocol intended primarily for use with MAC Security (IEEE 802.1AE) which can modify network traffic metadata including source and destination addresses, timing, and volume. Engineers decided early that having the ability to dissect this new network protocol in Wireshark would not only aid development and testing but also eventually be expected by the community. In this talk, engineers at PNNL present a new Wireshark dissector plugin for handling MAC Privacy protocol. They cover the plugin and its features as well as the pros and cons of developing a Wireshark plugin in Rust.</abstract>
                <slug>sf26us-201-mac-privacy-protocol-wireshark-plugin</slug>
                <track>Expert / Developer</track>
                
                <persons>
                    <person id='142'>Cameron Smith</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/PDJYJ9/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/PDJYJ9/feedback/</feedback_url>
            </event>
            <event guid='d7f5423b-15ae-54ae-838e-9fcac84f5909' id='202'>
                <room>Room 2</room>
                <title>Understanding LTE &amp; 5G: 3GPP Packet Flow and Network Analysis</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-21T14:45:00-05:00</date>
                <start>14:45</start>
                <duration>01:00</duration>
                <abstract>we&apos;ll walk through how a device connects to an LTE network, from initial access to an active data session, and examined the packet flows that make that connection possible. We also look at how 3GPP protocols structure this communication and how tunneling is used to carry traffic across the network. Providing a clearer understanding of how LTE networks operate and explore similar concepts as they evolve into 5G.</abstract>
                <slug>sf26us-202-understanding-lte-5g-3gpp-packet-flow-and-network-analysis</slug>
                <track>Intermediate</track>
                
                <persons>
                    <person id='17'>Mark Stout</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/RKVN3B/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/RKVN3B/feedback/</feedback_url>
            </event>
            
        </room>
        
    </day>
    <day index='5' date='2026-07-22' start='2026-07-22T04:00:00-05:00' end='2026-07-23T03:59:00-05:00'>
        <room name='Room 1' guid='91d4d02b-7495-5eb4-946a-6a24e4f87481'>
            <event guid='a1446d4c-04f3-5f74-8978-604033793d19' id='200'>
                <room>Room 1</room>
                <title>Keynote: Packets through the ages &#8211; A personal story</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-22T09:00:00-05:00</date>
                <start>09:00</start>
                <duration>01:00</duration>
                <abstract>Before the rise of the internet (mid 1980s through the mid 1990&#8217;s , the packet and protocol ecosystem was much different than it was today. Many of the protocols have now gone extinct and new ones have risen in their place.

Moving from the world of serial protocols (e.g. HDLC/SDLC) to the Internet stack was a seismic shift, but the need to understand what&#8217;s on the wire only became more important.

What the transition was like, and why Wireshark was crucial in enabling it.</abstract>
                <slug>sf26us-200-keynote-packets-through-the-ages-a-personal-story</slug>
                <track>Beginner</track>
                
                <persons>
                    <person id='141'>Peter Jones</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/3BTBPN/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/3BTBPN/feedback/</feedback_url>
            </event>
            <event guid='1b8e53f9-b8f5-50e8-9a99-b2888dd89541' id='193'>
                <room>Room 1</room>
                <title>From Zero to Captures: Setting Up Your Own Network Simulation Lab</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-22T10:15:00-05:00</date>
                <start>10:15</start>
                <duration>01:00</duration>
                <abstract>Want to test network scenarios, learn protocols, or debug configurations without expensive hardware? This hands-on session shows how to build realistic network environments using modern containerization and virtualization tools. We&apos;ll explore different approaches to spin up multi-vendor topologies on your laptop, capture traffic between simulated devices, and understand what works (and what doesn&apos;t) in virtual environments.</abstract>
                <slug>sf26us-193-from-zero-to-captures-setting-up-your-own-network-simulation-lab</slug>
                <track>Intermediate</track>
                
                <persons>
                    <person id='1'>Roland Knall</person>
                </persons>
                <language>en</language>
                <description>Ever wanted to test a complex routing scenario, understand how a specific protocol behaves under certain conditions, or simply learn networking concepts without investing in expensive hardware? Network simulation offers a powerful alternative - your laptop becomes a complete network lab.
In this practical, hands-on session, you&apos;ll discover how to create your own virtual network environments where you can safely experiment, break things, and learn. We&apos;ll start from scratch and build up to capturing real traffic between simulated network devices, showing you exactly what&apos;s possible with modern tools and where the boundaries lie.

**What You&apos;ll Experience:**

The session begins with the fundamentals: why simulate networks, what scenarios benefit most from simulation, and what the realistic expectations are. You&apos;ll see live demonstrations of creating network topologies - routers, switches, and hosts - all running on a single machine. We&apos;ll capture traffic between these virtual devices using Wireshark, examining how packets flow through simulated networks.

A key focus will be understanding the difference between simulated and physical networks. What traffic patterns look like in virtual environments vs. real hardware, which protocols behave identically and which don&apos;t, and when timing and performance characteristics matter. You&apos;ll learn to recognize these differences in your captures.

We&apos;ll explore practical integration scenarios: connecting your physical monitoring tools to virtual networks, setting up capture points in containerized environments, and understanding device-in-the-loop testing where virtual and physical components work together. This is especially relevant for anyone working with network TAPs, packet brokers, or monitoring solutions who want to test configurations before deploying to production.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/3YYFJM/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/3YYFJM/feedback/</feedback_url>
            </event>
            <event guid='4ee6041d-435a-557a-b00a-ca53b248761c' id='195'>
                <room>Room 1</room>
                <title>Media Casting Protocols: Everything AirPlay, AirDrop and Wi-Fi Aware</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-22T11:30:00-05:00</date>
                <start>11:30</start>
                <duration>01:00</duration>
                <abstract>Ever have a client fail to find an Apple TV? Or have slow or stuttering streaming? 

Well, then look no more! AirPlay and other casting protocols are surprisingly complex, but with the help of packets, you can feel more confident troubleshooting.</abstract>
                <slug>sf26us-195-media-casting-protocols-everything-airplay-airdrop-and-wi-fi-aware</slug>
                <track>Intermediate</track>
                
                <persons>
                    <person id='86'>Eva Santos</person>
                </persons>
                <language>en</language>
                <description>We will walk through: 

-AirPlay vs AirDrop
-The five phases of AirPlay 
-How to troubleshoot the phases over packet capture (802.11, BLE) and MacBook console
-The changes to AirPlay above iOS 26 and Android support
-Alternatives to AirPlay such as Wi-Fi Aware and Miracast, differences over in packet captures</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/VAHVRB/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/VAHVRB/feedback/</feedback_url>
            </event>
            <event guid='fd838313-22d1-53a8-9621-178998ba0af4' id='194'>
                <room>Room 1</room>
                <title>The Packet Doctors are in! Packet trace examinations with the experts</title>
                <subtitle></subtitle>
                <type>Packetdoctors Session</type>
                <date>2026-07-22T13:30:00-05:00</date>
                <start>13:30</start>
                <duration>01:30</duration>
                <abstract>The experts on this panel have been asked to look at a trace file and help find a reason for certain behaviors by attendees at many SharkFests. Based on this, they&#8217;ve decided to create a public forum for examining individual trace files with a broader audience for a collective learning experience. Trace files will be gathered from attendees prior to SharkFest and only given to the panel members during the session so that the &#8220;not-
knowing what to expect and whether it can be solved&#8221; experience of working through an unknown trace file can be preserved.
Come to this session and learn to ask the right questions and look at packets in different ways.
PLEASE SEND PERPLEXING TRACE FILES FOR ANALYSIS BY THE PANEL TO jasper@packet-foo.com PRIOR TO SHARKFEST!</abstract>
                <slug>sf26us-194-the-packet-doctors-are-in-packet-trace-examinations-with-the-experts</slug>
                <track></track>
                
                <persons>
                    
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/A7BFDV/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/A7BFDV/feedback/</feedback_url>
            </event>
            <event guid='23c4e456-e7e8-5262-84d5-8d6685eadd93' id='198'>
                <room>Room 1</room>
                <title>From Specs to Packets: Generating Binary Exchange Dissectors at Scale</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-22T15:15:00-05:00</date>
                <start>15:15</start>
                <duration>01:00</duration>
                <abstract>The Open Markets Initiative (OMI) has generated millions of lines of Lua dissector code for hundreds of binary electronic-trading protocols. This talk explains how we model binary protocols and why binary protocols form their own field of computer science. We will look at real exchange protocols covering how we go from a messy pdf spec to a Wireshark dissector. The session traces the evolution of code generation from early source generators to OMI&#8217;s advanced binary data modeling, showing how this shift enabled a large ecosystem of accurate, production-grade dissectors maintained through crowdsourcing. Along the way, we&#8217;ll examine what makes a scalable binary dissector, why protocol-driven development changes the rules, and how Wireshark helped form the OMI.</abstract>
                <slug>sf26us-198-from-specs-to-packets-generating-binary-exchange-dissectors-at-scale</slug>
                <track>Intermediate</track>
                <logo>/media/sf26us/submissions/FTMZDH/Logo_zB5ntT7_EeoWRFg_99P09kh.webp</logo>
                <persons>
                    <person id='140'>William Tegel</person>
                </persons>
                <language>en</language>
                <description>This talk presents the Open Markets Initiative (OMI) as a research platform built around a protocol-driven approach to dissector generation. OMI has produced over four million lines of Lua dissectors for real-world binary exchange protocols. The core idea is that the protocol binary data model itself, not the dissector, is the primary artifact. Once the protocol is captured in a structured, reusable form, multiple classes of tooling can be generated from it, with Wireshark dissectors as a key output.

We will examine several classes of exchange protocols and show how OMI&#8217;s generator differs from earlier iterations of code generation tools, &#8220;generations of generators.&#8221; Instead of emitting code from message templates, flat schemas or other domain specific languages, our binary data models encode protocol semantics, constraints, and structural variation explicitly. This allows families of related protocols to share definitions, makes version evolution tractable, and produces dissectors that are both predictable and auditable. Using real examples, we&#8217;ll show how generator design choices directly affect correctness, maintainability, and crowd contribution.

The entire electronic trading industry benefits from the open-source Wireshark and dissector ecosystem. Many exchange protocols are underspecified, implicitly defined, or guarded by information barriers. OMI turns reverse-engineering knowledge into shared specifications that can be reviewed, improved, and extended collaboratively. That process has led to a rapid expansion of accurate, production-grade dissectors, many of which are now relied on as primary analysis tools in the electronic-trading ecosystem.

The session is aimed at attendees interested in protocol modeling, code generation, advanced dissector design, and the ways open tooling can transform opaque binary systems into observable, debuggable infrastructure.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/FTMZDH/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/FTMZDH/feedback/</feedback_url>
            </event>
            <event guid='485b8707-f8e8-51e0-af34-7e7591a90e68' id='204'>
                <room>Room 1</room>
                <title>Examining NAT behavior with Wireshark - WCA Core Topic</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-22T16:30:00-05:00</date>
                <start>16:30</start>
                <duration>01:00</duration>
                <abstract>The use of Network Address Translation in networks is unavoidable.  In this session, we will examine the different use cases of NAT and the design and application of those use cases.  We will use Wireshark to examine how NAT modifies fields in the IP and TCP header and how that can aid/hinder network troubleshooting.  Attendees can expect an interactive session where we work together to understand the details of NAT operation and usage.</abstract>
                <slug>sf26us-204-examining-nat-behavior-with-wireshark-wca-core-topic</slug>
                <track>Beginner</track>
                
                <persons>
                    <person id='9'>Ross Bagurdes</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/SJTHY9/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/SJTHY9/feedback/</feedback_url>
            </event>
            <event guid='918ac0d9-676b-509f-af51-3a553570d800' id='188'>
                <room>Room 1</room>
                <title>Sponsor Technology Showcase Reception and Dinner</title>
                <subtitle></subtitle>
                <type>Dinner</type>
                <date>2026-07-22T18:30:00-05:00</date>
                <start>18:30</start>
                <duration>03:00</duration>
                <abstract>Sponsor showcase and dinner</abstract>
                <slug>sf26us-188-sponsor-technology-showcase-reception-and-dinner</slug>
                <track>Organization</track>
                
                <persons>
                    
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/WVUP7Q/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/WVUP7Q/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Room 2' guid='a25c3679-1842-5652-94a2-5218804e6fd8'>
            <event guid='7ab2d545-dc49-5a1f-9708-90baabfbac00' id='203'>
                <room>Room 2</room>
                <title>Topology-Based PCAP Analysis: Faster Insight Beyond Packet Lists</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-22T15:15:00-05:00</date>
                <start>15:15</start>
                <duration>01:00</duration>
                <abstract>Packet analysis tools present traffic as linear sequences, requiring analysts to reconstruct relationships mentally. This session introduces a topology-based approach that visualises PCAP data as a graph of hosts and interactions, enabling immediate structural understanding.

Using real examples, including DNS failure caused by misconfigured routing, we compare traditional packet list workflows with topology-driven analysis. The approach reduces cognitive load, accelerates diagnosis, and highlights patterns that are difficult to see in sequential views.

The session includes live demonstrations showing how analysts can move from packet inspection to structural reasoning, and how this reasoning can be captured as guided investigative workflows embedded directly within the analysis environment.</abstract>
                <slug>sf26us-203-topology-based-pcap-analysis-faster-insight-beyond-packet-lists</slug>
                <track>Intermediate</track>
                <logo>/media/sf26us/submissions/8BDMAY/gt_ultimate_LIr7eeJ_5qbCS1x.webp</logo>
                <persons>
                    <person id='143'>Ryan Younger</person>
                </persons>
                <language>en</language>
                <description>Traditional packet analysis relies on sequential inspection of frames, which can obscure higher-level structure and slow down diagnosis, particularly for less experienced analysts. However, network behaviour is inherently relational, involving hosts, conversations, and protocol groupings.

This session presents a practical approach to PCAP analysis using real-time topology visualisation. Instead of focusing on individual packets, traffic is represented as a graph of nodes (hosts) and edges (conversations), allowing analysts to immediately identify communication patterns, dependencies, and anomalies.

A core case study will demonstrate a DNS resolution failure caused by a misconfigured gateway. In a standard packet list, this requires careful inspection of ARP requests, repeated DNS queries, and missing responses. In a topology view, the same issue is visible at a glance: a central host attempting external communication, combined with a misleading local dependency and no successful continuation.

The session will show how topology-based analysis:

Reduces cognitive load by externalising relationships
Accelerates identification of failure patterns
Supports both novice learning and expert triage workflows
Complements, rather than replaces, traditional packet inspection

Attendees will leave with a new mental model for analysing network traffic, and practical techniques for integrating structural reasoning into their existing workflows.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/8BDMAY/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/8BDMAY/feedback/</feedback_url>
            </event>
            
        </room>
        
    </day>
    <day index='6' date='2026-07-23' start='2026-07-23T04:00:00-05:00' end='2026-07-24T03:59:00-05:00'>
        <room name='Room 1' guid='91d4d02b-7495-5eb4-946a-6a24e4f87481'>
            <event guid='4179ae7d-b93f-5ae6-af16-24a04d3b04b4' id='192'>
                <room>Room 1</room>
                <title>SharkBytes</title>
                <subtitle></subtitle>
                <type>Organization</type>
                <date>2026-07-23T09:00:00-05:00</date>
                <start>09:00</start>
                <duration>01:00</duration>
                <abstract>SharkBytes consist of &#8220;little crunchy bits of wisdom.&#8221; Like popular TED talks, SharkBytes aim to inform, inspire, surprise, and delight by delivering a speech on a personal topic in under 5 minutes.

Information and a review of past SharkByte presentations can be found https://sharkfest.wireshark.org/sharkbytes

Email us your SharkByte session idea: sharkfest@wireshark.org</abstract>
                <slug>sf26us-192-sharkbytes</slug>
                <track>Organization</track>
                
                <persons>
                    
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/EUUK7H/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/EUUK7H/feedback/</feedback_url>
            </event>
            
        </room>
        
    </day>
    
</schedule>
