DC++ and similar Direct connect clients tutorial

In that case you'd have to allow incoming connections to all unpriviledged ports since dc++ will assign a new random listening port on each porgram start. This will only work if you are either directly connected to the internet (no router or NAT) or if all those ports are also open in the router. Not recommended.

Please note that in the latest batch of DC++ software, there is an ADDITIONAL incoming TCP port for TLS (secure) connections. This port should be different from the regular TCP listening port and will also have to be openend both in the firewall as well as in the router.

I noticed that the previously posted rulesets lack outgoing connections (or maybe I've read too quickly over them). You will thus also need the following rules:

Rule for TCP protocol

Action = Allow
Protocol = TCP
Direction = Out
Source IP = Local Network zone
Destination IP = Any
Source port = [unprivileged] port set
Destination port = [unprivileged] port set

Rules for UDP protocol

Action = Allow
Protocol = UDP
Direction = Out
Source IP = Local Network zone
Destination IP = Any
Source port = [unprivileged] port set
Destination port = [unprivileged] port set

Action = Allow
Protocol = UDP
Direction = Out
Source IP = Local Network zone
Destination IP = [Your DNS Servers] zone
Source port = [unprivileged] port set
Destination port = 53

If a hub uses a tcp port below 1025 you will have to either change the destination port to "any" in the tcp rules or make separate rules.