Using WizShark to

Help in Your Wi-Fi

Troubleshooting

#WLPC

Robert A. Ferruolo @raferruolo

Motivation

Trace based troubleshooting is often the best option

High level graphs aren't always that useful for root

cause analysis

Statistical data isn't really that good at pointing to

the cause of an issue

Some issues can be missed when viewing packet

captures

@raferruolo

The philosophy behind WizShark

Effective and deep visualization for quick detection

of issues

Facilitate troubleshooting collaboration

Eliminate Trace Fatigue

Enable remote trouble shooting from any type of

device

@raferruolo

A picture is worth a thousand packets …

@raferruolo

Quick Interface Walkthrough

Dashboard

• Client/AdHoc/AP

• Sort

• Search

Trace View

• Frame View/Time View/Frame List

• Zoom in/out

• Scroll

• Share/Collaborate

• Filter

wizshark.net

Capturing / Uploading Traces

Workflows:

1. Use AP to Capture, Stream Locally then Drag and

Drop to WizShark

2. Capture with Wireshark and Upload Directly to

WizShark with New Plugin

3. Capture with Any Tool then Drag and Drop to

WizShark

wizshark.net

Ping Ponging Client

wizshark.net

Client Stops Communicating at Lower Data Rates

wizshark.net

Poor Video Performance

wizshark.net

Host Authentication Fail (Video Case Study)

wizshark.net

EAPOL Incompatibility

wizshark.net

Collaboration

wizshark.net

Key Takeaways

End-to-end remote troubleshooting from AirTight Cloud

Troubleshooting from a mobile device

Traces are cached and indexed for quicker retrieval

Built-in trace sharing for collaboration

Wi-Fi vendor agnostic -- supports PCAP family

Key Takeaways

More info at https://wizshark.net/

#WLPC

Thank you!