<?xml version='1.0' encoding='utf-8' ?>
<!-- Made with love by pretalx v2026.2.1. -->
<schedule>
    <generator name="pretalx" system="conference.wireshark.org" version="2026.2.1" />
    <version>2026-03-59</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>America/Chicago</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='Hermitage ABC | General Session' guid='91d4d02b-7495-5eb4-946a-6a24e4f87481'>
            <event guid='415214cc-a53e-527d-a081-f1edb959abff' id='189' code='BSA8P7'>
                <room>Hermitage ABC | General Session</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='155'>Chris Greer</person><person id='154'>Ross Bagurdes</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>
            <event guid='e2aee2d8-deac-55d5-b503-19706d7921ba' id='197' code='FYWGV9'>
                <room>Hermitage ABC | General Session</room>
                <title>Feeding Frenzy of Wild Ideas: When Sharks Brainstorm</title>
                <subtitle></subtitle>
                <type>Organization</type>
                <date>2026-07-18T17:00:00-05:00</date>
                <start>17: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.

This is open-house / open-door. Just come in and have some fun throwing ideas around</abstract>
                <slug>sf26us-197-0-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>
            
        </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='Hermitage ABC | General Session' guid='91d4d02b-7495-5eb4-946a-6a24e4f87481'>
            <event guid='987f7bf9-4da2-56f6-b74c-10bd081e2627' id='189' code='BSA8P7'>
                <room>Hermitage ABC | General Session</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='155'>Chris Greer</person><person id='154'>Ross Bagurdes</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='Hermitage ABC | General Session' guid='91d4d02b-7495-5eb4-946a-6a24e4f87481'>
            <event guid='902e8e03-54cc-5233-a277-e18dee25ec41' id='190' code='A3PJVZ'>
                <room>Hermitage ABC | General Session</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='156'>Josh Clark</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>true</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='10a85ba4-b4fd-5a0e-8d82-22122a8f89f7' id='241' code='PGTGW3'>
                <room>Hermitage ABC | General Session</room>
                <title>Sharkfest How To Tutorial</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-20T17:00:00-05:00</date>
                <start>17:00</start>
                <duration>00:30</duration>
                <abstract>Are you at Sharkfest for the first time? Then this session is for you. We&apos;ll explain how the conference works and what&apos;s probably different from other conference you may have been at. You&apos;ll learn about Packet Doctors, the evening events, the onsite WCA exam, and what the developer den is. The goal is to make sure you don&apos;t feel you missed out on something at the end of the conference because you didn&apos;t know how it worked.</abstract>
                <slug>sf26us-241-sharkfest-how-to-tutorial</slug>
                <track>Beginner</track>
                
                <persons>
                    <person id='188'>Jasper Bongertz</person>
                </persons>
                <language>en</language>
                <description>This should be a **30 minute slot** right before the welcome dinner, if possible, or maybe parallel to the start of the welcome dinner.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/PGTGW3/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/PGTGW3/feedback/</feedback_url>
            </event>
            <event guid='8cb11da3-b08e-5883-b105-779c7b2e0846' id='186' code='X73HTY'>
                <room>Hermitage ABC | General Session</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='Hermitage ABC | General Session' guid='91d4d02b-7495-5eb4-946a-6a24e4f87481'>
            <event guid='cd3b8e9e-70c9-5f81-94f0-d16f227fc097' id='191' code='H89ETP'>
                <room>Hermitage ABC | General Session</room>
                <title>Keynote: Wireshark Progress, Problems, and Plans</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-keynote-wireshark-progress-problems-and-plans</slug>
                <track>Organization</track>
                
                <persons>
                    <person id='192'>Gerald Combs</person>
                </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='78ff160d-9c2c-575b-a9a4-cdda13638429' id='237' code='GKG8F3'>
                <room>Hermitage ABC | General Session</room>
                <title>What is new in Wireshark</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-21T10:15:00-05:00</date>
                <start>10:15</start>
                <duration>01:00</duration>
                <abstract>We give an overview over interesting tidbits with the Wireshark Development team as well as an outlook on version 5.0</abstract>
                <slug>sf26us-237-what-is-new-in-wireshark</slug>
                <track>Beginner</track>
                
                <persons>
                    <person id='185'>Roland Knall</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/GKG8F3/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/GKG8F3/feedback/</feedback_url>
            </event>
            <event guid='eef77d22-8009-529f-892e-3992b513156a' id='207' code='DBPZAJ'>
                <room>Hermitage ABC | General Session</room>
                <title>Demystifying DNS Security: DNSSEC, DoT, DoH, DoQ - When and Where to Use them</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-21T11:30:00-05:00</date>
                <start>11:30</start>
                <duration>01:00</duration>
                <abstract>DNS security doesn&#8217;t have to be confusing! In this session, we&#8217;ll break down DNSSEC, DoT, DoH, and DoQ in simple terms&#8212;what they do, how they&#8217;re different, and why you need to know when and where to use each one. We&#8217;ll take a hands-on look with Wireshark to see how these protocols actually behave at the packet level. By the end, you&apos;ll have a solid grasp of how to secure your DNS traffic, what Protective DNS really does, and how to pick the right tool for the job.

