Airport Wi-Fi: timers, sign-in portals and the walk to the gate

Most free terminal Wi-Fi is metered by time rather than by data. Thirty minutes, sixty minutes, sometimes one session per device per day. When the allowance ends the network does not go quiet: it pushes you back to the sign-in page. Your device stays associated with the access point and keeps its address, so everything looks connected while nothing is being routed.

A VPN cannot talk its way past that, because the gateway has simply stopped forwarding and the tunnel has nowhere to send packets. The useful reflex is to read a sudden stall as a portal event first and an app problem second: open any ordinary web page, see whether the sign-in screen appears, finish it, then reconnect.

Terminal portals rarely offer a plain button. The common asks are an email address, a frequent-flyer number, the booking reference printed on your boarding pass, a phone number for an SMS code, or a social login. That page is served by the airport gateway itself, which means it is visible to the operator by design and sits outside any tunnel you bring up afterwards.

Order of operations is the whole trick: clear the portal over the open network, confirm that an ordinary page loads, then bring the tunnel up. The airport wrinkle is that you will do it more than once. When the session clock expires two gates later the portal comes back, and re-authenticating usually means supplying the same detail you gave the first time, so note down which one you used. Connecting before the portal has cleared, then wondering why the sign-in page will not load, is the mistake departures sees most.

In a large terminal the list of visible networks is long and unhelpfully similar. The airport service, one or two lounges, airline networks, retail and cafe hotspots, hotel shuttles idling outside, operational networks, and personal hotspots from the people in the next row of seats. Names differ by a hyphen, a single word, or nothing but capitalisation.

The dependable source for the right name is not the strongest signal. It is the airport's own signage at the gate or its website, which usually prints the service name exactly. Checking that once, before the first join, costs less than picking the wrong network and typing a booking reference into whatever asked for it.

Terminal coverage is a mesh of many access points rather than one radio. Walking from check-in to a far gate carries you across several of them, and the handover is not always clean: the device holds a weakening association too long, then switches, and the session is briefly interrupted even though the network name never changed. Long piers and moving walkways make it more obvious, because you keep travelling at a steady pace through the whole chain of cells.

This is where the protocol shows. The WireGuard handshake is a single round trip, so when the path changes underneath a live connection, re-establishing it is one exchange rather than a drawn-out renegotiation. What you tend to notice is the app reporting a brief reconnect while you are still walking, instead of a download that has quietly died.

Terminal capacity is shared backhaul, and demand follows the departure board. A bank of flights boarding together puts several hundred people on the same access points, every one of them refreshing gate information or starting something to watch on the flight. Throughput falls for everybody on that cell, tunnel or no tunnel.

Encryption does not create capacity, and no setting will. What does help is choosing a region close to where you are sitting, so the encrypted leg is short and requests are not making an unnecessary intercontinental hop before they start. The region list shows live latency, which is the number worth reading in a busy terminal: take the lowest one near you and stop tuning.