
"The Wi-Fi drops when I walk down the corridor."
Sound familiar? It's one of the most common complaints in Wi-Fi, and one of the hardest to prove. The user feels a gap on their call. The dashboard says everything's fine. And the only place the truth lives is in the packets.
So we built a tool for it. The Roaming Calculator takes a packet capture, finds every roam a client made, and tells you how long each one took, to the millisecond. Then it shows you the roam happening, frame by frame.
It's free. There's no account. And your capture never leaves your device.
Here's how to use it.
What you need
One thing: a wireless packet capture taken in monitor mode, with a client roaming in it.
- Formats: pcap or pcapng from Wireshark, an OmniPeek .pkt, or any of those gzipped.
- Both channels: a roam is a conversation with two APs, usually on two different channels. If your capture only listened to one of them, you'll get half the story. Capture on both.
- Not a wired capture. Roaming happens over the air, so a capture from a switch port won't have it.
Don't have a capture to hand? No problem. Press Watch a sample roam on the start page and the tool loads a made-up one, so you can follow along with everything below.

Step 1: Load your capture
Go to roam.wifininjas.net and press Choose a capture, or drop the file anywhere on the page.
That's it. The capture opens in your browser and stays there. Nothing is uploaded, because there's nowhere to upload it to: the page isn't allowed to talk to anything but itself. Captures hold sensitive stuff, so we built it that way on purpose.
A few seconds later you'll see what's in it.

Step 2: Pick the network and the client
On the left you'll see every network (SSID) in the capture and every client that joined it. No typing MAC addresses.
The tool picks the network and the client with the most roams for you. If that's not the one you're after, just click another.
Step 3: Give things proper names
00:00:5e:00:53:a1 doesn't mean much to anyone. "Reception" does.
Click any name to change it. APs start out as AP1, AP2 and so on, and the client starts as "Client". Rename them to whatever makes sense on your site, and the new names show up everywhere: the scoreboard, the animation, and the results you copy out.
You can also click the little device picture next to the client to change it to a laptop, a scanner, a voice handset and so on.

Step 4: Read the scoreboard
Every roam gets a row and a bar. The white line is the target: 150 ms unless you change it.
- Green means the roam beat the target.
- Red means it didn't.
- Grey means frames were missing from the capture, so the tool won't guess.

In the sample, Matt's laptop made two roams and both were slow: 429 ms and 771 ms. More on why in a moment.
You'll also see first connections listed underneath. They're measured the same way, but they aren't roams and they aren't judged, because a first connection always does the full login.
Step 5: Watch the roam
Click a roam and press Play. This is the fun bit.
Your character walks from the old AP to the new one while every frame of the roam flies between them, in order. The colours match Wireshark, so an Authentication frame is red and EAP is purple, the same as you're used to.
Underneath, a timeline builds to scale, so you can see exactly where the time went.

A few things to try:
- Step forwards and backwards one frame at a time with the arrow buttons.
- Slow, Normal, Fast changes the speed.
- Click any frame in the list to jump straight to it. The frame numbers match Wireshark's, so you can go and find the same frame there.
- Swap between Matt and Mac, and between an office, a warehouse and a hospital. It makes no difference to the numbers. It's just more fun.
The call bubble
Next to the character there's a small bubble that shows what a voice or video call would feel like during the roam.
- Green: the call's fine.
- Amber: silence, but short enough that you wouldn't notice.
- Red: the roam has gone past the target and the call is breaking up.
One honest caveat: it shows what a call would feel like. Your client may not have been on one.
Step 6: Read the two numbers
There are two ways to time a roam, and people argue about which is right. The answer is both, so the tool gives you both.
Auth to auth. From the first frame the client sends to the new AP to the last frame of the key exchange. This is the roam itself, and it's the number the verdict uses.
Data to data. From the last data frame on the old AP to the first on the new one. This is what the user feels, but only if the client was sending something. If it was sitting idle, you're measuring the silence, not the roam. The tool tells you when that's the case.

