Network inspector and timeline

Everything the phone sends and receives passes through Vetro's own network card, so Vetro sees it without installing anything in the phone and without the apps being able to notice. The Network and Timeline tabs show it: open Tools, the small toggle below the phone screen, to see them.

What the phone's network is

The phone believes it is on a normal network (address 10.0.2.15, with a gateway and a DNS server). Behind it, Vetro's own network stack, inside the emulator, answers it, and from there the traffic goes one of two ways.

Online, with Vetro Connect. While Vetro Connect runs on your computer, the phone reaches the internet through it: a small program that opens the real connections, because a browser page cannot. Apps load, web pages open.

Offline (the sinkhole), when Vetro Connect is not running. Nothing leaves your browser:

This keeps the phone completely isolated, which is useful for analysis; apps that need their server will show an offline or error message. Add ?net=offline to the app's address to start that way even while Vetro Connect is running.

The Network tab

The Network tab, with the system's own connectivity check

Right after start-up you will typically see the system checking whether it is online (its connectivity check): answered by the real server when the phone is online, by the sinkhole when it is offline.

Each row is one request: when it started, the method, the host and path, the response status, the sizes of the request and the response, the body type, the duration, and a waterfall bar that shows it in time.

The line on the right counts requests, DNS questions, TLS connections and frames.

Vetro also has hooks that read HTTPS traffic in clear text inside the TLS libraries, from the outside. They work in the command-line tools; bringing them to the page, together with a TLS endpoint for the sinkhole, is still in progress.

The Timeline tab

The timeline ties what you did to what happened next.

The Timeline tab

Time on the timeline is the phone's own clock (guest time), which advances with the instructions the phone executes, so it is the same on a fast and a slow computer.

Each effect is attributed to the last input that came before it within the window (3 seconds by default; you can change it). This is a simple rule, not a proof: a request an app makes by itself, on a timer, may land on whatever you did just before it.