Beginners welcome. DNS newbies too.</abstract>
                <slug>sf26us-207-demystifying-dns-security-dnssec-dot-doh-doq-when-and-where-to-use-them</slug>
                <track>Intermediate</track>
                
                <persons>
                    <person id='155'>Chris Greer</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/DBPZAJ/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/DBPZAJ/feedback/</feedback_url>
            </event>
            <event guid='80ecd092-3c9d-5377-b2db-c105f5effbdf' id='166' code='SAY8D9'>
                <room>Hermitage ABC | General Session</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='139'>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' code='XPYXAB'>
                <room>Hermitage ABC | General Session</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='159'>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='4ceb7c5d-7c53-54f2-be1a-4b5ccaaf5d12' id='232' code='PNSKEA'>
                <room>Hermitage ABC | General Session</room>
                <title>Capturing the spectrum of wireless packets</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-21T16:00:00-05:00</date>
                <start>16:00</start>
                <duration>01:00</duration>
                <abstract>There is a veritable avalanche of wireless devices, from Wi-Fi and Bluetooth to Zigbee, aircraft, thermometers, door sensors, Lora mesh, and more.  If you can&apos;t see it, you can&apos;t analyze it or debug it; we&apos;ll talk about ways to capture as many protocols flying around in the air as we can, and what the most affordable hardware to do it is.</abstract>
                <slug>sf26us-232-capturing-the-spectrum-of-wireless-packets</slug>
                <track>Beginner</track>
                
                <persons>
                    <person id='181'>Mike Kershaw</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/PNSKEA/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/PNSKEA/feedback/</feedback_url>
            </event>
            <event guid='2e6a4435-1f25-5e6f-91a7-329d982f6ac4' id='199' code='LRBBM8'>
                <room>Hermitage ABC | General Session</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='161'>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' code='WNWRRU'>
                <room>Hermitage ABC | General Session</room>
                <title>Sponsor Technology Showcase Reception, Team Trivia for IT Nerds, 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-team-trivia-for-it-nerds-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='Hermitage D | Classroom' guid='a25c3679-1842-5652-94a2-5218804e6fd8'>
            <event guid='5e865f1a-9c33-5d02-8f77-f3879003ec37' id='240' code='ZBAFXP'>
                <room>Hermitage D | Classroom</room>
                <title>TCP details that matter for the WCA Exam</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-21T11:30:00-05:00</date>
                <start>11:30</start>
                <duration>01:00</duration>
                <abstract>The _Wireshark Certified Analyst_ exam is not an easy certification to take, especially if your knowledge about the details of the TCP protocol is somewhat shaky. In this talk we&apos;ll take a look at the aspects mentioned in the WCA curriculum and discuss them together. The goal is to make sure you understand what you need to bring to the exam and help you identify the areas where you might have to improve your skill analyzing TCP to achieve the WCA status.</abstract>
                <slug>sf26us-240-tcp-details-that-matter-for-the-wca-exam</slug>
                <track>Expert / Developer</track>
                
                <persons>
                    <person id='188'>Jasper Bongertz</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/ZBAFXP/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/ZBAFXP/feedback/</feedback_url>
            </event>
            <event guid='b1f84748-76a6-5759-929d-44dd659a0b44' id='201' code='PDJYJ9'>
                <room>Hermitage D | Classroom</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='163'>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='da5c8e63-eda7-54aa-95de-6eb10f16cb2e' id='249' code='CPNTMA'>
                <room>Hermitage D | Classroom</room>
                <title>NGNE with AI: Think Like an Architect</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-21T14:45:00-05:00</date>
                <start>14:45</start>
                <duration>01:00</duration>
                <abstract>AI is already changing how network engineers learn, troubleshoot, document, automate, and operate networks. But the opportunity is not to hand the network over to a chatbot. The opportunity is for hands-on practitioners to move up a level: defining better workflows, writing clearer requirements, setting stronger guardrails, validating results, and using AI as a force multiplier.

