Big Sur VPN Issues?

Common Problems and Fixes

SplitTunnel Team·5 min read·Updated January 2026

Key Takeaways

  • Big Sur changed how VPNs work—Network Extensions replaced Kernel Extensions

  • Many VPN issues stem from outdated clients that don't support the new APIs

  • Most issues are resolved by updating VPN client to a Big Sur-compatible version

What Changed in Big Sur for VPNs

macOS 11 Big Sur introduced major architectural changes that affected VPN compatibility. Understanding these changes helps explain why your VPN may have stopped working.

  • Kernel Extensions (KEXTs) deprecated in favor of Network Extensions

  • New security requirements for system extensions

  • Changes to how apps interact with network stack

  • ContentFilterExclusionList (Apple apps bypassing VPN)

Common Big Sur VPN Issues

  • VPN client won't install or crashes

  • "System Extension Blocked" errors

  • VPN connects but no traffic flows

  • Apple apps bypass VPN unexpectedly

  • DNS resolution fails while connected

  • Slow VPN performance

The Network Extension Transition

Before Big Sur, VPNs used Kernel Extensions (KEXTs) that ran with high privileges in the macOS kernel. Apple deprecated these for security reasons.

New VPNs use Network Extensions—sandboxed, more secure, but requiring vendors to rewrite their software. Many VPN vendors were slow to adapt.

If your VPN worked before Big Sur and stopped after upgrading, an outdated client is likely the cause.

Fixing "System Extension Blocked"

  1. Open System Preferences → Security & Privacy

  2. Click the lock icon and authenticate

  3. Look for message about blocked system extension

  4. Click "Allow" next to your VPN

  5. Restart your Mac

  6. Try connecting to VPN again

Apple Apps Bypassing VPN

Early Big Sur versions had a ContentFilterExclusionList that let Apple apps bypass VPNs and firewalls. This was controversial and partially addressed in later updates.

Update to Big Sur 11.4 or later to get fixes for the ContentFilterExclusionList issue.

Fixing DNS Issues

VPN may connect but fail to resolve domain names. Check your DNS configuration:

bash
# Check current DNS servers
scutil --dns | grep nameserver

# If empty or wrong, VPN didn't set DNS correctly

You may need to manually set DNS or update to a VPN client version that handles Big Sur DNS properly.

Updating Your VPN Client

Most Big Sur VPN issues are solved by updating to a compatible client version:

  • Cisco AnyConnect: Version 4.9 or later

  • GlobalProtect: Version 5.1 or later

  • OpenVPN Connect: Version 3.2 or later

  • Tunnelblick: Version 3.8.4 or later

  • WireGuard: Native macOS app (built for Big Sur)

Remove the old VPN version completely before installing the update. Leftover kernel extensions can cause conflicts.

When VPN Updates Aren't Enough

Sometimes updating the VPN client isn't possible—corporate VPNs are controlled by IT, and they may be slow to push updates.

Options if you're stuck:

  • Request IT update the VPN client deployment

  • Check if a newer client is available for manual install

  • Consider upgrading to macOS 13.5+ for better VPN compatibility

  • Use SplitTunnel on macOS 13.5+ for per-app VPN control

Considering macOS Monterey or Later

macOS 12 (Monterey) and later refined the Network Extension APIs, improving VPN compatibility. If you're still on Big Sur and facing persistent VPN issues, upgrading may help.

On macOS 13.5+, SplitTunnel provides per-app VPN control using Apple's modern Network Extension framework—letting you route specific apps through or around your VPN.

Frequently Asked Questions

Per-App VPN on macOS 13.5+

Upgrade to Ventura or later and get full per-app VPN control with SplitTunnel.

Requires macOS 13.5 (Ventura) or later