Background
In some PPPoE bridge deployments, luci-app-ap-modem can add a WAN-side virtual IP (e.g. 192.168.1.254/24) and routing looks correct, but LAN clients still cannot open modem UI (192.168.1.1).
Typical symptom:
- TCP connect to
192.168.1.1:80 succeeds
- HTTP request from LAN clients times out
- Router-local curl to
192.168.1.1 works
Why
Some modem firmwares only reply to management traffic when the source IP is in their local subnet / expected interface policy.
Proposal
Two improvements would help many users:
-
Docs / troubleshooting note
- Mention this symptom and suggest adding SNAT for traffic to modem management IP.
-
Optional feature in luci-app-ap-modem
- Add an optional SNAT toggle in Global Settings:
- enable SNAT
- destination IP (modem IP, e.g.
192.168.1.1)
- source IP (virtual IP, e.g.
192.168.1.254)
- Keep default OFF to avoid changing existing behavior.
If maintainers agree, I can send a PR with a minimal implementation.
Background
In some PPPoE bridge deployments,
luci-app-ap-modemcan add a WAN-side virtual IP (e.g.192.168.1.254/24) and routing looks correct, but LAN clients still cannot open modem UI (192.168.1.1).Typical symptom:
192.168.1.1:80succeeds192.168.1.1worksWhy
Some modem firmwares only reply to management traffic when the source IP is in their local subnet / expected interface policy.
Proposal
Two improvements would help many users:
Docs / troubleshooting note
Optional feature in luci-app-ap-modem
192.168.1.1)192.168.1.254)If maintainers agree, I can send a PR with a minimal implementation.