This talk introduces practical AI concepts for network engineers, including LLMs, agents, prompt workflows, API-based tooling, Spec-Driven Development, Test-Driven Development, and the role of deterministic automation alongside AI systems. We will walk through realistic NetOps use cases such as MOP review, incident summarization, log and packet capture analysis, Python and config generation, and an SDD-based workflow using real AI-assisted infrastructure design work.

The central message is simple: the next-generation network engineer does not stop being hands-on. The NGNE learns to think like an architect.</abstract>
                <slug>sf26us-249-ngne-with-ai-think-like-an-architect</slug>
                <track>A.I.</track>
                <logo>/media/sf26us/submissions/CPNTMA/image_Sut1jmD.webp</logo>
                <persons>
                    <person id='195'>Scott F Robohn</person>
                </persons>
                <language>en</language>
                <description>Here is a slightly longer version of the abstract:

AI is already changing how network engineers learn, troubleshoot, document, automate, and operate networks. But the opportunity is not to hand the network over to a chatbot. The opportunity is for hands-on practitioners to move up a level: defining better workflows, writing clearer requirements, setting stronger guardrails, validating results, and using AI as a force multiplier.

This talk introduces practical AI concepts for network engineers, including LLMs, agents, prompt workflows, API-based tooling, Spec-Driven Development, Test-Driven Development, and the role of deterministic automation alongside AI systems. We will walk through realistic NetOps use cases such as MOP review, incident summarization, documentation cleanup, log and packet capture analysis, Python generation, config generation, and an SDD-based workflow using real AI-assisted infrastructure design work.

The central message is simple: the next-generation network engineer does not stop being hands-on. The NGNE learns to think like an architect: designing workflows, constraining tools, reviewing ruthlessly, validating behavior, and using the right tool for the right job.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/CPNTMA/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/CPNTMA/feedback/</feedback_url>
            </event>
            <event guid='a9fdf509-af7f-5449-ab64-4c230c8dc7c9' id='231' code='BGPWJC'>
                <room>Hermitage D | Classroom</room>
                <title>Wireshark plus Advanced Analytics &#8211; Better Together (2 part session)</title>
                <subtitle></subtitle>
                <type>Workshop</type>
                <date>2026-07-21T16:00:00-05:00</date>
                <start>16:00</start>
                <duration>02:15</duration>
                <abstract>Real life troubleshooting a difficult 3rd party software performance issue with using Wireshark and Advanced Analytics</abstract>
                <slug>sf26us-231-wireshark-plus-advanced-analytics-better-together-2-part-session</slug>
                <track>Expert / Developer</track>
                
                <persons>
                    <person id='180'>John Pittle</person>
                </persons>
                <language>en</language>
                <description>Join us for a troubleshooting deep dive into solving a difficult problem occurring within Webex login from 2018, known as the 98% hang condition.  We&#8217;ll showcase how the partnership of Wireshark and Advanced Analytics can be leveraged to quickly isolate the fault domain.  Captures will be provided for use during the session.  Session is half presentation and half hands-on lab with Wireshark.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/BGPWJC/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/BGPWJC/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='Hermitage ABC | General Session' guid='91d4d02b-7495-5eb4-946a-6a24e4f87481'>
            <event guid='a1446d4c-04f3-5f74-8978-604033793d19' id='200' code='3BTBPN'>
                <room>Hermitage ABC | General Session</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='162'>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='6fbb9f1a-de99-5332-b32b-b5626887d8f3' id='234' code='ZSVEAS'>
                <room>Hermitage ABC | General Session</room>
                <title>Burnout Is Only the Beginning: How to Prevent a Buildup of Trauma in IT</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-22T10:15:00-05:00</date>
                <start>10:15</start>
                <duration>01:00</duration>
                <abstract>Your network never sleeps. Neither does your team &#8212; and that&apos;s the problem.

