...and as appearently you are the one who can reproduce the bug, instead of suggesting it as a general problem, it'd nice from you to came up with some steps to reproduce. E.g. I have been running a two ADCH++ hubs for 4 years and I've never seen this issue...
-- You received this bug notification because you are a member of Dcplusplus-team, which is subscribed to ADCH++. https://bugs.launchpad.net/bugs/1127553 Title: Connection closed without reason to the client Status in ADCH++: New Bug description: When a client tries to connect with a registered nickname, sometimes the hub decides it can not verify the client's authentication. However, the client doesn't get any message about what is wrong and only gets disconnected. Meanwhile, while running the hub in dbg, the only message that is related to it is "disconnecting because 18" - also not very informative. Sometimes a password change may help, but even that isn't always helping. A session from dbg: W7OC connected W7OC ready W7OC entering IDENTIFY W7OC verifying IP xx.xx.xx.xx W7OC verifying CID VFXHSFHDWWX6BRBOTRT7NYN6DSDGQAWELQ4YHWA W7OC verifying nick DjSlash W7OC entering VERIFY W7OC disconnecting because 18 Removing W7OC - VFXHSFHDWWX6BRBOTRT7NYN6DSDGQAWELQ4YHWA ManagedSocket deleted SocketStream deleted To manage notifications about this bug go to: https://bugs.launchpad.net/adchpp/+bug/1127553/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : linuxdcpp-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
