To see our schedule with full functionality, like timezone conversion and personal scheduling, please enable JavaScript and go here.
09:00
09:00
60min
Keynote: Things I Love About Wireshark (and maybe a couple of things I don't)

Gerald Combs & Friends talk about the new developments over the past year

Organization
Room 1
10:00
10:00
15min
Break
Room 1
10:00
15min
Break
Room 2
10:15
10:15
60min
Don’t blame the network – ask the network!
David Soussan

When systems have problems often times engineers say it is a network problem… and they’ll say this without any actual data pointing the finger at the network. Sometimes it is a blamestorming session – 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’t one particular thing but the interactions between two endpoints that just don’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’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.

Intermediate
Room 1
11:15
11:15
15min
Break
Room 1
11:15
15min
Break
Room 2
11:30
11:30
60min
Lessons learned in troubleshooting
Kevin Tobin

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 & failed file transfer failures etc. We will show how Wireshark helped locate root cause or prove "it's not the network".

Intermediate
Room 1
12:30
12:30
60min
Lunch
Room 1
12:30
60min
Lunch
Room 2
13:30
13:30
60min
Lost In Transmission
Megumi Takeshita

Finding and counting packet losts in each layer

Intermediate
Room 1
14:30
14:30
15min
Break
Room 1
14:30
15min
Break
Room 2
14:45
14:45
60min
Using wireshark to tshoot DICOM protocol
Jose Juan Hurtado

Learn how to quickly diagnose and troubleshoot issues related to the medical imaging DICOM protocol. Stop the finger-pointing between multiple vendors. Determine where is the bottleneck in slow connections. Resolve incompatibility issues by looking at raw communication. Evaluate impact of network quality in DICOM communications. Discuss the challenging and ever growing issue of larger images and study sizes.

Intermediate
Room 1
18:30
18:30
180min
Sponsor Technology Showcase Reception and Dinner

Sponsor Showcase and dinner

Organization
Room 1