Step 7: See where the time went
Under the animation the roam is split into its parts:
| Part | What it is |
|---|---|
| 802.11 authentication and reassociation | The client and the new AP saying hello |
| EAP / RADIUS | The login, checked with your RADIUS server |
| 4-way handshake | Agreeing the encryption keys |
In the sample's slow roam, 98% of the time is EAP / RADIUS. The Wi-Fi part took 4 ms. The other 421 ms was paperwork with the RADIUS server, which the client had to redo from scratch at every single AP.
The tool also calls out the longest wait in the roam and who everyone was waiting for, and it tells you if any frames had to be resent.

What the roam types mean
The tool names each roam so you know what you're looking at.
| Roam type | In plain English | Usually |
|---|---|---|
| 802.1X full | A complete login with the RADIUS server at every AP | Slow |
| 802.11r over the air | Fast roaming. The client talks straight to the new AP and the keys are ready in advance | Very fast |
| 802.11r over the DS | Fast roaming, but the client asks the new AP by way of the old one and the wired network | Fast |
| 802.1X with PMK caching | The client and AP remember each other from before and skip the login | Fast |
| PSK | A shared password. No RADIUS, just the 4-way handshake | Fast |
| SAE (WPA3-Personal) | The WPA3 version of a shared password | Fairly fast |
| Open / Enhanced Open | No login at all | Fast |
For 802.11r over the DS you get two times: from the Reassociation Request, and from the FT Action Request that came before it by way of the old AP.
Here's the same kind of walk on a network with 802.11r switched on. Three roams, all comfortably inside the target.


429 ms down to 6 ms. Pretty cool, right?
Step 8: Change the target
Why 150 ms? It's my target for a roam you won't notice on a call. But some apps need tighter, and your voice vendor may quote their own number.
So change it. Drag the slider or type a number, anywhere from 10 to 1,000 ms. Every verdict, the scoreboard and the call bubble update straight away.

Step 9: Take the results with you
At the bottom there are two buttons:
- Copy results gives you a plain text summary to paste into an email or a report.
- Download CSV gives you a row per roam for a spreadsheet.
Both use the names you gave things, and both keep the MAC addresses too.
When the tool won't give you a number
Captures are never perfect. Frames get missed. When that happens, the tool says so instead of making something up.
- The client's first frame is missing. You still get a time, with a note that the real roam was a touch longer.
- The last frame is missing. No time. It tells you which frame it couldn't find.
- It's a wired capture. It tells you, and asks for a wireless one.
- There are no roams. It tells you the client stayed on one AP for the whole capture.
- The login failed or the AP said no. It names that, and doesn't time it.
A number you can't trust is worse than no number. Somebody's going to put this in a report.
It works on a phone too
Desktop is the best way to use it, but it works on a phone if that's what you've got in your hand on site.

So your roams are slow. Now what?
If the tool shows 802.1X full roams with most of the time in EAP / RADIUS, the fix is usually 802.11r. It lets the client skip the login at every AP.
Don't get me wrong, it isn't a switch you flip without checking. Not every client supports 802.11r, and some older ones get upset when they see it. Check your clients first, turn it on, then capture again and measure the difference. That before and after is exactly what this tool is for.
And if the roams are fast but users still complain? Then it's not the roam itself. Look at when the client decided to roam, and what it roamed to. That's a design and coverage conversation, and one for another post.
Questions people ask
Is my capture uploaded anywhere?
No. It's read in your browser and never sent. The page is locked down so the browser itself would block an upload. Close the tab and it's gone.
Which capture formats work?
pcap and pcapng from Wireshark, OmniPeek .pkt, and gzipped versions of those. Anything else: open it in Wireshark and save it as pcapng.
Do I need the Wi-Fi password to decrypt the capture?
No. The tool only reads frame headers and the unencrypted management and login frames. It never tries to open your data.
How big a capture can it handle?
Up to 500 MB. If yours is bigger, filter it in Wireshark first with wlan.addr == and your client's MAC address, then save the result.
Why does it say the client was mostly idle?
Because it wasn't sending much either side of the roam, so the data to data time is mostly waiting. For a true user's-eye number, capture while the client is on a call or streaming something.
Why is the roam shown as incomplete?
Frames are missing from the capture. The most common reason is that the capture only heard one of the two channels.
Have a go
Open the Roaming Calculator, load a capture (or the sample), and see how fast your clients really roam.
If it finds something surprising on your network, tell us. We'd love to hear about it.
Roam sweet roam.
