This guide connects active mode, passive-mode limits, and the TCP, UDP, router, firewall, VPN, and public-address settings used by a DC++ client.
Usage
- Open Active Mode, set the client to active mode, and note its public address plus TCP, UDP, and optional TLS ports.
- Forward the same ports through the router and allow them in the computer firewall.
- Enter Your Public Host Or IP and Active TCP Port; add UDP Port or TLS Port only when configured.
- Select Check Active Mode.
Concrete Example
A client uses TCP and UDP port 50000. Forward TCP 50000 and UDP 50000 to that computer, allow both in the firewall, and test the public address with TCP 50000. An open TCP result confirms outside reachability from this server. It does not prove UDP search replies.
Interpretation
An open TCP listener supports incoming peer connections. A failed TCP result points to the client listener, forwarding, local firewall, VPN, CGNAT, ISP policy, or address. Optional TLS is separate. Passive mode can still join hubs and chat, but two passive users normally cannot connect directly and search results can be reduced.
Troubleshooting
- UDP: A web request cannot prove UDP without a real client reply; match the UDP port in the client, router, and firewall, then test a live search.
- CGNAT: Ask the ISP for a public address or use a VPN that supplies a forwarded port.
- Double NAT: Forward through both routing devices or bridge the upstream device.
- VPN: Use the provider-assigned port and address, not the home router's public address.
Icon Reference
| Icon | Label | What It Does |
|---|---|---|
| Check Active Mode | Check Active Mode submits the public address and configured active-mode ports. | |
| Complete | Complete marks a finished active-mode check. | |
| Review Output | Review Output marks a closed, filtered, partial, or manual result. | |
| Open Help | Open Help opens this active-mode guide. |