Introduction
The Wireshark Technical Steering Committee (WTSC) steers the fundamental technical decisions within the Wireshark open source project so that the mission “to deepen the understanding of computer communications as much as possible with the use of the Wireshark analyzer suite” can be fulfilled.
The WTSC Charter provides more details.
Listed below are each of the candidates and the introductory statement supplied with their application.
Ross Bagurdes
It’s been a genuine pleasure to participate in the Wireshark community as both a user and educator. Presenting at SharkFest, in both sessions and full classes, has pushed me to grow technically and given me opportunities to share knowledge with others.
As you may know, I’ve spent the past two years working closely with Chris Greer to bring the Official Wireshark Certification Program to life. One of the things I admire most about Wireshark is how deeply it’s rooted in community support, which in many ways reflects the spirit of the internet protocols it helps us analyze. It was incredibly important for me to engage the Wireshark community to ensure our certification program effort aligned with Wireshark’s needs. I made sure we engaged key community members to provide critical feedback throughout the certification development process, which, just like with Wireshark, will be a never ending process.
Fittingly, on the same day WTSC applications are due, the Wireshark Certified Analyst certification officially goes live. It’s one of the proudest achievements of my career, and I’m excited about how it will support user engagement and demonstrate the value of Wireshark to the businesses that rely on it every day.
Wireshark is an incredible tool, and I’m proud to contribute as a user, teacher, speaker, and now as a co-creator of the official certification program. For me, this role was a culmination of a life time of work and play with computers - from my first TRS-80 CoCo2, to engineering college, to decades of teaching and developing IT curriculum, it a role custom built for my skills.
Thank you for considering my application.
Sake Blok
Transparency note: Sake is currently a member of the WTSC
I’d like to continue my membership of the WTSC. Although my work as a developer for the Wireshark project has diminished since a few years, I am a power user resulting in a good feel for what our users need and/or could use in the Wireshark suite (including the CLI tools).
- Wiki: https://wiki.wireshark.org/SakeBlok
- LinkedIn: https://www.linkedin.com/in/sakeblok/
- BlueSkey: https://bsky.app/profile/syn-bit.nl
- Mastodon: https://mastodon.nl/@SYNbit
Jasper Bongertz
Transparency note: Jasper is currently a member of the WTSC
Jasper Bongertz is a network security expert with focus on network forensics and incident response. He started working freelance in 1992 while he was studying computer science at the Technical University of Aachen. In 2009, Jasper became a Senior Consultant and Trainer for Fast Lane, where he created a large training portfolio with a special focus on Wireshark and network hacking. In 2013, he joined Airbus Defence and Space CyberSecurity, before moving on to G Data Advanced Analytics in 2019 where he is now the head of the CyberSecurity Incident Response Team (CSIRT).
Jasper is the creator of the packet analysis tool TraceWrangler, which can be used to convert, edit and sanitize PCAP files. His blog regarding network analysis, network forensics and general security topics can be found at https://blog.packet-foo.com (yes, it looks pretty deserted, but the content might still be useful to some).
- Twitter: @packetjay
- BlueSky: https://packetjay.bsky.social
- Mastodon: https://infosec.exchange/@packetjay
- LinkedIn: https://www.linkedin.com/in/jasper-bongertz-9776a41/
Anders Broman
Transparency note: Anders is currently a member of the WTSC
Worked for Ericsson 44 years and 4 month. In various positions in system test area. Responsible for Ericssons internal Wireshark for 20 odd years. Now retired.
Member of Wireshark core since March 2004. Developed numerous protocol dissectors in the telco area. ASN1 defined dissectors and others. Dabbled in gtk2 grk3 transition. Helped Implementing pcap-ng as the default file format. Doing code reviews etc.
Josh Clark
Josh is an enthusiastic Wireshark and Stratoshark user and a focused performance analysis mentor in both tools. He has over a decade of experience using Wireshark to learn how network protocols work and identify bottlenecks in distributed systems. He is also an early adopter of Stratoshark for troubleshooting and performance analysis. Josh is also a 4-time presenter at Sharkfest with a particular focus in teaching network people how servers put packets on the network.
As a Technical Steering Committee member, Josh will advocate for making Wireshark and Stratoshark easier to use in more places. His enhancement request history on GitLab already shows that advocacy. He has submitted several requests to make Wireshark more approachable to new users and make Stratoshark more capable of reading system calls on more platforms.
If you want to learn more about Josh, you are welcome to visit his website at www.jeclark.net. You can also find details about his past Sharkfest presentations on Github and see what he has to say on LinkedIn.
Chris Greer
Much to my surprise, I received an invitation to apply for election to the Wireshark Technical Steering Committee. What an honor to be extended such an opportunity. I was asked to share why I would like to join as a member of the WTSC and what my experience with the project is.
The Wireshark analyzer and the community behind it have been a focus of my professional interest for over two decades. In short, I love the art of packet analysis and learning as much as I can about it. My other passion is helping others learn how to develop this art, primarily with the Wireshark analyzer. Teaching others how to make sense of the traffic they see is interesting, challenging, and exciting all at the same time. It gives me great joy to hear from former students and clients as they share their packet war-stories and how they found the root cause of complex network problems with Wireshark. I feel I could contribute to the WTSC with information from the field of Wireshark users, both as a consultant for hire and Wireshark educator. As a member of the team who designed and created the Wireshark Certified Analyst (WCA) certification, benefitting from WTSC meetings would assist in steering the certification and ensuring it keeps pace with the direction of the product and community as a whole.
In 2011, I attended my first SharkFest Dev/User conference, primarily to record the sessions and assist in getting them documented. In 2012, I presented my first session on the capture limitations of a laptop. Since then, I have attended almost every US based conference, and some in the EU. As an educator, in 2018 I was asked to co-present the introductory pre-conference course, which was both an honor and an exciting challenge. Since then I have had the opportunity to teach many of the pre-conference intro courses, as well as one on Threat Hunting for security focused attendees.
Apart from SharkFest, with the goal to reach as many people as people as possible with Wireshark tips, tricks, and best practices, in 2010 I started a YouTube channel focused on how to get the most out of Wireshark. As the channel grew, I was amazed to connect with more and more of the community of users. Their questions began to steer my content, bringing more ideas for videos and relevant technical use-cases to the channel. In 2021 I was asked by a much larger YouTuber - David Bombal, who focuses on the CCNA space - to join him on his channel to share more protocol and Wireshark content. This collaboration widened my channel into a new user community, which drove viewership to over 100,000 views per month and over 150,000 subscribers.
At no time did I ever foresee the content growing to this point, but I am quite excited that it has. I see it as a vehicle to continue to share, promote, and encourage the art of packet analysis to the new generation of users. If elected as a member of the WTSC, it would help me to further support the growth of the product and the community.
- YouTube: https://youtube.com/chrisgreer
- LinkedIn: https://linkedin.com/in/cgreer
- Website: www.packetpioneer.com
Joakim Karlsson
I have a 13 years background running Quality Assurance at Ericsson AB. From Function Tester/Developer and to Function Test Architect on Packet Core products. From where I got subjected to first becoming a user of Wireshark, to later contributing changes, and today Core Developer.
My area of expertise revolves around 2G/3G/4G/5G protocols, most Telecom protocols.
Jaap Keuter
Transparency note: Jaap is currently a member of the WTSC
As long time core developer and being involved with the creation of Foundation and the WFAC, now WTSC, I feel we’re not done yet putting this project on solid ground. Many things are going in the right direction, among which is starting the Foundation in the first place and now getting a certification program going for instance. But there is still things to do to embed the project and foundation more solidly in the FOSS space. A more extensive network of foundation members and cooperation in Open Source Software bodies is essential for the long term existence of this project. I would like to be able to contribute to this ongoing effort to make this project a lasting success.
Roland Knall
Transparency note: Roland is currently a member of the WTSC
Hey everyone! I’m Roland Knall, a Wireshark Developer since 2013, a Wireshark Core Developer since 2016 and current WTSC member running for re-election. Over the past nine years, I’ve focused on making Wireshark more accessible and user-friendly through UI improvements and community building. You might know me as the voice behind the SharkBytes podcast, where I chat with community members about packet analysis, career development, and the future of networking.
My technical contributions center on practical features that solve real workflow problems. I co-developed the extcap interface that lets Wireshark capture from Android devices, SSH connections, and specialized hardware. I’ve also worked on drag-and-drop filters and columns, the profile management feature and the profiles import/export system that helps teams share analysis configurations. I like to think: “what makes my life easier using Wireshark” when searching for new things that can be implemented.
Beyond coding, I’m deeply involved in keeping our community connected and growing. I moderated panels at SharkFest conferences as well as the conferences themselves, handle technical integrations for our Discord server (now 6,000+ members strong), and help maintain the collaborative atmosphere that makes Wireshark special. Through the podcast, I’ve had the privilege of interviewing everyone from Gerald Combs to scholarship recipients, always trying to create space for diverse voices and perspectives in our community.
Looking ahead, I’m excited to keep continuing to strengthen our governance structures through the WTSC. The establishment of the Wireshark Foundation as a nonprofit shows we’re thinking long-term, and I want to help ensure Wireshark remains both technically excellent and community- as well as open-source driven. If re-elected, I’ll keep working to balance innovation with accessibility, making sure Wireshark serves both newcomers and experts while fostering the welcoming community that’s been our strength for over two decades.
Mike Mann
I’ve been a Wireshark core developer since 2012, but went inactive ~2019 because my “day job” got a little too hectic. I left that job in January and have jumped back into Wireshark development in the past month or so. I’ve spent most of my career “getting embedded (industrial) devices to talk to each other”, hence the need and attraction to Wireshark. What has kept me interested is the number of development opportunities - GUI, scripts, refactoring, reducing technical debt and of course, increased dissection. I can always find something to work on, some puzzle to be solved.
I will continue to try to get submitted MRs “over the finish line” in areas I feel confident in (mostly dissection functionality) and try to shape the APIs into “as simple as possible, but no simpler”. Sometimes protocols aren’t written to be “dissection friendly”, but I want code to be as clean as possible because some developer will probably copy/paste it as a starting point, and you wind up having to fix 2 things.
I don’t have any relevant affiliations, and my LinkedIn profile can be found here: Mike Mann | LinkedIn. While I have a few personal GitHub projects, Wireshark is most of the “public” code I’ve written.
Peter Wu
Transparency note: Peter is currently a member of the WTSC
I would love to help continue making the Wireshark community project a success. During WTSC meetings, I have previously been taking notes. While that could potentially be replaced by AI tools, I have found the quality of these summaries somewhat disappointing. As such, I plan to continue to help there.
As Core Developer, I have been primarily been involved in the TLS dissector and related components. Whenever I run into something that is not working optimally, I try to tackle it and achieve the best user experience within the given constraints.
The experience and knowledge gained during Wireshark development and my work in the Cloudflare Research team also translate to educational presentations at SharkFest.
While I have unfortunately been somewhat busy, and not contributing as much in form of reviews and code, feel free to poke me for anything that needs help. Wireshark is important software with a rich community, it deserves good care.