Skip to content

Remove lucky; LAN names with A + AAAA; router IPv6 source per WAN - #98

Merged
Cd1s merged 1 commit into
mainfrom
fix/lucky-edge-v6src
Sep 26, 2026
Merged

Cd1s merged 1 commit into
mainfrom
fix/lucky-edge-v6src

Conversation

@Cd1s

@Cd1s Cd1s commented Sep 26, 2026

Copy link
Copy Markdown
Owner

What

  • lucky removed — init scripts, services.lucky (an old config gets services.lucky: removed — use services.ddns and services.edge), web UI cards, image build (the binary is no longer installed), CI, docs. The built-in DDNS (提议:DDNS 内置到 mr(不常驻) #5) and reverse proxy (提议:内置 HTTPS 反向代理 + 自动证书(mr-edge,DNS-01) #6) replace it: about −10 MB rootfs and −30…50 MB resident memory.
  • Reverse proxy LAN names — lan_dns now renders interface-name=<host>,<bridge> (A and AAAA of the LAN bridge, following a new delegated prefix). The previous host-record gave A only, dnsmasq forwarded the AAAA query and IPv6 clients went to the public address.
  • Proxy on — its dnsmasq (LAN port 53 is redirected there) never asked the main dnsmasq for the reverse proxy's hosts or dns.records names; it now forwards them to 127.0.0.1 and allows their private answers (rebind-domain-ok).
  • IPv6:两条 WAN 各有前缀时,路由器自身发起的 IPv6 流量选错源地址被上游丢弃 #97 — with two WANs that each delegate a prefix, the router's own IPv6 picked the other WAN's prefix as source and the upstream dropped it; each WAN now gets a main-table default route with src from its own prefix (removed / demoted when the prefix goes or the WAN is down).

Why

Migration of a real deployment from lucky to the built-in services exposed the LAN DNS gaps; #97 was found on the same router.

Verification

  • tools/ci.sh private and public: ALL CHECKS PASSED — new: TestEdgeLANDNSWithProxy, TestSrcDefaults6, netns checks for the router's own IPv6 through a prefix-filtering upstream (and after the prefix goes away), home config with DDNS + reverse proxy rendered through real nft / dnsmasq.
  • Verified on the live router (with the currently deployed image): certificates issued through Cloudflare DNS-01, sites reachable from the LAN (IPv4 + IPv6) and from the internet.
  • sync-public.py: no leaks.

Closes #97

https://claude.ai/code/session_01HWeUjo1dmS7gBkCYHrVjCr

…AAA; router IPv6 source per WAN

- lucky is gone: init scripts, the services.lucky option (an old config gets a clear error), UI,
  build (the binary is no longer in the image), CI and docs; services.ddns + services.edge replace it
- services.edge lan_dns: the route hosts are an interface-name (A and AAAA of the LAN bridge,
  following a new prefix); a host-record gave A only and the AAAA query went upstream
- with the proxy on, its dnsmasq (which answers the LAN) forwards the reverse proxy's hosts and the
  dns.records names to the main dnsmasq (and lets the private answers through rebind protection)
- two WANs with delegated prefixes: the router's own IPv6 leaves each WAN from that WAN's prefix
  (a default route with src per WAN), so the upstream no longer drops it

Closes #97

Claude-Session: https://claude.ai/code/session_01HWeUjo1dmS7gBkCYHrVjCr
@Cd1s
Cd1s merged commit f8cd486 into main Sep 26, 2026
2 checks passed
@Cd1s
Cd1s deleted the fix/lucky-edge-v6src branch September 26, 2026 09:40
@Cd1s Cd1s mentioned this pull request Sep 26, 2026
52 tasks done
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.

IPv6:两条 WAN 各有前缀时,路由器自身发起的 IPv6 流量选错源地址被上游丢弃

1 participant