IT pros are on call at 3am, absorbing abuse from non-technical staff, and carrying the weight of every outage. The result? A workforce burning out quietly, abandoning their posts, snapping at their families, and turning to substances to cope. According to the CDC, suicide rates among IT professionals are quietly climbing. This discussion needs to happen now.

DJ Eshelman has 25+ years in IT consulting and has lived these stories firsthand. In this session, he breaks down how trauma accumulates in IT, why burnout is a management failure not a technology one, and what network leaders can do right now to stop the cycle.

You&apos;ll leave with: practical steps to protect your team, reduce technical debt, and retain the people keeping your infrastructure alive.

The biggest threat to your network isn&apos;t the next zero-day or patch gone bad. It&apos;s losing the people who defend it.</abstract>
                <slug>sf26us-234-burnout-is-only-the-beginning-how-to-prevent-a-buildup-of-trauma-in-it</slug>
                <track>Beginner</track>
                <logo>/media/sf26us/submissions/ZSVEAS/image_uCAec2E.webp</logo>
                <persons>
                    <person id='183'>D. J. Eshelman</person>
                </persons>
                <language>en</language>
                <description>**Why Your Network Is Only As Strong As The People Running It**

You came to SharkFest to sharpen your technical skills. But this is the session that might change something more fundamental.

Network engineers are among the most overworked, under-resourced professionals in any industry. The 3am calls, the constant firefighting, the impossible on-call expectations &#8212; they don&apos;t just create stress. Over time, they create trauma. And that trauma follows people from job to job, quietly compounding until it becomes a crisis.

DJ Eshelman has 25+ years in IT  consulting and has lived these stories firsthand. Now as an Independent Executive Director with Maxwell Leadership, he&apos;s dedicated to changing the IT Leadership world.
In this session, he breaks down how trauma accumulates in technical environments, how to recognize the signs in yourself and your team, and critically, why most of it is a management problem, not a technology problem.

You&apos;ll leave with:

- A clear framework for understanding the IT trauma cycle (aka IT PTSD)
- Practical steps managers can take immediately to protect their teams
- Tools for structured priority management that reduce reactive chaos
- An honest look at what actually retains great technical talent

Prior attendees have had all-day discussions about this talk which tells us it is just that important right now.

Whether you&apos;re an individual contributor, a team lead, or a department head, the health of the people running your network is just as mission-critical as the network itself.

The biggest threat to your infrastructure isn&apos;t the next zero-day. It&apos;s losing the people who defend it.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/ZSVEAS/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/ZSVEAS/feedback/</feedback_url>
            </event>
            <event guid='4ee6041d-435a-557a-b00a-ca53b248761c' id='195' code='VAHVRB'>
                <room>Hermitage ABC | General Session</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='158'>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' code='A7BFDV'>
                <room>Hermitage ABC | General Session</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>
                    <person id='188'>Jasper Bongertz</person>
                </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' code='FTMZDH'>
                <room>Hermitage ABC | General Session</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='160'>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='9eb468bc-732f-58fd-9379-b0f333a9be68' id='255' code='EZKBZW'>
                <room>Hermitage ABC | General Session</room>
                <title>TCP SACK Overview and Impact on Performance</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-22T16:30:00-05:00</date>
                <start>16:30</start>
                <duration>01:00</duration>
                <abstract>TCP SACK is an important performance enhancement to TCP. Learn the details of how to interpret the SACK field and relate it to performance of the application, using a very interesting case study from an actual customer.</abstract>
                <slug>sf26us-255-tcp-sack-overview-and-impact-on-performance</slug>
                <track>Intermediate</track>
                
                <persons>
                    <person id='180'>John Pittle</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/EZKBZW/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/EZKBZW/feedback/</feedback_url>
            </event>
            <event guid='8f159cfd-8698-561d-af48-f1473a3ecc87' id='197' code='FYWGV9'>
                <room>Hermitage ABC | General Session</room>
                <title>Feeding Frenzy of Wild Ideas: When Sharks Brainstorm</title>
                <subtitle></subtitle>
                <type>Organization</type>
                <date>2026-07-22T17:45:00-05:00</date>
                <start>17:45</start>
                <duration>00:45</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.

