Repository navigation
Remove lucky; LAN names with A + AAAA; router IPv6 source per WAN - #98
Merged
Merged
Conversation
…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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
services.lucky(an old config getsservices.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.lan_dnsnow rendersinterface-name=<host>,<bridge>(A and AAAA of the LAN bridge, following a new delegated prefix). The previoushost-recordgave A only, dnsmasq forwarded the AAAA query and IPv6 clients went to the public address.dns.recordsnames; it now forwards them to127.0.0.1and allows their private answers (rebind-domain-ok).srcfrom 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.shprivate 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.sync-public.py: no leaks.Closes #97
https://claude.ai/code/session_01HWeUjo1dmS7gBkCYHrVjCr