·How do I setup a hub?
·Where can I get hub software?
·What are the minimum hardware requirements?
·How to run a hub with a dynamic IP?
·How do I make my hub private?
·How to setup NMDC Hub v1

There are many different types of hub software out there today, but they all require the same basics.  A computer, hub software, scripts/plugins and a dynamic name. Each obviously varies in setup, options, security, performance enhancements, etc.  There are simply too many out there for this FAQ to show a how-to for each.  Read the help files that come with each hub software.  If any questions arise, post it on the hub software's specific forum, listed in the help file.  If you're behind a router, then you will need to forward the port(s) your hub is running on.  The same methodology that's outlined in this FAQ applies to a hub.

•How to set up Ynhub
•Looking for other guides...

feedback form

feedback form

Any feedback you provide (corrections, updates or suggestions) are sent to the owner of this FAQ
and anyone else involved in writing or editing this item.

by USR56K edited by JMGullett
last modified: 2007-02-01 16:13:54

The table is a work in progress, suggestions are welcome.

NMDC Protocol Based Hubs

Hub Name	OS	CLI / GUI /Service	Scripts	Plugins	$UserCommand	$UserIP	$UserIP2	$NoHello	$NoGetINFO	$BotINFO	Quicklist	Other
Aquila		CLI / Ser		X				Native	Native	Native		ZLine
BDCH		CLI / Ser	Lua 5		Native		Native	Native	Native	Native	Native	SecuredExecutor, Webservice
DCH:Pro		GUI
DCH++		CLI / Ser	Lua 4/5	X	Plugin, Script	Plugin	Plugin	Native		Plugin
dchub		CLI / Ser	Perl, Python	X
dchubjava		GUI?	Java
DConnect Daemon		CLI	Perl
DCSH		CLI / Ser	Lua 5
LatHack		GUI		X
Lamahub		CLI	Lua 5	X
ODC(#)H		CLI / Ser		X						Plugin
Open DC Hub		CLI / Ser	Perl		Script	Script				Script
PHPDC-Hub	All	Ser	PHP
PtokaX		GUI	Lua 5		Script	Script						ZLine
py-dchub	All	CLI	Python
RDCHub		GUI	X
SBSoftEA		GUI	Pascal	X
SDCH		GUI	VBScript, JScript		Native	Native		Native	Native	Native	Native
Verlihub		CLI / GUI / Ser	Bash, Perl, Lua 4/5	X	Native	Native	Native	Native	Native	Native
XHub		GUI				Native				Native		Multihub
Ynhub		GUI			Adv. Textfile	Native	Native	Native	Native	Native
..

ADC Protocol Based Hubs

Hub Name	OS	CLI / GUI /Service	Scripts	Plugins	Other
ADCH++		CLI
DCNet-X		CLI / Ser
DSHub		CLI/GUI			PING Extension
DC-Hub		CLI / Ser
luadch		CLI
µHub		CLI

Windows Based

•PtokaX - Stable hubsoftware, especially popular for the larger hubs.  Extensions useLua version 4 scripts.
•DCH++ - From thecreator of DC++, he's developing hub software which is still closedbeta.  Extensions are either plugins or Lua version 5 scripts.
•SBSoftEA - Written inDelphi. Extensions are scripts.
•YnHub - Completerewrite of the popular Yhub by two great Devs.  Most features arebuilt in, so no need for plugins/scripts. 
•ODC(#)H -Written in C#.  Extensions are plugins.
•SDCH - ShadowDCHub. Open source, written in VB6.  Extensions are written invbscript.
• RDCHub
•XHub - Many advanced features(client detection, adv rules, multihub linking).
•LatHack DC Hub- Hub purely based on C/C++ plugins.  Comes with severalrudimentary ones: anti-flood, anti-spam, IP filter, OP chat.
•DCH:Pro -
•Direct Connect Secured Hub- (aka DCSH)
 

•dchubjava

feedback form

feedback form

Any feedback you provide (corrections, updates or suggestions) are sent to the owner of this FAQ
and anyone else involved in writing or editing this item.

by USR56K
last modified: 2008-04-04 19:31:39

•Computer- A dedicated computer is ideal for greater stability.  A shared computer, which you use for daily tasks, also works but is not ideal because of more frequent computer reboots and the chance of crashes.


•CPU- The speed of the computer is primarily dependent on the number of users you will host. You can get away with a Pentium 120 for a small hub and no scripts. Larger hubs (4000+) typically need a modern CPU to deal with the spikes and more complex scripts/plugins, etc.  A2+ Ghz CPU should suffice.

•Memory- Memory also scales with the user count. 64MB is ok for a small hub (think 100 users), but once you get more users it's a VERY good idea to install more memory so the OS doesn't use the page file. Memory usage is also very  dependent on the hub software being used and the operating system.  512MB should be enough for most hubs.

•OS- The operating system you use is another important choice to make. Running a hub on Windows 98SE (also includes Win95 and WinME) would NOT be a good idea because, after several days, the memory usage of windows, the hub software and whatever else you are running would skyrocket due to the poor management of the Win9x OS. Windows 2000/XP/2003 or Linux are ideal because they all contain superior memory management, security and stability.

•Network Connection - Yet another variable that depends heavily on the user count and slightly less on the hub software in use. Minimum, you need 128 kbps upload dedicated to a hub. If you share your server pipeline with DC++, then it's a good idea to use some sort of upload limiting on DC++. This is so the DC++ uploads don't saturate your upload pipe and lag your hub. Obviously, the more users you host, the larger the pipeline you'll need. You can safely host 100 - 200 users with any hub software on a dedicated 128kbps upload.  A 7000 user hub can consume 7 MiB/s.

feedback form

feedback form

Any feedback you provide (corrections, updates or suggestions) are sent to the owner of this FAQ
and anyone else involved in writing or editing this item.

by USR56K edited by JMGullett
last modified: 2007-02-01 16:36:36

There are two options for an address for a hub, either an IP address or a dynamic name. If the server has a static IP, then you could use it when registering on the public lists. Although, if the IP ever changes, it will often take days to be updated across all of the main ones. This is why you use a dynamic host service like Dynip or DynDns. Users will always use the same name (i.e. myserver.kicks-ass.net) when accessing your hub. If the IP ever changes, you simply update the dynamic name with the new IP and, within hours, all DNS will have been updated.

feedback form

feedback form

Any feedback you provide (corrections, updates or suggestions) are sent to the owner of this FAQ
and anyone else involved in writing or editing this item.

by USR56K edited by JMGullett
last modified: 2007-02-01 16:40:43

There are a few things you can do to make your hub private.

•In the hub software, enable the option to only allow registered users.  Consult the hub documentation on how to accomplish this.
•Only allow certain IP ranges to connect to the hub (such as only your University). This can be accomplished in some hub software. Otherwise, you'll need to do this in a firewall.

feedback form

feedback form

Any feedback you provide (corrections, updates or suggestions) are sent to the owner of this FAQ
and anyone else involved in writing or editing this item.

by USR56K edited by JMGullett
last modified: 2007-02-01 16:42:01

This hub software is no longer used on DC. The guide will be kept around for historical purposes.

How to create a hub using NeoModus Direct Connect Hub version 1

1. Download the hub software from www.neo-modus.com; make sure you download "Direct Connect Hub (v1.0)."

2. Install the program to any location you wish. C:\Program Files\Direct Connect Hub is the default.

3. Once it's installed, start the hub.

If you receive that error message, you need to either install NeoModus Direct Connect version 1 or download DCSysTray.ocx and put it in your \Windows\System32 directory.

4. Once you have started the hub, you will be at a screen that looks like this:

•Listening Port: This is the port the hub operates on. 411 is the default port used. If you run multiple instances of DCHub on the same computer, you MUST use a different port for each hub.
•Register hub with: This is the address the hub will register itself with so others can find it.
•Auto Register: Disable this if you want the hub to not show up on the public hub list. Although, it seems the hub will do so regardless of the setting (bug).
•Auto Start Serving: Enable this if you want to have the hub software start to host right on startup. Otherwise, you must click on 'start serving' in the bottom right before users can enter the hub.
• Redirect Address: You can redirect users to another hub when your hub is full or going down for maintenance. Many scripts require something in this field, so if you don't want to forward to another hub enter 127.0.0.1.
•Min Client Version: Only applies to NMDC clients, DC++ is unaffected. 1.0091 is the latest build of the NMDC v1 client.

•Max Users: Limit the number of users the hub will hold.
•My IP Address: You can either enter your IP or a use a dynamic host service like Dynip or DynDns. It's recommended that you use a dynamic name for this reason. Append the port number if not using 411.
•Name: Enter in a unique hub name.
•Description: It's good practice to list your basic hub rules in here (i.e. share, slots). You can also list the theme for the hub.
•Start Serving: Click this once you have the hub set up. It will be automatically checked if 'Auto start serving' is enabled.

5. Client Stats

This window will show you all users that are currently logged on. If you double click on a name, the user will be disconnected.

6. Security

Here is where you can add registered users and operators. Also, you can see which IP's are permanently and temporarily banned in the hub. Default temp ban time is 10 minutes.

•Bot Pass: It's very important to use a password that uses letters, numbers and shift characters so an outsider cannot control the bot.
•Only allow registered users: If you want a private hub, enable this setting. Only users who are registered will be allowed to enter.

7. Client Interactions

In this window you can setup the welcome message that everyone will see on logon. You also can send a mass private message to every user in the hub (this is a good idea when the hub is being restarted, etc).

8. Status Messages

This window will show you all the things the hub is sending and receiving. The window is read from bottom to top. In the above window, the hub registered itself on the hub list. Then a user with the name 'BSOD2600' logged on to the hub using DC++ 0.263. Then the client searched for an MP3. The bottom two windows will occasionally show hub or script errors.

9. Scripts

Ahhh, the most important component of the hub, its scripts. First you need to find the scripts you want to use in the hub. A list of sites has been compiled here. Once the scripts have been downloaded, place them into your Scripts directory (i.e. C:\Program Files\Direct Connect Hub\Scripts). Scripts will have the .script file extension, and its icon will have .ico (if present). If you don't see the extension, then enable it on windows.

You can edit scripts two ways, either with a text editor like notepad or using the script host window. When you click on a script name in the left window, it will open up the file. Be careful, though. The editor has a 64k size limit for editing. This means that if your script file is 104K, it will only be able to open the first 64k. When you save the file, it will be unusable to the hub since half of it will now be missing.

10. Network Searching

The description in the hub software is pretty self-explanatory about how this is used. It's really not used all that often.

11. Optimizations

•Enable Scripting: Disabling scripts will lighten the load on the computer. Of course, without scripts, the hub is pretty wide open.
•Block chat messages: Basically an anti-spam setting for main chat.
•Do not send chat messages to away users: Self-explanatory. If a user is away, the hub will not send messages to them; generally not recommended to enable.

feedback form

feedback form

Any feedback you provide (corrections, updates or suggestions) are sent to the owner of this FAQ
and anyone else involved in writing or editing this item.

by USR56K edited by JMGullett
last modified: 2007-02-01 16:58:01