This is open-house / open-door. Just come in and have some fun throwing ideas around</abstract>
                <slug>sf26us-197-1-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='918ac0d9-676b-509f-af51-3a553570d800' id='188' code='WVUP7Q'>
                <room>Hermitage ABC | General Session</room>
                <title>Sponsor Technology Showcase Reception, esPCAPe Group Packet Challenge 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, group packet challenge and dinner</abstract>
                <slug>sf26us-188-sponsor-technology-showcase-reception-espcape-group-packet-challenge-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='Hermitage D | Classroom' guid='a25c3679-1842-5652-94a2-5218804e6fd8'>
            <event guid='e75788b9-ac20-595b-bcd7-9fe22a5b1abb' id='165' code='M8KMKW'>
                <room>Hermitage D | Classroom</room>
                <title>Don&#8217;t blame the network &#8211; ask the network!</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-22T10: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='138'>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='d7f5423b-15ae-54ae-838e-9fcac84f5909' id='202' code='RKVN3B'>
                <room>Hermitage D | Classroom</room>
                <title>Understanding LTE &amp; 5G: 3GPP Packet Flow and Network Analysis</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-22T11:30:00-05:00</date>
                <start>11:30</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='164'>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>
            <event guid='7ab2d545-dc49-5a1f-9708-90baabfbac00' id='203' code='8BDMAY'>
                <room>Hermitage D | Classroom</room>
                <title>Topology-Based PCAP Analysis: Wireshark-Integrated 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 a real NetSupport RAT infection from a published malware-traffic-analysis.net exercise, 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 also demonstrates a Wireshark-integrated workflow using PDML export, and an AI analysis engine that runs entirely in the browser: an evidence-grounded triage layer that identifies the infected host, its C2 beacon, and the protocol disguise in seconds, without packet data ever leaving the machine.</abstract>
                <slug>sf26us-203-topology-based-pcap-analysis-wireshark-integrated-insight-beyond-packet-lists</slug>
                <track>Intermediate</track>
                <logo>/media/sf26us/submissions/8BDMAY/image_ApBlXqv.webp</logo>
                <persons>
                    <person id='165'>Ryan Younger</person>
                </persons>
                <language>en</language>
                <description>Traditional packet analysis relies on sequential inspection of frames, which obscures higher-level structure and slows diagnosis, particularly for less experienced analysts. 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. Traffic is represented as a graph of nodes (hosts) and edges (conversations), letting analysts immediately identify communication patterns, dependencies, and anomalies.

A single case study anchors the session: a threat hunt through a real 15,000-packet NetSupport RAT capture from a published malware-traffic-analysis.net exercise. In a packet list the C2 channel hides in plain sight: one conversation among nearly a hundred external hosts, on port 443, dressed as TLS. In the topology it surfaces as a persistent edge that never goes quiet. The built-in AI analysis then completes the picture: a deterministic, evidence-first engine flags 273 requests on a fixed 60-second timer inside a single long-lived connection, plus cleartext HTTP on a TLS port whose User-Agent names the tooling itself. The analysis runs on-device in the browser, every claim is grounded in the capture, and the suggested display filters pivot straight back into packet-level verification, completing the incident report from verdict to infected host, hostname, and user.

The session will show how topology-based analysis:

