dchub
dchub is a Direct Connect hub clone. It resembles an IRC server with some extra features dedicated to file sharing.
| Tags | Communications File Sharing Direct Connect |
|---|---|
| Licenses | GPL |
Recent releases
- 28 Nov 2003 10:44
Changes: Some commands were moved into plugins. Duplicate rule emission in the log has been fixed. ClientBot has been updated to use the new commands. A message flood control bug has been fixed.
- 26 Oct 2003 04:52
Changes: Configuration files are in XML. Perl problems were fixed. The hub does not hang when kicking users from a script. Passwords are crypted. The account privilege system was totally revisited. Numerous incorrect type conversions were fixed. A crash which occurred when the -f flag was used without a parameter was fixed.
- 04 Oct 2003 02:08
Changes: This release supports both libgcrypt and OpenSSL. Many commands are now cluster compatible (*kick, *ban). Ban by IP was included, and a bug that allowed users without nicknames to enter the hub waas fixed. New events were added for ban, kick, and hubinit. ClientBot now handles new clients and manages some of the '#' commands (making them cluster compatible).
- 21 Jul 2003 08:14
Changes: The cluster port can now be changed. Bugs in log file rotation and the *banip functions were fixed. A timeout on dying connections was added. A compilation problem on Alpha was fixed. Some debug messages were removed. The crash occuring in -pbanip was fixed. The bug that sometimes prevented a user with an unpriviliged password-protected account from reconnecting was fixed. The German documentation was updated.
- 17 May 2003 07:24
Changes: *kick commands have been partially rewritten. A duplicated multichat message problem has been fixed. The Perl handler has been rewritten. ClientBot has been greatly improved. The -hpstat command has been repaired. Duplicated hello/quit messages on the cluster have been removed.
- All comments
Recent commentsKudos
Also, thanks for fixing that problem in dchub. Keep up the hard work, and I will try and contribute all I can to help!
Multi-hub Fusion and bots?
I was just wondering if anyone had setup a multi-hub fusion with multiple bots for any sort of events like checking for files from users, etc, since I am trying to determine if I have multiple security bots setup on different hubs (1 per hub of course), would the users be checked upon entering the hub fusion by all bots or upon entering the specific hub that they were originally logged into? So if they tried to login to myhub1.com, and it was in a multi-hub fusion with myhub2.com, would the bot in myhub1.com check and then the one in myhub2.com check, or would it just be the one in myhub1.com? Also, if the user was not registered in one hub, and they entered the multi-hub fusion, would the user be rejected?
Overall, I think that I am just somewhat confused on the interaction of the hubs most likely and what data they trade back and forth in terms of userlists, and how they delegate which hub has what responsibilities in terms of requests from users, etc.
Thanks again.
Re: ban mask ip
> what im must write and where to ban mask
> ip 62.87.xxx.xxx
>
> PLEASE HELP
> aptekarz@tenbit.pl
What you just need to do is add a line to the .ipmask file with just "62.87", since it's doing a substring check of the IPs obtained. Then make a reverse boolean logic statement in the "dchub_myinfo_handler.pl" script, located in the script dir under your dchub dir under the IP filtering section to enable IPs other that the ones given in the file to be referenced. Then, you must restart the hub using the Perl interpreter, referencing "main.pl" as your startup Perl script.
Good luck,
Garrett
Error with DCHub 0.41
Well, apparently I found an error with DCHub 0.41. We just upgraded from 0.22 to 0.41 (since 0.40 kept on crashing the server), and I noticed that the amount of "ghost users" increased dramatically. I kicked several users via the regular kick command in the UI of DC++, but several people complained, and then I tried to kick one of these "ghost users" via Hub-Security using -skick. The funny thing is that it completely terminated the DCHub program (I am assuming due to some uncaught exception).
So here's a fix that I propose: since I noticed that the users logging on had the same IP and share size, I believe that the hub should check the incoming IP, do a substring check of the any username with the same IP. Then see if any similar names are on, kick the ghost user, tell the client to relog, and wham! done.
Thanks a lot for your time.
Garrett
ban mask ip
what im must write and where to ban mask ip 62.87.xxx.xxx
PLEASE HELP
aptekarz@tenbit.pl