Summary
For years, I figured the tiny “i” next to my network name in Settings > Wi-Fi on my iPhone was for looking up details, not fixing anything. You tap it when you need your IP address (which you can change) for something else, then close the screen without reading past it. It sits between the toggle and forget-network, and I must have tapped past it 100 times without ever reading what was on it. Then my phone started acting as if it had never joined my router before, on a network it had connected to for years without issue. I finally tapped that “i” mostly because I’d run out of other things to try, and actually read what was on the screen. Private Wi-Fi Address. On by default. Explained in one line of gray text I’d never bothered reading. I’d been blaming my router for months. What actually happens when you tap that “i” Your phone has two addresses now Every Wi-Fi radio has a MAC address, a hardware identifier burned into the chip at the factory. It doesn’t normally change over the life of a given device. For most of Wi-Fi’s history, your phone hands that same address to every network it touches: home, the coffee shop, the airport, all seeing the identical string. Apple started messing with that in iOS 8, randomizing the address your phone broadcasts while it scans for networks it hasn’t joined yet. iOS 14 went further: your phone now generates a separate private address for every network you connect to by default, with the real hardware MAC hidden underneath. A few newer iOS versions add another layer, letting you pick between a private address that stays fixed on a given network or one that keeps rotating even there. Open Settings > Wi-Fi, tap “i” next to your current network. The toggle is right there under “Private Wi-Fi Address,” switched on, and you probably never touched it. Why Apple hides your real MAC address in the first place The tracking problem nobody told you about MAC addresses turned into a tracking tool almost by accident. Retailers put Wi-Fi sensors in stores to see which shoppers walked past which aisles, reading nothing more than the network probes phones send out automatically while hunting for known networks, and there’s no login or loyalty card needed. Airports and train stations used the same setup to time how long lines took to move, and none of it required you to join a network. Turning on Wi-Fi while you walked past a sensor was enough. Apple’s fix is to stop handing out the real address by default, everywhere. When that privacy feature fights your own network The symptom that finally clicked for me A lot of home networking still assumes a device’s MAC address never changes. I’d set a static IP reservation on my router for my phone, mainly so a couple of smart home routines could always find it, and it worked for a while before it just stopped, with no obvious reason. I only caught it because I happened to be poking around my router’s admin panel for something else, checking the connected-devices list, and kept seeing a new client pop up right around when my phone would’ve reconnected. Different address every time. I lined the timestamps up against my own phone use, and it was the same device, just showing up as brand new each time instead of picking up the reservation that was already sitting there waiting for it. Routers with MAC filtering run into the same wall, and so do static DHCP setups and captive portals at hotels, dorms, and offices that authenticate a session by device address instead of a persistent login. If you’ve had to log back into the hotel’s Wi-Fi every couple of hours for no obvious reason, that’s very likely what’s going on behind the scenes. Go to Settings > Wi-Fi, tap the “i” next to a specific network, and turn off Private Wi-Fi Address for that network. Your phone will then use the same address there every time, which is what fixed my reservation. Do this for networks you trust and control where a fixed address actually matters; your own router or a work network with MAC filtering are the obvious cases. It’s also worth doing on a captive-portal network you’re stuck with for a while, a hotel or conference Wi-Fi you’ll be reconnecting to for days. Those often re-authenticate you by device address, so a private address that keeps rotating is exactly why you keep getting sent back to the login page. Turning it off for that one network for the length of your stay can fix it, and the privacy trade-off is small, since you’re not on that network long-term anyway. For open, often free Wi-Fi connections with no login screen, there’s no reason to touch the setting there. Leave Private Wi-Fi Address on, especially for networks you don’t control and won’t be returning to. What to actually do about it If your phone keeps dropping off your home network, losing a static IP reservation, or failing a MAC filter it should pass, check the Private Wi-Fi Address before you blame the router or the Wi-Fi hardware. Keep it on for public and unfamiliar networks. Turn it off on a network only if you actually need a fixed address there, for a reservation or a filter that depends on one. My own troubleshooting took weeks. I checked cables, reset the router twice, and didn’t think to open that “i” screen until pretty much everything else had failed.