Source: https://swgbar.com/en/guides/macos-vpn-virtual-interface-vs-swg-inspection/
Language: en

# macOS VPN virtual interfaces vs. SWG HTTPS inspection

Understand how VPN tunnels (Virtual egress interfaces) interact with SWG HTTPS decryption on macOS, how to read Egress interface details, and when bypass requires Hardware IPv4.

SWG bar · Updated November 18, 2026

Many corporate Macs run both a **VPN or Zero Trust client** and **SWG HTTPS inspection** at the same time. Because both tools sit in the network stack, it is easy to confuse encrypted VPN tunneling with TLS interception—or wonder why **Bypass SWG** behaves differently when a full-tunnel VPN is active.

## Separate VPN tunneling from HTTPS break-and-inspect

A VPN changes **which network interface and IP tunnel** carries your packets, whereas SWG HTTPS inspection changes **whether TLS is decrypted and re-signed** along the path:

| Behavior | Standard VPN tunnel (no TLS interception) | Enterprise SWG with HTTPS break-and-inspect |
| --- | --- | --- |
| **What it modifies** | Routes IP packets through a `Virtual` tunnel interface (`utun*`). | Terminates TLS and re-signs site certificates with a local root CA. |
| **TLS certificate seen by Mac** | Origin server’s **Public trust path** certificate chain. | Re-signed certificate signed by the corporate inspection root CA (**Confirmed** / **Suspected**). |
| **Can both happen together?** | Yes—many SASE/Zero Trust agents send traffic over a `utun` tunnel to a cloud SWG that also decrypts HTTPS. | Yes—both `Virtual` egress and a local inspection root appear together in SWG bar. |

## Read Network information in SWG bar Domain details

