Skip to content

feat(net): require public IPv4 on PPPoE WANs - #150

Merged
Cd1s merged 4 commits into
mainfrom
feat/require-public-ip
Oct 17, 2026
Merged

Cd1s merged 4 commits into
mainfrom
feat/require-public-ip

Conversation

@Cd1s

@Cd1s Cd1s commented Oct 17, 2026

Copy link
Copy Markdown
Owner

What

  • Add wan[].require_public_ip for PPPoE WANs, with configurable cooldown, bounded automatic redials, persistent runtime state, risk events, validation, docs, lab config coverage, and doctor guidance.
  • Remove unhealthy WAN IPv6 defaults from the WAN policy table and raise its main RA route metric alongside IPv4 failover.
  • Persist gateway conflict event deduplication under /run/mini-router/ and replace the proxy-off hand-written reverse check with rendered proxy configuration coverage.

Why

PPPoE sessions can be admitted into an ISP CGNAT/private-address pool without usable egress. The router should recover only that session, stop after repeated failures, and explain the condition. Multi-WAN failover must switch both address families, and hook processes need state that survives process boundaries.

Verification

  • cd mr && gofmt -l .
  • cd mr && go vet ./...
  • cd mr && go test -count=1 ./...
  • sh tools/ci.sh

Closes #144

@Cd1s
Cd1s force-pushed the feat/require-public-ip branch from 1224a8e to 1287afa Compare October 17, 2026 15:38
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.

net: follow-ups from #138 (event dedupe across hook processes, proxy-off reverse test)

1 participant