Reduces cognitive load by externalising relationships
Accelerates identification of attack and failure patterns
Supports both novice learning and expert triage workflows
Extends structural reasoning with grounded, on-device AI triage
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 and AI-assisted triage 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>
            <event guid='ef7a8f51-8317-5419-a04a-1ada7e856795' id='239' code='RTCHM3'>
                <room>Hermitage D | Classroom</room>
                <title>Attacks in the Network - A look at real world malicious traffic examples</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-22T16:30:00-05:00</date>
                <start>16:30</start>
                <duration>01:00</duration>
                <abstract>It&apos;s not easy to spot attacks in network packets, mostly because there&apos;s so many of them (packets, that is), resulting in the Signal-to-Noise ratio is extremely high. But there are also additional challenges, like encryption or attackers simply using protocols that administrators use themselves. We&apos;ll take a look at a number of real world scenarios and learn about various attack patterns and how to find/recognize them.</abstract>
                <slug>sf26us-239-attacks-in-the-network-a-look-at-real-world-malicious-traffic-examples</slug>
                <track>Security</track>
                
                <persons>
                    <person id='188'>Jasper Bongertz</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/RTCHM3/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/RTCHM3/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='Hermitage ABC | General Session' guid='91d4d02b-7495-5eb4-946a-6a24e4f87481'>
            <event guid='4179ae7d-b93f-5ae6-af16-24a04d3b04b4' id='192' code='EUUK7H'>
                <room>Hermitage ABC | General Session</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>
            <event guid='485b8707-f8e8-51e0-af34-7e7591a90e68' id='204' code='SJTHY9'>
                <room>Hermitage ABC | General Session</room>
                <title>Examining NAT behavior with Wireshark - WCA Core Topic</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-23T10:15:00-05:00</date>
                <start>10:15</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='166'>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='aed488e3-f964-5b46-9c4f-c6265d20a467' id='208' code='7X7YG3'>
                <room>Hermitage ABC | General Session</room>
                <title>Understanding and Analyzing Web Performance</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-23T11:30:00-05:00</date>
                <start>11:30</start>
                <duration>01:00</duration>
                <abstract>Why is the website slow?

This simple question can spawn a whole world of complexity, so let&apos;s take a tour through it!

We will use browser developer tools as our north star, diving into packets as well as internal net-export logs to show what&apos;s happening at every step of a web request. By translating the waterfall to the wire, we&apos;ll be able to understand common web performance bottlenecks and the quick fixes that make them disappear. 

Finally, we&apos;ll take a peek at energy-aware web design to see how a website can mindfully sip power rather than burning through a battery. 

You will leave this session with the tools and understanding to debug modern websites.</abstract>
                <slug>sf26us-208-understanding-and-analyzing-web-performance</slug>
                <track>Beginner</track>
                
                <persons>
                    <person id='156'>Josh Clark</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>true</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/7X7YG3/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/7X7YG3/feedback/</feedback_url>
            </event>
            
        </room>
        <room name='Hermitage D | Classroom' guid='a25c3679-1842-5652-94a2-5218804e6fd8'>
            <event guid='2d573846-0a1f-59e6-9eb4-316612d84587' id='246' code='YNP8WZ'>
                <room>Hermitage D | Classroom</room>
                <title>AI Found Holes In Our Cheese</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-23T10:15:00-05:00</date>
                <start>10:15</start>
                <duration>01:00</duration>
                <abstract>This past spring, the software world was rocked by AI vulnerability storm, as the state of the art in AI vulnerability scanning advanced rapidly, and flaws were found in the software that we use every day. Wireshark wasn&apos;t spared from this, and in this talk Gerald will show how Wireshark was impacted, and the processes and tools that the development team uses to protect Wireshark from security issues.</abstract>
                <slug>sf26us-246-ai-found-holes-in-our-cheese</slug>
                <track>Security</track>
                
                <persons>
                    <person id='192'>Gerald Combs</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://conference.wireshark.org/sf26us/talk/YNP8WZ/</url>
                <feedback_url>https://conference.wireshark.org/sf26us/talk/YNP8WZ/feedback/</feedback_url>
            </event>
            <event guid='8dbd4860-0002-50d6-b1b0-ca6ab3bf5151' id='210' code='TPZ79F'>
                <room>Hermitage D | Classroom</room>
                <title>Troubleshooting with Wireshark and how to explain your findings</title>
                <subtitle></subtitle>
                <type>Presentation</type>
                <date>2026-07-23T11:30:00-05:00</date>
                <start>11:30</start>
                <duration>01:00</duration>
                <abstract>We will focus on troubleshooting with Wireshark and how to present your results to audiences of different technical levels with the use of Profiles, filters and other views in Wireshark.  I will provide sample profiles and captures so you can follow along</abstract>
                <slug>sf26us-210-troubleshooting-with-wireshark-and-how-to-explain-your-findings</slug>
                <track>Beginner</track>
                
                <persons>
                    <person id='171'>Patrick Barber</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

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