Windows Firewall access is on the game host. DD-WRT forwarding is on your router. An external test checks the outside path. Passing one does not prove the others or a successful gameplay join.
1. Prepare the host and game
Use a supported DD-WRT router reachable from the trusted LAN. Give your Windows server host a stable LAN address, such as a DHCP reservation. Install a game in Keldrin and review its ports and connection mode. If two servers require the same public protocol/port, configure distinct ports before forwarding.
Keldrin derives requirements from installed game packages and the active connection mode. Ordinary WindRose invite/NAT mode and Valheim Crossplay do not need a fixed router-forwarded port. Their Windows application-access requirements are separate.
2. Save and inspect
In Keldrin, open Managed Ports. Enable Manage DD-WRT game-port forwarding, enter DD-WRT router IPv4, Router username and the write-only password, then choose Save and inspect. The password is stored locally with Windows current-user protection.
3. Understand the inspection
| Result | Meaning / next step |
|---|---|
| Managed | The required enabled Keldrin-owned rule matches this host and endpoint. |
| Missing | A required forwarding rule is absent. Review the proposed rule before applying. |
| Managed elsewhere | A Keldrin-owned rule targets another host. Confirm the intended destination before changing it. |
| Legacy conflict | An existing unmarked rule needs an ownership decision. Review it before choosing Take ownership. |
| Foreign conflict | An overlapping rule belongs to another purpose. Resolve the conflict deliberately; Keldrin does not automatically remove unrelated ranges. |
4. Apply only the reviewed rules
Choose Take ownership and apply when the displayed destinations and ranges are correct. Keldrin can mark exact legacy game rules and create missing managed rules. It does not give blanket ownership of unrelated forwarding entries. Use Refresh rules to inspect the result.
The managed DD-WRT rule names are compact and start with *. The status uses current inspection evidence, with periodic refresh at most every ten minutes and immediate refresh after relevant settings or ownership changes.
In DD-WRT, open NAT / QoS → Port Range Forwarding to review the matching router entries.
*CoreKeeper and *Valheim rules share the game host’s LAN address. Use your own host address and the ports configured in Keldrin.What success looks like
5. Confirm the outside path
Configure the Remote Portal outside your home network. Keldrin can then report its supported external-connectivity evidence. Exact temporary nonce tests run only while the game is stopped; running games keep ownership of their sockets. Complete the final check by joining from a genuinely external computer.
If your ISP uses carrier-grade NAT, or another router sits upstream, forwarding on DD-WRT alone may not make your server reachable. Review the upstream arrangement. Never forward Keldrin Local Web’s TCP 8080; use the Remote Portal for remote controls.
Try it without changing anything
The interactive demo uses the current Local Web interface with dummy servers. Every result is simulated; it transfers no files and changes no real systems.