User stuartj is partially correct in his assessment of DC++.
I say partially because many users are passive due to it being extra work to go active.
Passive users can u/l or d/l only to/from active users, significantly reducing their user pool.
“Serious” DC++ users are active – going passive is a limp-along solution.
Also, I found several articles on using remote.it to set up TCP/UDP ports.
So apparently (hopefully!) it *IS* a fit if I can just figure out how to do it.
I am using the Remote.it Application on Windows 11.
I set up the TCP and UDP services following on-line instructions.
I would normally connect DC++ as follows:
My IP addr: 192.168.1.169
TCP port: 1406
UDP port: 1407
The resulting remote.it local endpoints were:
bobs-hp-laptop-tcp-for-dc.at.remote.it:1406
bobs-hp-laptop-udp-for-dc.at.remote.it:33000
I then changed the DC++ connections to:
IP addr: 127.0.0.1
TCP port: 1406
UDP port: 33000
No joy – no search results in DC++, which means Active is not working
Both remote.it connections say … Idle - Connect on demand
Am I missing a step to connect the services?