Hello All,
What are the ports that DC++ use to connect to hubs/other clients? and what are the port types (TCP/UDP)? I need this info in order to configure my firewall not to block these ports.
Thanx,
komar.
DC++ Ports
Moderator: Moderators
Hubs usually listens to port 411 (tcp).
The NMDC client uses default port 412 (tcp AND udp).
DC++ uses default random port settings IIRC, but please set it to whatever you like (1412 is good). QuickDC use 1412 because ports below 1024 are privileged on UNIX.
The NMDC client uses default port 412 (tcp AND udp).
DC++ uses default random port settings IIRC, but please set it to whatever you like (1412 is good). QuickDC use 1412 because ports below 1024 are privileged on UNIX.
I wrote QuickDC - A DC++ compatible client for Linux and FreeBSD.
-
ivulfusbar
- Posts: 506
- Joined: 2003-01-03 07:33
DC++ ports
> DC++ uses default random port settings IIRC
And these are?
Sofar I need to enable the following firewal rules to run in active mode, but lately I have the feeling clients use more ports than I currently have configured:
Inbound TCP/UDP Your client port in active mode
Outbound TCP 80 (hublist)
Outbound TCP/UDP 375-425
Outbound TCP/UDP 1410-1415
The next one I had to enable once I found out that I got timeouts on someone that had all slots available (seems I wasn't the only one who couldn't connect to him)
Outbound TCP/UDP 33276
Is this a 'default random IRC port'? And what range would they come from? if that random means 1024+ then it will make firewalls that allow all those outbound port very unselective on what traffic goes out and so less safe. (Just remember the recently Ms SQL worm. Firewalls that do not allow outbound traffic on that port did not cause trouble on the internet.
And these are?
Sofar I need to enable the following firewal rules to run in active mode, but lately I have the feeling clients use more ports than I currently have configured:
Inbound TCP/UDP Your client port in active mode
Outbound TCP 80 (hublist)
Outbound TCP/UDP 375-425
Outbound TCP/UDP 1410-1415
The next one I had to enable once I found out that I got timeouts on someone that had all slots available (seems I wasn't the only one who couldn't connect to him)
Outbound TCP/UDP 33276
Is this a 'default random IRC port'? And what range would they come from? if that random means 1024+ then it will make firewalls that allow all those outbound port very unselective on what traffic goes out and so less safe. (Just remember the recently Ms SQL worm. Firewalls that do not allow outbound traffic on that port did not cause trouble on the internet.
Re: DC++ ports
Same question here. Please enlight us 
Also - what are UDP ports used for??
Also - what are UDP ports used for??
-
GargoyleMT
- DC++ Contributor
- Posts: 3212
- Joined: 2003-01-07 21:46
- Location: .pa.us
Re: DC++ ports
So you want to know what you need to open up on a real (filtering both ways instead of just inbound) firewall for DC++?
First off, UDP is used for search results in active mode.
Secondly, DC++ uses a very wide range of port, by default, to listen to:
You only have to open up port 80 to dcplusplus.sourceforge.net (for version.xml checking, plus hub list), as well as to any host you have set as a hub list.
You'll have to open up tcp outbound on the ports that the hubs you're going to be using run on.
You'll have to open up inbound TCP/UDP on the port you force DC++ to use.
You'll have to open outbound TCP/UDP to the ports the remote clients use. You could restrict this to just 1412, and say f'off to non-standard clients. Otherwise, you'll have to open up the whole range, because DC++ will not complain if you put a port lower or higher than (1025, 32000) in the settings.
First off, UDP is used for search results in active mode.
Secondly, DC++ uses a very wide range of port, by default, to listen to:
Code: Select all
setDefault(IN_PORT, Util::rand(1025, 32000));You'll have to open up tcp outbound on the ports that the hubs you're going to be using run on.
You'll have to open up inbound TCP/UDP on the port you force DC++ to use.
You'll have to open outbound TCP/UDP to the ports the remote clients use. You could restrict this to just 1412, and say f'off to non-standard clients. Otherwise, you'll have to open up the whole range, because DC++ will not complain if you put a port lower or higher than (1025, 32000) in the settings.