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
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), 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
en0or 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.
- Hardware: Physical network interfaces on your Mac (such as Wi-Fi
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 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
Hardwareinterface 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) and request an administrator TLS inspection 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.