Skip to content

proxy: add built-in NAT46 and managed DNS64 - #169

Merged
Cd1s merged 5 commits into
mainfrom
feat/proxy-nat46
Oct 25, 2026
Merged

Cd1s merged 5 commits into
mainfrom
feat/proxy-nat46

Conversation

@Cd1s

@Cd1s Cd1s commented Oct 25, 2026

Copy link
Copy Markdown
Owner

What

  • Add proxy.nat46 with an embedded SOCKS5 NAT46 converter supporting TCP CONNECT and UDP ASSOCIATE, source suffix/full IPv6 usernames, hot-reloaded source tables, safe destination rejection, and loopback-only validation.
  • Manage mr-nat46 and the optional mr-dns64 OpenRC services from mr apply, including doctor service health/healing and generated configuration.
  • Add a private unbound DNS64 instance under proxy.nat46.dns64 that follows healthy WAN IPv4 DNS, validates/reloads forwarders, and leaves system unbound untouched.
  • Add proxy UI controls, English translations, lab coverage, tests, and NAT46/DNS64 documentation with the unchanged proxy.extra_config wiring.

Why

sing-box 1.14 does not synthesize NAT64 addresses for IPv4 literals. The router's existing per-port proxy nodes therefore need a built-in converter and DNS64 resolver so the external nat46-socks, system unbound, and isp-dns.sh can be retired without changing the user's proxy extra configuration.

Verification

  • cd mr && go vet ./...
  • cd mr && go test -count=1 ./...
  • python3 tools/i18n.py check
  • sh tools/ci.sh — ALL CHECKS PASSED
  • OpenRC scripts pass sh -n; real DNS64 resolution was not run because this build host does not have /usr/sbin/unbound.

Closes #168

@Cd1s
Cd1s merged commit dbaa9bc into main Oct 25, 2026
2 checks passed
@Cd1s
Cd1s deleted the feat/proxy-nat46 branch October 25, 2026 12:32
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.

proxy: integrate NAT46 SOCKS and managed DNS64

1 participant