DHCP & DNS gateway
Start with selected-device bypass routing, take over LAN DHCP when you are ready, or serve an isolated downstream network.
Explore gateway modesOpen source · macOS 13+
OpenSurge is a Surge-style macOS gateway and control plane powered by mihomo. Route phones, TVs, consoles, and other devices through one observable, recoverable network path.
Free and open source · Apple Silicon and Intel · unsigned packages

NETWORK CONTROL, NOT APP SETTINGS
Devices such as game consoles and TVs cannot run the same proxy client as a Mac. OpenSurge moves routing policy to the Mac gateway so downstream devices use ordinary IP networking.
Start with selected-device bypass routing, take over LAN DHCP when you are ready, or serve an isolated downstream network.
Explore gateway modesGive a phone, TV, PS5, or VR headset a dedicated selector while keeping local and private traffic direct.
See device policyImport compatible proxies and rules while OpenSurge retains ownership of gateway-critical DNS, TUN, and recovery state.
Understand the architectureSTART SMALL, SCALE DELIBERATELY
The setup changes with the network you actually control. OpenSurge explains the operational impact before it changes DHCP, routes, or advertisements.
Keep router DHCP. Manually point selected stable devices at the Mac.
Disable router DHCP and let OpenSurge provide device network settings.
Use a separate AP, SSID, VLAN, or interface behind the Mac.

ONE ENGINE, DEVICE-SCOPED POLICY
OpenSurge compiles stable device identity into source-scoped mihomo rules. Mac-local mode stays independent, and the connection view shows the outbound chain that traffic actually used.
Read the PS5 gateway guideWIND ROSE · EXPERIMENTAL IPV6
IPv4 and Mac-local traffic use mihomo TUN. Experimental downstream IPv6 uses RA/SLAAC/RDNSS plus a macOS BPF broker and the project-patched mihomo userspace packet path—without claiming the packets entered utun.
Explore the IPv6 architecture
BUILT FOR NETWORKS THAT MUST RECOVER
Unit tests protect business rules. Virtual LAN labs exercise DHCP, DNS, TUN, NAT, rollback, and topology-specific IPv6 paths. Public claims stay bounded by the evidence that was actually collected.
Inspect the Virtual LabStart with one device, verify the path, and expand only when the topology is ready.