Why two laptops on an iPhone hotspot can't talk

2026/04/07
networkhotspotiosap-isolation

Two laptops on the same WiFi. You find each other's IP with ifconfig. You run nc. It works.

Two laptops on the same iPhone hotspot. Same steps. Nothing.

I assumed a hotspot was just a small WiFi router. So why do the same steps fail?


The setup that works

Home WiFi. Two laptops on the same network.

Laptop A (192.168.0.2) ──┐
                          ├── WiFi Router ── Internet
Laptop B (192.168.0.3) ──┘
# Laptop A
nc -l 5000
 
# Laptop B
nc 192.168.0.2 5000

Works. The router forwards packets between devices on the same subnet. Standard LAN.

The setup that doesn't

iPhone hotspot. Two laptops connected.

Laptop A (172.20.10.2) ──┐
                          ├── iPhone (172.20.10.1) ── Carrier ── Internet
Laptop B (172.20.10.3) ──┘
nc -l 5000
nc 172.20.10.2 5000

Silence. The connection times out. Same subnet. Same command. Doesn't work.


The cause: AP isolation

This is AP isolation: the AP (Access Point, here the iPhone) refuses to forward packets between connected clients. Each laptop can reach the phone, and through the phone the internet. They cannot reach each other.

Laptop A → iPhone → Internet     ✓
Laptop B → iPhone → Internet     ✓
Laptop A → iPhone → Laptop B     ✗

Tested in November 2026 on an iPhone hotspot running iOS 26.6.2: one laptop ran an HTTP server, the other tried to reach it, and the server received no request; its log stayed empty. The same two laptops on home WiFi connected fine.

On WiFi, Laptop A's frame for Laptop B goes to the phone first. With isolation, the phone drops it there; it never reaches the carrier or passes through NAT.

Apple does not document this behavior. In 2017 an Apple engineer on the developer forums wrote that, as far as he knew, Personal Hotspot did not restrict client-to-client traffic, but that it was designed "solely" to connect clients to the internet and he would not build a product on it. That was one engineer's understanding eight years ago, and the iOS 26.6.2 test above shows the opposite.

Why there is no switch

Apple has never said. My guess, three things stacked:

  1. Security by default. Coffee shop hotspot: random strangers should not be able to see each other's nc listeners.
  2. iPhone as client, not router. Apple's mental model is that the phone is a terminal device. Router features (port forwarding, DMZ, isolation toggle, QoS) are absent.
  3. Support cost. Fewer knobs, fewer tickets.

No user setting. Apple's NEHotspot APIs are for joining Wi-Fi networks. Apple's MDM schema has keys to turn Personal Hotspot on or off and to stop users changing it, and none for isolation.

Android varies by phone maker, and Android's public hotspot API has no isolation setting either. On iOS there is no user toggle.

The workaround: Tailscale

The cleanest way around this is an overlay VPN. Tailscale is the default recommendation.

# Both laptops
brew install --cask tailscale
# Open the app, log in to the same account on both

Each laptop gets a Tailscale IP (100.x.x.x). Use those to reach each other:

# Laptop A
nc -l 5000
 
# Laptop B (use Tailscale IP, not the hotspot's 172.20.10.x)
nc 100.64.1.5 5000    # works

Why it works: Tailscale runs at L3 on top of the internet. Both laptops reach out through the iPhone's NAT to Tailscale's coordination server, which hands each laptop a list of the other's addresses. Tailscale tries each for a direct WireGuard connection. The 172.20.10.x address still goes through the phone, where isolation would drop it. The public IP and port belong to the same iPhone NAT both laptops sit behind, so the NAT has to turn Laptop A's packet around to Laptop B. That is called hairpinning.

Some NATs hairpin and some don't; Apple doesn't say which kind the iPhone is, and this was not tested. If it doesn't, Tailscale falls back to its DERP (Designated Encrypted Relay for Packets) relay servers. Either way, Laptop A no longer sends straight to Laptop B's 172.20.10.x.

The irony: your two laptops sitting a foot apart may now be talking through a relay server somewhere on the internet. It still works.

Alternatives if Tailscale is off the table:

  • A small travel router. Use the iPhone as WAN (USB tether or client WiFi), let the travel router be the real AP. Laptops connect there, free to talk.
  • USB tether one laptop, then have it share its connection as a WiFi hotspot to the other laptop. That laptop becomes the router.

Both work but require extra hardware or awkward config.

Summary

WiFi routeriPhone hotspot
Devices can talk to each otherAP isolation blocks device to device
Router forwards LAN trafficPhone refuses to forward LAN traffic
You control the configApple decided for you

An iPhone hotspot looks like a small router, but it was built to get connected devices online. Apple promises nothing about devices reaching each other. If you need two laptops to actually talk while tethered, you route them through the internet via Tailscale. Apple didn't leave a door; you build one.