Skip to content

Fix vmnet VPN external interface refresh#1666

Open
0xMH wants to merge 2 commits into
apple:mainfrom
0xMH:fix/1519-vpn-utun-nat
Open

Fix vmnet VPN external interface refresh#1666
0xMH wants to merge 2 commits into
apple:mainfrom
0xMH:fix/1519-vpn-utun-nat

Conversation

@0xMH

@0xMH 0xMH commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update

Motivation and Context

Fixes #1519.

I dug into this issue a bit and found that containers could not reach addresses behind a VPN connection because the vmnet NAT network was created against the host network state at startup, but was not refreshed when VPN interfaces/routes changed. As a result, container traffic continued using stale vmnet NAT/routing state and failed to reach VPN-only destinations.

This change refreshes reserved vmnet NAT networks when host network state changes, configures vmnet with an active point-to-point tunnel interface when present, and updates the network allocator if vmnet selects a new subnet during refresh.

Testing

  • Tested locally
  • Added/updated tests
  • Added/updated docs

@0xMH 0xMH force-pushed the fix/1519-vpn-utun-nat branch from 089f4e1 to 91993c3 Compare June 8, 2026 21:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Hosts behind OpenVPN (Tunnelblick) not reachable from container

1 participant