Skip to content
How to set up a VPN on Mac: The MacBook settings that actually matter

How to set up a VPN on Mac: The MacBook settings that actually matter

How to set up a VPN on Mac: The MacBook settings that actually matter

Installing a VPN on Mac takes two minutes. Configuring it so macOS can’t quietly route traffic around the tunnel takes longer, and most MacBook owners never get there.

Mac App Store vs. Direct Download: Same VPN, Different App

Search the Mac App Store for any major VPN and it will be there. Go to the provider’s own site and there is often a second build of the same product, with a different installer and, in many cases, a longer settings menu.

The difference comes from Apple’s rules. Apps sold through the Mac App Store run inside a sandbox and must handle networking through Apple’s Network Extension framework, which limits what they can touch. A build distributed directly can install a privileged helper, write its own firewall rules and offer things the sandboxed version can’t ship: per-app split tunneling, custom DNS, extra protocols, or a firewall-based kill switch that keeps working when the tunnel drops.

For a personal MacBook, the direct download is usually the better pick. The App Store version makes sense on a managed work machine where IT blocks outside installers, and almost nowhere else.

Choosing the service comes first, obviously. Gizmodo’s editors put more than 30 VPNs through a macOS test bench, measuring speed loss, split tunneling and streaming access, and kept five; their picks for Mac are a reasonable shortlist before touching any of the settings below. One finding from that work lines up with the point above: the App Store build of some of those apps lacks features the website version includes.

The VPN Kill Switch Has a Blind Spot Called Sleep

A kill switch blocks internet traffic whenever the VPN connection drops. On paper, it’s the setting that matters most. On a MacBook, it’s also the one most likely to fail without anyone noticing.

Laptops change state all day. The lid closes, the Mac sleeps, Wi-Fi hands off from the office network to a phone hotspot, and the tunnel has to rebuild every single time. Apple gives VPN developers a flag called includeAllNetworks that forces all traffic into the tunnel, and developers have spent years on Apple’s own forums documenting how it misbehaves during network changes, sometimes knocking the Mac offline instead of rerouting it. Some apps rely on that flag alone. Others add macOS’s built-in packet filter as a second layer. Users rarely know which approach their app takes.

Then there’s the window nobody fully closes: the seconds between boot and the moment the VPN app starts. Anything that syncs at login (iCloud, Mail, a cloud drive client) can reach the network before the tunnel exists. Setting the app to launch at login and connect automatically shrinks that window. An always-on or “block traffic when disconnected” mode, where the app offers one, shrinks it further.

Testing takes thirty seconds. Connect, check the public IP on any lookup site, switch Wi-Fi networks, refresh. If the real address shows up even once, the kill switch isn’t doing its job.

What TunnelCrack Revealed About MacBooks on Public Wi-Fi

In August 2023, researchers from New York University and KU Leuven presented TunnelCrack at USENIX Security. After testing more than 66 VPN products across five platforms, they found that every VPN client on macOS except one could be pushed into leaking traffic outside the tunnel by a malicious Wi-Fi network. The technique, which they called LocalNet, abuses the exception most VPNs make for local traffic. A rogue hotspot (cloning a coffee chain’s network name is enough) hands out public IP ranges as if they were local, and the Mac sends that traffic in the clear. The full list of affected clients sits on the TunnelCrack research page.

Nine months later, in May 2024, Leviathan Security Group disclosed TunnelVision (CVE-2024-3661), which abuses DHCP option 121 to push rogue routes onto a connected device. macOS made the affected list. Android, which ignores that DHCP option, didn’t.

Plenty of providers have patched since. The user-side fix is still worth applying: switch off the setting usually labelled “Allow LAN access” or “local network sharing” whenever the MacBook joins a network you don’t control. Hotel, airport, café, conference hall. That single toggle removes the opening the public Wi-Fi attack depends on.

Split Tunneling Without Losing the Printer or the NAS

Blocking the local network has a cost at home. Printers, NAS drives, smart speakers and screen mirroring to a TV all live on the LAN, and a strict setup makes them disappear. Since macOS Sequoia, apps also need explicit permission to reach local devices, which means one more prompt to approve (or accidentally deny) under Privacy & Security in System Settings.

Split tunneling is the better answer, and it’s the most underused feature in Mac VPN apps. Route the browser, mail and messaging through the tunnel; let a video call app, a game launcher or a local backup tool go direct.

The pattern that works on a MacBook is two profiles. At home: LAN access on, generous exclusions. On the road: LAN access off, nothing excluded. Some apps can tie each profile to specific Wi-Fi networks so the switch happens on its own, and anyone whose app offers that should use it.

WireGuard, IKEv2 or Automatic on Apple Silicon?

Protocol menus look intimidating and matter less than they used to. On M-series MacBooks, WireGuard and the proprietary protocols built on it are light on battery and quick to reconnect after sleep, which ties straight back to the kill switch problem. IKEv2 copes well with network handoffs too, and macOS supports it natively. OpenVPN over TCP port 443 is the fallback for hotel or corporate networks that block everything else: slower, but harder to filter.

“Automatic” is fine if the app says what it picked. If it doesn’t, choose a WireGuard-based option by hand and leave it alone.

Apple Has Broken This Before

When macOS Big Sur shipped in November 2020, researchers including Patrick Wardle found a file called ContentFilterExclusionList that let more than 50 of Apple’s own apps (the App Store, Maps, FaceTime, Music) bypass third-party firewalls and VPNs. Someone connected to a VPN was still exposing a real IP address every time one of those apps went online. Apple removed the list in the macOS 11.2 beta in January 2021, after weeks of bad press.

That list is long gone. The episode still shows where the real ceiling sits: a VPN on a Mac can only be as tight as the operating system allows, and major macOS releases regularly change how network extensions behave. So the thirty-second Wi-Fi test isn’t a one-time check. It belongs on the to-do list for the day each new macOS version lands, right after fixing whatever else the update broke.

Author

Madhurima Nag

Madhurima Nag is the Head of Content at Gadget Flow. She side-hustles as a parenting and STEM influencer and loves to voice her opinion on product marketing, innovation and gadgets (of course!) in general.

Be the first to comment

Latest
Your Comment..
Sign up to leave a comment.

Your comment and username are shown publicly. Privacy Policy

Click here to tag users that participate in this comment thread.
Click here to upload an image or gif.
Click or drag your image here (Maximum Size 4MB, Accepted formats JPG, PNG, GIF).
Add an emoji to your comment.
Click here to add a gif from Giphy.com to your comment.
Search
powered by Giphy