Import the ecosystem, retain gateway ownership

OpenSurge can import compatible mihomo profile sections for proxies, groups, providers, and rules. It deliberately retains ownership of gateway-critical DNS, TUN, controller, and listener fields so an imported subscription cannot silently redefine the network lifecycle.

One engine, several responsibilities around it

The control plane starts and validates processes, generates device overlays, monitors policy groups and providers, correlates connections with LAN identity, and guides network recovery. Those responsibilities are outside the scope of an ordinary profile editor.

  • TUN-based transparent routing on supported macOS paths.
  • DHCP/DNS coordination through dnsmasq.
  • pf NAT and IPv4 forwarding lifecycle management.
  • Per-device selectors and rule overrides.
  • Web GUI, menu bar status, diagnostics, and recovery.

Compatibility still depends on the source profile

A node protocol name alone is not a guarantee. UUIDs, transport and TLS parameters, rule providers, and server-side settings still need to match. OpenSurge validates the composed runtime configuration before applying it.

FAQ

Questions people ask before changing the network

Is OpenSurge a fork of mihomo?

OpenSurge is a separate macOS gateway and control-plane project. It embeds a project-built mihomo engine and maintains a narrow patched packet listener for the experimental downstream IPv6 data path.

Can I import an existing subscription?

Yes, when it is compatible with the mihomo configuration format. OpenSurge imports policy content while preserving fields that belong to gateway safety and lifecycle management.