Solved the problem for me too. One little mistake though. For the BZR the line is 690 in AdcHub.cpp
Normally looks like updateCounts(false); Should be changed to if (state == STATE_NORMAL) updateCounts(false); -- You received this bug notification because you are a member of LinuxDC++ Contributors, which is subscribed to LinuxDC++. https://bugs.launchpad.net/bugs/933421 Title: connecting to ADCS hubs shows public tag Status in Linux DC++: New Bug description: When connecting to ADCS hubs with linuxdcpp 1.1 (debian squeeze) as a registered user( or OP) the tag shows as being in a public hub and changes to private only after 10-15 seconds. In case of a single hub: 1/0/0 to 0/0/1. This is causing problems in private hubs where no public hubs are tolerated and it makes login impossible when the check is performed during login. This is regardless of the actual hubsoft, tested luadch, flexhub adchpp in the queue. Logs from flexhub feed: [13:13] <HUBSEC> [LOGIN] [A] [LAJ] [2] IP: xx.xx.xx.xx <nick unknown> HSUP OK. [13:13] <HUBSEC> [FI] [0] Monitored nick is connecting... all traffic outputs to: Feed [13:13] <HUBSEC> [LOGIN] [A] [LAJ] [4] IP: xx.xx.xx.xx <@ldcpp> BINF OK. [13:13] <HUBSEC> [Monitoring <xx.xx.xx.xx>] [RCV] HPAS CID [13:13] <HUBSEC> [X] [0] [Redirect] [GetAddress] Request: maxhubs / Path: USED:true LIST:Fix.your.maxhubs.settings! / Answer: Fix.your.maxhubs.settings! [13:13] <HUBSEC> [FI] [1] [Redirect] maxhubsIP: xx.xx.xx.xx <@ldcpp> was redirected to: Fix.your.maxhubs.settings! because: Connected to too many public hubs, you have: 1, the hub maximum is: 0 To manage notifications about this bug go to: https://bugs.launchpad.net/linuxdcpp/+bug/933421/+subscriptions -- Mailing list: https://launchpad.net/~linuxdcpp-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~linuxdcpp-contributors More help : https://help.launchpad.net/ListHelp