When you open any hostname in **SWG bar → Domains** (or run `swgbar domains detail <domain>` via the [CLI](<https://swgbar.com/en/cli/>)), look at the **Network information** section:

*   **Target address**: The destination IP observed for the hostname (helps separate internal private IPs from public endpoints).
*   **Egress interface**:
    *   **Hardware**: Physical network interfaces on your Mac (such as Wi-Fi `en0` or wired Ethernet).
    *   **Virtual**: Virtual tunnel interfaces (such as `utun*` created by WireGuard, OpenVPN, Tailscale, or enterprise Zero Trust/SWG tunnel agents).
    *   **Unknown type**: Interface classification could not be determined from the available metadata.

Remember that SWG bar’s TLS probe opens an independent IPv4 TCP connection and does not replicate every application’s custom proxy, IPv6, or QUIC behavior. See [how SWG bar works](<https://swgbar.com/en/how-it-works/>) for details.

## How VPN virtual interfaces affect SWG bypass

SWG bar 2.4.12’s **Bypass SWG** routes new connections for the selected hostname directly through a **connected physical (`Hardware`) interface with an available IPv4 gateway**. That design has practical implications when a VPN is active:

*   **Split-tunnel or local Wi-Fi/Ethernet available**: Bypass sends the selected hostname over your physical `Hardware` interface while leaving other hosts untouched.
*   **Strict full-tunnel VPN or firewall blocking direct physical egress**: If no physical IPv4 gateway is reachable—or corporate firewall policy blocks direct outbound TCP outside the tunnel—SWG bar shows an error such as `"No connected physical interface with an IPv4 gateway"` or `"Physical connection failed; bypass has not been verified"`.

If direct physical routing is blocked on your network, disable the domain bypass rule (see [Troubleshoot Recovering & Paused states](<https://swgbar.com/en/guides/troubleshoot-swg-bypass-recovering-paused-macos/>)) and request an administrator [TLS inspection exception](<https://swgbar.com/en/guides/swg-bypass-vs-tls-exception/>) so traffic stays on the corporate tunnel without HTTPS decryption.

## Re-test after toggling VPN or switching networks

Because changing Wi-Fi networks or connecting/disconnecting a VPN alters your Mac’s routing table, earlier observations may reflect the previous path—and SWG bar may clear detection history on network changes. Run `swgbar probe <domain>` or reopen the connection after switching networks so you compare fresh certificate evidence against the active **Egress interface**.

## Keep reading

*   [How to Bypass SWG on a Mac (One-Click Domain Bypass & CLI)](<https://swgbar.com/en/guides/how-to-bypass-swg/>)
*   [How to Bypass SSL Inspection on a Mac (Corporate SWG & Per-Domain Fix)](<https://swgbar.com/en/guides/bypass-ssl-inspection-mac/>)
*   [How to Bypass HTTPS & TLS Inspection on macOS (Break-and-Inspect Guide)](<https://swgbar.com/en/guides/bypass-https-tls-inspection-mac/>)
*   [How to Bypass Corporate Proxy & SWG SSL Inspection on a Mac](<https://swgbar.com/en/guides/bypass-corporate-proxy-ssl-inspection-mac/>)
*   [How to tell if your Mac is intercepted by an SWG (HTTPS & SSL inspection)](<https://swgbar.com/en/guides/detect-https-inspection/>)
*   [How to Check if Your Employer or Work Mac Is Intercepting HTTPS (SSL Inspection)](<https://swgbar.com/en/guides/check-if-work-mac-intercepting-https/>)
*   [SSL Inspection Checker for Mac: Menu Bar Tool to Detect HTTPS Interception](<https://swgbar.com/en/guides/ssl-inspection-checker-mac/>)
*   [Zscaler SSL Inspection on Mac: How to Check & Bypass per Domain](<https://swgbar.com/en/guides/zscaler-ssl-inspection-bypass-mac/>)
*   [Netskope SSL Inspection on Mac: Check Decryption & Bypass per Domain](<https://swgbar.com/en/guides/netskope-ssl-inspection-bypass-mac/>)
*   [Cloudflare WARP & Zero Trust TLS Inspection on Mac: Detect & Bypass](<https://swgbar.com/en/guides/cloudflare-warp-tls-inspection-mac/>)
*   [Confirmed vs. Suspected HTTPS inspection in SWG bar](<https://swgbar.com/en/guides/confirmed-vs-suspected-https-inspection/>)
*   [Inspect MITM root certificates & issuers in SWG bar](<https://swgbar.com/en/guides/inspect-mitm-root-certificates-macos/>)
*   [Enterprise SWG & MDM HTTPS inspection on a Mac](<https://swgbar.com/en/guides/enterprise-swg-https-inspection-macos/>)
*   [SWG bypass vs. TLS inspection exception (break and inspect)](<https://swgbar.com/en/guides/swg-bypass-vs-tls-exception/>)
*   [Bypass SWG for multi-domain web apps, SSO, CDNs & APIs on Mac](<https://swgbar.com/en/guides/multi-domain-sso-api-cdn-swg-bypass/>)
*   [Fix SWG bypass Recovering, Paused & connection errors on Mac](<https://swgbar.com/en/guides/troubleshoot-swg-bypass-recovering-paused-macos/>)
*   [Why certificate-pinned apps & mTLS break under SWG inspection](<https://swgbar.com/en/guides/certificate-pinning-mtls-swg-inspection-macos/>)
*   [Fix SWG TLS & SSL certificate errors in CLI and AI tools on a Mac](<https://swgbar.com/en/guides/swg-tls-certificate-errors-macos/>)
*   [Homebrew, Docker, Python & Node.js CA trust behind an SWG on Mac](<https://swgbar.com/en/guides/homebrew-docker-python-node-ca-trust-swg-macos/>)
*   [Fix Claude Code & Cursor 'unable to get local issuer certificate' on Mac (SWG & MCP)](<https://swgbar.com/en/guides/ai-coding-agents-claude-code-cursor-swg-macos/>)
*   [Verify TLS certificates with openssl & security verify-cert on Mac](<https://swgbar.com/en/guides/verify-tls-certificates-openssl-security-verify-cert-macos/>)
*   [SWG bar permissions, local privacy & TLS probe limits](<https://swgbar.com/en/guides/macos-network-extension-privacy-probe-limits/>)
*   [How SWG bar checks HTTPS inspection](<https://swgbar.com/en/how-it-works/>)
*   [Download & install SWG bar for Mac (macOS 14+)](<https://swgbar.com/en/install/>)
*   [Chrome Extension to Detect SSL & HTTPS Inspection (SWG Bar Companion)](<https://swgbar.com/en/chrome-extension/>)
*   [SWG bar CLI Guide](<https://swgbar.com/en/cli/>)
*   [SWG bar MCP Guide](<https://swgbar.com/en/mcp/>)
*   [SWG bar release information](<https://swgbar.com/en/releases/>)
*   [About SWG bar](<https://swgbar.com/en/about/>)
